Just want to also say thanks to the frontend team reacting to this, sometimes a bit too frank, feedback. Just report the facts everyone as the saying goes “Play the ball not the man”
1 Like
I wonder if an option for addressing non-contrasting adjacent ‘not_home’ zones might be as simple as
state-person-zone-odd-color
state-person-zone-even-color
Maybe a colour could be defined for each zone when the zone is created either in Yaml or in the UI?
2 Likes
2022.12.4
History for a sensor which is unavailable now:
Transparent graph…
P.S. Added this post, then deleted it - to recheck to be sure.
Restored it later.
Update:
Sigh. Can we have green back for this please?
5 Likes
I still haven’t forgiven them for shrinking the keypad - and that was a few releases back.
2022.12.4
binary_sensor, device_class=cold
unknown, on, off
Was described in this issue, I just was not able to reproduce it, now got in 2022.12.4:
Beat me to it. I just noticed that. 
What I cannot understand is, why did they release the .4 when they know it injects this bug? Surely it is not a human decision that history graphs for binary sensors changes to yellow on yellow making them unusable. Totally unusable. Only transparent on transparent would be a worse combination.
1 Like
Somehow I feel the title of this filtered away thread is not even adequate anymore.
not only is this thread now only populated by the good people trying to keep the HA Frontend meaningful, and spend hours and hours providing serious feedback. Added to that, we are being confronted by changes that make things even worse…
last 3 4 true new errors listed:
- transparent for unavailable (and obvious incorrect decision to show unknown as off)
- non listed state for unavailable
- non changing colors for binary sensors
- incorrect colors for some: see alarm button disarmed
and as can be seen here Color of states Off and Unavailable are the same in History graph card in release 2022.12 · Issue #14619 · home-assistant/frontend · GitHub, and here The color of binary sensors never changes (regardless of state) · Issue #14701 · home-assistant/frontend · GitHub there is no such thing as a generic color for any state, it all depends on the class (if available).
In my company, I’d call the decision to escalate, and have a serious talk. Can’t do that here probably. If we out the slightest emotion, we would simply be moderated away. And no way to talk to the manager…
Ive started my findings/comments/suggestions already in the last beta. Some things were fixed. In the process other changes were added and made the experience worse. And they are piling up.
I am starting to feel completely let down. One day we are answered this and that is decided (very/light grey). Within 2 lines of chat on a PR, that is decision is abandoned. And some wild experiment is thrown at us, because someone ‘likes’ it?
Come on good people.
at least test your own PR’s before releasing them into the wild…
8 Likes
Wow update looks great! Thank you for fixing unavailable!
One thing puzzles me is why water sensor is red when it is dry ? Should not red be some kind of danger color ?
Because they broke the off colours with the latest update. See the post by Ildar about three posts above.
When this thread was created it was moved to “social” first, then moved to “configuration”, but currently it does look like a “social” since users are communicating here w/o any meaningful affect to HA design.
I think we are back in the way rgb is now defined to have perhaps a solution, which will work for all tasts.
Why not going back to declaration with declaration type (and solve the parsing topic with a backend or whatever parser for the single card, where it is used)
Then everyone can
- define the colors as they are used to with rgba()
- The standard can set transparency to 100%
- The theme users can set color and transparency for whatever they want
2 Likes
yes, and I forgot to add to my post, we should bring this back into the release topic. And suggest a title change.
It’s not about I dislike the 2022.12 color changes. it should read something like Colors are broken in 2022.12
1 Like
exactly ((
with my all due respect to Dev team, and this are not just diplomatic & polite words
1 Like
Fixed.
5 Likes