Remove Hue discovery on manual configuration #17070
Merged
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
homeassistant
added
integration: hue
small-pr
ghost
assigned 
pvizeli
approved these changes
Oct 4, 2018
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description:
We used to allow
hue:to be configured in configuration.yaml without any options. This would then trigger a discovery of hubs and then set them up. When we moved to config entries, the logic changed to discover and them import them. This allowed people transitioning to import their auth.This logic was introduced on March 30. Now it's time to sunset this behavior.
Related issue (if applicable): fixes #17025
Example entry for
configuration.yaml(if applicable):hue:Checklist:
tox. Your PR cannot be merged unless tests passIf the code does not interact with devices: