When looking in History, the state is shown as “On”, Off", “Unavailable”. I was fooled to use the Uppercase spelling in an automation trigger.
Either the history should use the correct casing or the state trigger should be made case insensitive.
Probably not going to happen. Lovelace makes things pretty, it’s what it is there for. This applies to other areas of the frontend too, like History and the Logbook.
Your example is a minor one. Device Classes can change the states 'on' and 'off' to all sorts of things.
If you want to know the state of an entity look in Developer Tools States.
1 Like
I understand fully and that my example is a minor one, possibly spawning into major changes. Or maybe just a note in the documentation.
I know that I can see the current state in Developer Tools State, but for earlier states I get kindoff directed to the History (In the UI), I now know to check the logbook or ignore the prettified History uppercase.
It’s by no means an issue for me any longer, just an improvement idea for user friendliness
Casing is only an issue for English speakers.
Those state names are actually translated so, for consistency, you are actually requesting to remove translation of state names.
I don’t have an opinion, but it’s highly unlikely to happen…
2 Likes
Thanks.
Changed to my native language and saw the translation… now back to english 
25 year old flashback, ‘Internet Explorer’ translated on the desktop. Somethings are best unseen
1 Like