May be I got it wrong. It could be cleared in case of DISCUSSION.
Two people discuss smth, both may make mistakes, it anyway may be sorted out.
But you may observe it here.
Sorry, my reply was perfectly calm but when there is a real issue and many people are upset about it sarcasm does not help.
Best thing is to acknowledge the issue, not to be dismissive of it.
But that is beside the point, I suppose we wait and hope that the Devs accept that there is an issue that needs to be dealt with and release a fix in the next update 
5 Likes
What really feels strange to me is that one of the most important parts of HA, the dashboard, is probably the worst documented and the one with the most bugs.
It is impossible to find a list of vars for theming. Impossible to find almost anything useful in any official docs. It is all trial&error.
Most features work great, like automation, script etc. Integrations also.
But dashboards/cards are a mess.
Without the 2-3 card developers making the working cards on github/hacs, HA dashboards would essentially be unusable.
1 Like
There is still something I miss. I see a lot of coded solutions and I have no clue where to put them and what effect they have.
I assume I am amongst a larger group who havenāt coded or modified themes and colours. And I have actually no intention to do so. I am still hoping and waiting for an update where this will be fixed in a user friendly way. Thatās my request for the devs that a solution and clear documented information will follow.
I have rolled back to a previous release and I sit tight and wait. So far the new updates have no impact on the functionality I have programmed.
4 Likes
2 ways:
ā wait for an official default theme with colors appropriate for you;
ā wait for a custom theme which you may more or less like - then wait for official docs about āhow to add a theme, how to edit a themeā - or find someoneās step-by-step instructions.
The 2nd way: since currently Dev say that āonly 2 vars are officially supportedā ā means āuse other variables for your own riskā ā then what docs are we talking about? probably only common steps like āhow to add a themeā (w/o explanations for each variable) may be documented thenā¦
I think that since UI elements are changing (which is GOOD generally) ā then list of supported variables may change too ā so maintaining a list of variables in docs could be a not easy task.
1 Like
May I also voice my concern about this change.
The changes to state color does not make any sense. The contrast is terrible.
Now, are we expected to do this manual custom theming or is it going to change/revert back in the future?
I feel like this change shouldāve stayed in the beta and not part of the actual release.
4 Likes
I hope that whoever came up with new colour scheme, will go to petrol station and be welcomed with all the labels changed to slightly different shades of blue with tiny fonts for diesel / petrol / high octane - and then labeled as toxic when he/she says that it was a dumb move.
6 Likes
Found my own solution 
Last question, is there a way to change the colors back before this release?
You could restore a backup from before the update (like I did) or use a theme like for example @robertwigley suggested here.
I canāt see that this theme approach helps with the colouration of zones, or am I missing something? Iām a bit fed up with Green for home, grey for not_home or blue for everywhere else.
Sorry, canāt help you with that. I did not use the theme until now, first I want to set up a test system where I can test new releases to protect my daily use system.
Iām chiming in here with the dislike.
My biggest issue is the history graphs. Off is the same colour as Unavailable. On is both orange and blue depending on if itās a sensor or a switch(?) ā On should be always the same colour. Thin bars of orange are much harder to see than the previous thin bars of green.
Can I change these in a relatively straight forward manner, or should I wait for customisation options?
1 Like
Thatās actually not only a color problem, but a rendering problem. The way they render the timeline bars is incorrect. Antialiasing will blur the colors together at the edge of each bar transition from one color to the next. If a bar is very thin, this reduces contrast a lot more than it would simply with the colors. You can see this by yourself by taking a screenshot of a history timeline and zooming into it. In my history explorer card, I specifically managed the timeline rendering in a way to keep high contrast at the color edges, even for thin bars. The HA devs didnāt do that.
You could use the custom card I linked to above to replace the native history, itās has fully configurable colors and lots of nice other stuff too, I promise 
(shameless plug, sorry).
3 Likes
I too am struggling to see state changes on some cards.
My custom cards are fine, but the core cards, notsomuch.
I appreciate the steps towards making the colour selections easier to customise for theme developers, however I think it would have made sense to retain the previous colour selections in the core pallette so users can deviate away if they wanted.
Idea:
It would be great if there was a page in settings which had all the domains and state options with their default colour selections and from there allow users to select alternate colour for each as desired or necessary.
And any outliers being defined manually as before with css/card-mod or custom cards.
The dev already said a documents page on themes and supported options this was coming soon.
3 Likes
Ah ā¦ that is awesome.
Thanks for the reply 
OK, I should clarify, I was saying that the dev said a documents page was coming soon to themes. Sorry, I donāt think there will be a UI page in the near future. My brains not firing yet and I missread your message.
Still, itās a step in the right direction so we can get in there and get tinkering 
Thanks again. Looks like you guys have had a rough couple of days.
Someā¦ āpassionateā people out there 
Iāve been admin on a couple forums. I bet the private mod chat areaās been busy.
With that, I appreciate all you guys do to try and steer the threads back on point.
Normally itās a thankless task, but thank you guys
7 Likes
Nothing that hasnāt already been said, but given the situation felt it important to stand up and be counted.
I donāt care for the color choices, but as I roll my own I donāt really care what you choose as long as I am able to achieve my own design objectives. A very big thank you to the Dev that offered to provide some documentation on the new direction.
That said, how they chose to do it is puzzling at best. Gaining more control over the colors et.al. is great, but I have a feeling it wonāt be long until this needs to be re-factored. And, I am now wishing I didnāt accidentally stumble on WHY they made this change, because it is just stunning.
In the interest of keeping things constructive, I would like to suggest that from time to time it might be helpful to get outside guidance on big application architecture decisions.
Lastly, while it may ātechnicallyā not be a breaking change, anything that has this big of an impact on such a large part of your user base warrants far more communication than was given ahead of the change.
This is just a hobby for me, but I really do greatly appreciate the project and all the people that spend so much time and energy keeping it great
8 Likes
@ HeyImAlex Thanks for your work! And I did take notice of your earlier post about your add-on. I might have the time to tinker with these coming holidays.
1 Like