Allows multiple entries to be added for the integration #39
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Basically we maintain the domain, while for all the other places we use the unique_id for separate instances. Currently the unique_id is generated from the conf_name. For backwards compatibility you would like to be able to set it to "uponor".
…rieve from config_entry : ConfigEntry
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the DOMAIN (uponor) is set as the unique_id.
This prevents multiple entries to be added.
Users can now optionally set a unique_id of their own preference or leave the field empty for it to be auto-generated.
The
async_setupin__init__.pyhas been disabled, and seems like dead code.Disclaimer: I am not familiar with Python and very inexperienced with the custom_component things in HA.
Open to suggestions / improvements.
Fixes #34