First, I’m not sure I’m posting on the right category…
Second, I’m not sure the issue was not reported already, only that I haven’t found any info - which is weird as I ‘didn’t change anything’ I assume more people should have encountered it already…
Anyway, since moving to 0.86.* (I think but not 100% sure), the lovelace interface does not always reflect correctly the states of my sensors. For example it shows a zwave switch as ON while when opening the device popup UI (clicking the device on lovelace to see history and other info) it shows as OFF which is the real state. This happens a lot now. No way for me to know now the real state of devices without checking one by one. It also happens on my config made battery sensor - lovelace reports 98%, device itself reports 56%. Please see the following 2 print screens where the case is evident:
BTW, moving to …/states shows the correct status and going back to lovelace fixes temporarily the lovelace UI (so it reflects correctly). I couldn’t trace a trigger for this behavior.
Restarting solves only temporarily.
Clearing cookies and cache - done that now, let’s see if helps.
99.9% of the time it is an android chrome browser, saved as ‘app’ (you know, the save to desktop shortcut…).
When reported on this post - I took the print screens from a PC chrome browser, so it is not the platform…
@DavidFW1960, are you talking about the battery graph or the weather cards? I’m still playing with the different cards…
I’ve seen something similar. It can take a while to update the more info pop-up if there are large data downloads (to update history graphs) going on in the background.
DavidFW1960 No, it’s the same entity - on the lovelace interface you can edit the entity’s name inside the card - so as the whole card is of lights, I dropped the “Light - …” prefix. but the name on the zwave core.entity_registry is the “full” one. I guess it’s a legacy behavior of mine when learned how to manage correctly zwave naming from the pre-lovelace era (funny as all my experience with HA is 4-5 months, jaja)
tom_l My history collection is limited to 12 devices that are not too chatty.
I noticed another phenomenon (happened just now, after cleaning cookies and cache) -
When I switch off a light through Lovelace:
the actual light turns off
the toggle button on Lovelace turns off and then back on
opening the device detailed card - its status is off
It doesn’t happen always but now I noticed it and it explains my past time frustration about HA doesn’t always reflect the real state. Apparently it is not HA, only Lovelace…
It’s early days. It will get better. Lovelace definitely does need a bit of polishing. Try putting an input_select in a picture elements card if you want to see a real mess.
Jaja, sure! So important to raise the issues so we can validate it’s a general issue and then that the developers will attend them…
The question is if this forum is enough or do we need to report also on the GitHub account…
I know this is a pretty old post, but since a few weeks I have the exact same issue. After rebooting my Raspberry Pi the Lovelace dashboard works for a few hours and shows the correct state of the entities. But then suddenly it does not longer work properly. Means that when i click a switch button to turn off a lamp, the turns off but status does not change.
Can anybody help me with that?
kind regards
Turbokanne
I assume more people should have encountered it already…
