Is unavailable now hard-coded transparent or is there a variable for this? Though you have written in one of the according github entries, that this will be configurable.
Found it
We are preparing a fix for that. Inactive and unavailable state will be two different colors on the dashboard, more-info, logbook, history. It will be 2 shades of grey and will be configurable with themes.
Conflicts with âtransparentâ.
Thatâs clear. But my question was about the announced configuration/promised options.
Yes, as a first solution we thought about 2 shades of grey but just create hole in the history timeline appears to be a better solution. Inactive color is configurable but not unavailable as itâs an empty slot in the timeline.
Thatâs punny
Can you comment my remarks?
Maybe already asked somewhere.
Since the latest âcolorâ update my nefit climate entity is always red instead of blue. Itâs always red because Itâs always âheatingâ. But technically it is not. During the night e.g. it sets back to 19°C and during the day 20.5°C. When the target tempvis met it stops hearing but since the climate entitiy is always set, to 19 or 20.5 it is now always red đ¤ˇ.
How could that be the case and above all, how can I go back to original color? Or change the behaviour of the color? Like it is only red when rhe system status is heating and not standby?
Seconding this.
I realize that technically the âstateâ of the Thermostat is âHeatâ, but the thing I actually care about is if the furnace is actually heating at the moment. I donât care whether Iâve got it set to Heat, Cool, or Heat/Cool: I want to know what operation is currently being performed, at a glance.
As it stands, the current change is a strict downgrade in experience from how it used to work.
Actually, I meant graphs for sensors w/o UoM.
Currently for 2022.12.1 we have this:
1.The sensor was created at ~00:20, the graph show âemptyâ (i.e. âtransparentâ) line for the period when this sensor did not exist.
2.After some time the sensor became âunavailableâ; currently it is same color as for âoffâ - so letâs imagine that it will be âtransparentâ in the next HA release.
3.HA was rebooted between 00:25âŚ00:26.
At that time the sensor became âunknownâ:
4.Then the sensor was deleted.
Then the sensor was added again - so we see âunknownâ in the graph:
Currently this picture seems rather logical (if not talking about same color for âunavailableâ, âunknownâ & âoffâ and that âgap with unknownâ).
Because of your changes now we will see no differences between âunavailableâ & âdoes not existâ states.
Will it be SAME color as âoffâ?
Wrong, if you mean history-graph.
Here is a screenshot of some previous untouched HA version:
I am generally fine with the color changes as implemented. I do, however, have âalertâ entities that when âidleâ are appearing as red. No idea what colors appear when âonâ or âoffâ. I only see two variables in the theme styles with alert in the name (ârgb-state-alert-color: var(ârgb-red-color), --rgb-state-binary-sensor-alerting-color: var(ârgb-red-color); )
Just curious if Iâm missing something here, or have something misconfigured somewhere, or if this needs to be adjusted in the actual HA code â but it seems like an âidleâ alert shouldnât be default red?
Example:
alert:
smoke_basement:
name: Smoke Alert in Basement
entity_id: sensor.basement_smoke_co_status
state: 'smoke'
repeat:
- 5
- 10
- 130
skip_first: false
notifiers:
- hass_text
co_basement:
name: CO Alert in Basement
entity_id: sensor.basement_smoke_co_status
state: 'CO'
repeat:
- 5
- 10
- 130
skip_first: false
notifiers:
- hass_text
That is being discussed here already: State color of thermostat entity based on wrong attribute. ¡ Issue #14608 ¡ home-assistant/frontend ¡ GitHub
Is it a binary sensor of some particular class?
Could you give an example?
hugely appreciate the lengths the frontend team now seems to adjust some color oddities in the original 2022.12 effort.
Must confess I am a bit underwhelmed by PR #14710 on the unavailable color to be transparent. To me transparent looks like a rendering bug. As if the graph is broken.
There is not even a state named in that screenshot, so it doesnât indicate with text what is the matter. We have nu clue at all.
I can not understand this design decision, was there was a nice example by Paul how these unavailable/off/on colors were set to very light grey/grey/active color (cant find the screenshot right now)
there is not a single other situation in HA where âtransparentâ indicates anything, other than a bug/issue.
How would this be sane design, are we sure this isnt a fluke?
(checking the PR now)
and yes, unfortunately this appears not to be a fluke. Though I see the exact same wording written in doubts I used aboveâŚ
now even read:
o dear.where is this going?
How have you established this âappears to be a better solutionâ?? In the last 3 days that is, where you said:
At least indicate âunavailableâ, but preferably bring back the light greyed background to that. Seems universal, so why be purposely different here.
--rgb-state-unavailable-color: var(--rgb-light-grey-color);
please.
At least two vars should be added - for unavailable & unknown in history-graph.
I guess we have to agree there, because now, as it is intended, âoffâ will be the same as âunknownâ.
Which ofc is so not what the backend team states at any opportunity. Check the latest changes made to the binary entities, that have those 4 states now⌠And that was explicitly and purposely done, because being âunknownâ is not off/on. Itâs a pain, but hey, it kind of is true.
And now our frontend tells another story: never mind the entity is unknown, weâll show it as off. It is plain incorrect.
I would really use a very light grey color for unavailable entities - such as: #F8F8F8 rgb(248,248,248) for exampleâŚ
Or, at least, keep the text based information âUnavailableâ - so that the gap does make any sense at all⌠
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â