10 Likes
The new interface seems to have been deployed without extensive research.
There is not enough contrast, and this create immense problems to those with poor vision.
Accent color is not being used (or maybe it’s overriden) by the new color management.
This requires, in my opinion, an expedited rectification.
3 Likes
Why even write that first line? What purpose does it fill other than to throw shade? Just state the issues and move on. EDIT: Now you have me doing it. Sorry.
3 Likes
I’m sorry you don’t like it but that’s seems to be the case given it’s been such an issue that a dedicated thread needed to be made.
Its implementation should have required much more research and caution. I would have defined this a breaking change.
Edit: can we agree that people who have poor vision and need a high contrast interface would find themselves having to revise all their dashboard just because?
1 Like
Sorry, miss read the post. Ignore me.
Probably because ignoring becomes a trend?
This is an open source project.
Dev people do it for free.
Community moderators do it for free.
People like you, like me who is sharing their solutions - do it for free.
Users do not like situations when smth is changed - and their complains are ignored.
Users do not like situations when they spent plenty of time to create a perfect HA setup - and suddenly it becomes broken due to some sudden breaking changes.
more-info with statistics - a good example.
Anything was made to restore the good old way? No.
So this is a trend - and it is frustrating. No wonder when people - being ignored - get irritated and express themselves emotionally.
11 Likes
I’m not trying to be offensive when I say this but you have a tendency to fly off the rails when you disagree with anything instead of replying with constructive feedback. Sorry, but volunteers don’t have to listen to feedback if they don’t like the way it’s presented to them.
8 Likes
Just your personal impression, like someone may find you not good enough in some cases.
But - finally there is a technical side which is more important than our feelings.
tbh: I don’t care much about the color changes in this release… at some places, I really like the idea … but on others… I don’t really know, if it is working as intended… 
Here’s a small example of my thermostats (Homematic IP device, integrated per Homematic (IP) local [custom component]…
All thermostats listed in an entity-list:
there’s no difference in the color - although, they have different states.
When I open the “more info” dialog, there are different Icon Colors…
But, the color depends on the “profile” - not on the state:
Idle (Auto) && Heating (Auto)
While the thermostats in profile (Heat) have another color - independend if they are heating or Idle:
So, I would recommend, the colors should be set by the state (Heating, Idle, etc) - and not by the selected profile.
At least, that would be more intuitive…
And: Why are the colors not reflected in the entities card, like it is the case for other entities?
(And no, I am not aware that I have used battery cards in this example)
3 Likes
it seems like that might be due to something overriding the colors? My thermostat always shows as red when set to heat mode in all the cards (like yours does in more-info). I agree, I used to use the color as an indication of if it is currently heating which is no longer possible
2 Likes
GUI changes always seem to cause a lot of anguish and understandably so as it’s the part that we all interact with on daily basis. This is just another repeat of what happened when the settings got moved around. Personally I feel there needs to be a lot more research before pushing these changes out to users.
Anyway, trying to be constructive and to find some sort of solution for the users it’s upset. Is there any way that we could have a template theme provided that we can load in configuratoin.yaml that restores the previous colour palette and then people can make modifications from there to suit themselves? This would save everyone reinventing the wheel to try and do the same thing.
Just my two thoughts.
3 Likes
Regarding the changed colors:
Again, I am just a user and only one personal opinion. But it feels like strange things like this are done (creating work for people who style their dashboards) but all the real problems are ignored.
More or less all (core) cards behave differently and often inconsistenly. Each has bugs that are never fixed and none are in any way streamlined.
The stack cards being a prime example where it is an absolute pain for a newbie to figure out how to style them because they have nothing in common with the other cards.
Maybe it would be better to gather the problems with the core cards ans fix those. Then add theming ability via UI. Right now it is a huge guessing game and cumbersome search using dev tools in browsers to figure out how to bend the cards without breaking them.
The basics of dashboards were a problem, not the colors 
The entire frontend now seems to primarily work because of card mods/external cards. Without those no layout or styling would work and many cards would show strange behavior on different devices.
6 Likes
Is that still applicable after this update, or has the documentation just not been updated to reflect the 2022.12 release?
I’m using like this and it is working fine:
- type: state-icon
entity: lock.vw_passat_door_locked
style:
'--rgb-state-lock-jammed-color': var(--rgb-amber-color)
'--rgb-state-lock-unlocked-color': var(--rgb-red-color)
'--rgb-state-lock-locked-color': var(--state-icon-color)
top: 90%
left: 35%
1 Like
That was updated for this release.
Hi All,
I’ve started to create an “old style” HA Dark theme.
Just create a new theme.yaml and copy this code:
home_assistant_old_style:
primary-background-color: "#111111"
card-background-color: "#1c1c1c"
secondary-background-color: "202020"
primary-text-color: "#e1e1e1"
secondary-text-color: "#9b9b9b"
disabled-text-color: "#6f6f6f"
divider-color: rgba(225, 225, 225, 0.12)
mdc-ripple-color: "AAAAAA"
state-switch-color: "#ffd700"
state-automation-color: "#ffd700"
state-cover-color: "#ffd700"
state-fan-color: "#ffd700"
state-light-color: "#ffd700"
state-binary-sensor-color: "#ffd700"
state-input-boolean-color: "#ffd700"
state-person-home-color: "#008000"
badge-person-not-home-color: "#636B75"
state-person-zone-color: "#800080"
state-climate-heat-color: "#800080"
state-climate-idle-color: "#000000"
app-header-text-color: "#e1e1e1"
app-header-background-color: "#101e24"
Change it theme under your user and enjoy good old HA colors.
Just started to work on it, so it will take a few hours.
But I guess you’ve got the idea.
7 Likes
The problem in my humble opinion:
during the “open smart home” event (or how this was called) - Paulus already showed some sketches, in which direction the UI will change.
at that moment, I just thought: "Oh please - not yet another ‘alexa / smart home app’ copy.
The problem:
Nearly all of them are using similar themes.
And - HomeAssistant is trying to follow a trend where “Design” overcomes functionallity.
And that is something, I really would question here…
The Team should provide the technical platform - but from UI, I would really love if the user could decide how the UI should look like.
I don’t want to loose options I do have now - just to get another app that’s looking like the Amazon Alexa App, or the Hue App…
I really love the opportunity, to get Information out from the Dashboard - and not only have controlls.
That’s one BIG advantage of HomeAssistant compared to other smarthome apps.
And Beleive me:
If HA will go in this direction - and Matter support will be rolled out on other platforms as well… there’s probably no need for having HomeAssistant, if I CAN do the same (with the same UI) within the other apps as well…
13 Likes