Introduce target selector for lights #5
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
This uses the native homeassistant target selector over the previous entities selector. This means we can target areas as well as individual lights, and aligns with the expectations of the platform in general. This commit also includes a refactor of the card configuration that will migrate previous configurations to the latest state (specifically from the use of entities to targets for previous version migration)
I want it to be shown as optional, so that a default can be applied later in the flow (rather than ensuring it exists)
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.
The target selector is a better (and more aligned) experience with homeassisstant - and also means you can select an entire area for your lights (rather than one-by-one)
Care was made (and specs added) to ensure previous configuration migrates forward appropriately (you should see your previously selected entities appear within the new component)