-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignore ioBroker vdc generated by digitalstrom-vdc adapter #163
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. |
Is your feature request related to a problem? Please describe.
Currently the adapter reads all available VDCs inside digitalstrom and makes their devices available in ioBroker. Since the digitalstrom-vdc exposes ioBroker devices in digitalstrom, there is no need to loop them back into iobroker (because they exist there in the first place).
Describe the solution you'd like
Best way would be to check if the digitalstrom-vdc is installed. If yes read the config value to get the DSUID of the vdc and then ignore that DSUID with all its devices. The name of the variable inside digitalstrom-vdc is native.vdcDSUID
Describe alternatives you've considered
Keep it like today and have them imported too.
The text was updated successfully, but these errors were encountered: