Apparently devs decided what colors we need to use?
Would be better they just made a tool to let use define the colors ourselves. I know, you can still change colors, but a simple theme editor would be nice. A leave the choice up to the users. And, … Let each dashboard have it’s own theme.
I have dashboards that are used mostly on PC, but also a dashboard special for my mobile…
Just in case you are not aware: You can set already a different theme for each individual view of a dashboard. So the last point was already possible before…if you define or import different themes.
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 are still a small disaster to me.
2 Likes
hello,
same boat : 2022.12.3 doesnt fix high CPU usage for me, usually my nuc8i5 is at 6% and now 12%.
is there a fix for that to be prepared?
thanks
Just FYI: There are entities/domains that have a lot more than only 4 states, e.g. media players and vaccums come to mind.
so this doesnt get buried in a sidetracked topic, the title of the somewhat subjective I dislike the 2022.12 color changes has been changed to the more succint 2022.12 Color states are broken/unusable
We feel it is important this is discussed in a broader context of community members.
8 Likes
puzzling here, would it be feasible to write that condition so it doesnt retrigger within a set timeframe, per trigger entity?
I mean, if a trigger moves around a bit, but the others are only infrequent travelers, Id want the condition to count for the one that changed a lot, and be sparse in updating, but do allow the less frequent trigger entity to cause an update
edit
it would need to fallback to indivual last_changed ?
{{(now() - trigger.from_state.last_changed).total_seconds() >
states('input_number.presence_timer')|int(default=60)}}
or, simply:
- >
{{(now() - trigger.from_state.last_changed).total_seconds() > 600}}
I guess, and no longer use the this.last_triggered? (btw, that should be this.attributes.last_triggered shouldn’t it?)
There’s already a fix in for the off state colour. Fix binary sensor color when off by piitaya · Pull Request #14735 · home-assistant/frontend · GitHub
1 Like
From another side, this is an open source project where everybody (devs, testers, users-who-help-and-share-solutions, moderators, …) are doing this for free. And everyone should just respect each other and listen to others’ opinions. And may be people should not be strict to some particular person(-s), everyone can make an error, just keep on moving.
7 Likes
This is also a commercial enterprise, so not everybody in this project is working for free.
1 Like
For sure. As I said in general. The guys were be able to make nice drop lists when you make an automation or script with the possible states. I would say that also can be used for setting a colour to them…
Still on 2022.11.5. This mornings update had nothing to offer on colour settings. I keep hoping
For all who are willing to update to latest core 2022.12.4 and expecting to climate color state be fixed: it’s still unfixed, rolling back to 2022.11.5, again.
Why is icon_color not working for Tile card? How to control color for the icons?
Yep.
Including this point. Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
6 Likes
Filed a bug at core because of broken bundled frontend version.
Exactly.
This project is run by a leader that also has a company Nabu Casa. It is Nabu Casa that employs 18 people now. It is Nabu Casa that 1000s of us pay for. I am in Europe and pay 75 Euros per year.
And until now I think I had my moneys worth.
Natually it makes my integration with Amazon Alexa easier than it would have been. But I actually mainly pay because I feel it is important that there are full time staff that ensure that releases are built at a high quality and that difficult technology is developed that require more time than a hobby programmer can do in the weekend. Matter support is a very good example of this.
But the recent months the quality of the releases have suffered and we are many that do not feel we are being listened to.
Instead of looking forward to the next HA release - I fear them. I fear what they will break. I feer how many hours I will need to spend to make things work again.
That is sad
20 Likes
Excellent. Lets hope that constant venting all over the place stops with it too 
2 Likes
Thank you! I’ve seen this before. Users raise a legitimate concern, and their comments are shuffled off to a thread with a dismissive title starting with “I don’t like.” Of course there are things we all don’t like, and most of us don’t care what you don’t like. But when functionality is removed or replaced with something worse, and people speak out about it, it’s not good for the project to just dismiss it as whining.
This is a valid concern. Users should be looking forward to new versions, not dreading them. There are hundreds of feature requests and WTH’s here on this forum, describing exactly what users want. Any of those would be preferable to making changes nobody asked for.
It’s not dismissing, it’s taking a large topic and moving it to a new location so that all the less talked about issues are seen. This isn’t to silence people, it’s to give the small guys a voice in between the over talked about topics. I suggest you try to put yourselves into the shoes of people trying to post an issue in the release thread when all they see is a single topic pushing their posts into a black hole.
11 Likes