State Color not working with some entities.
See original GitHub issueI have the following yaml config for state color.
stateColors:
'off': '#3F5E98'
'on': '#FFDB15'
binary_sensor.off: '#3F5E98'
binary_sensor.on: '#FFDB15'
person.home: '#3F5E98'
alarm_control_panel.disarmed
With this code, not all binary sensors are adapting the set state colors. Only some binary sensor entities show with the set colors, rest shows with the default colors. why is it so?
Issue Analytics
- State:
- Created a year ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Entities card - entity state color - Home Assistant Community
I'd like to change the “state color” of an entity inside an entities card. ... Add CSS styles to (almost) any lovelace card....
Read more >State Color not working · Issue #34 - GitHub
Notice all my entities using secondaryinfo does not have state color. Even the state color set to true.
Read more >How to set a specific color to a specific entity state? - Reddit
In 2022.12 update static/predefined colors for entity states has been ... Any idea where can I specify the color a state is assigned...
Read more >Filing & Other General FAQs - the Texas Secretary of State
In most cases, documents submitted to the Secretary of State for filing are not required to be notarized. The Business Organizations Code (BOC)...
Read more >View entity health status and find entities without alert conditions
The color-coded health status indicates whether app or other entity has any ... an app listed on the APM index that is not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to reproduce this. It will be fixed in the next release.
Fixed in V1.0.24.