What I find really really good is the option to modify name, area and icon in the UI for an entity if it has an unique id. It’s so easy and user friendly that I don’t understand that this functionality can’t be used to set up the colours for the entity as well. In general there are no more then 4 states (on, off, unavailable, unknown). I hope our Devs read this . That would be for me the ultimate solution. The (custom) themes set the global colours and you modify the entity colours to your liking to suit your dashboard.
I am still on 2022.11.5 because the updates after I still a small disaster to me.
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”
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.
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
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…
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
. That would be for me the ultimate solution. The (custom) themes set the global colours and you modify the entity colours to your liking to suit your dashboard.
