Conversation
ghost
assigned
bramkragten
reviewed
Nov 23, 2018
|
|
||
| states.forEach((stateObj) => { | ||
| const domain = computeStateDomain(stateObj); | ||
| if (domain === "alarm_control_panel") { |
9 tasks
bramkragten
approved these changes
Nov 23, 2018
Merged
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
When the user has no Lovelace config, will generate a lovelace config based on the available entities. Uses same strategy as for the legacy state panel.
This will allow users to transition to Lovelace at their own pace. They can keep using the automatic generated one initially.
Fixes #2088
States panel
Lovelace panel (auto-generated)