I mainly use my HA for monitoring my home solar PV and battery via a custom integration, I also log temperature and power consumption data from a variety of temp sensors and smart plugs. I have a subset of all these sensors being logged to MariaDB and InfluxDB simultaneously. I’m seeing a weird issue where Lovelace cards that show values seem to be stuck on some past value, which approximates to when I installed the update to Operating System 10.3 earlier today. However the correct values are still being logged and cards that show graphs are responding correctly. So for instance the current PV Power value looks like this:
It’s stuck showing a value from around midday (hence the 4 hours ago) but the trace has continued.
I also have a Grafana dashboard running off InfluxDB and everything seems to be working just fine there.
So far I’ve tried restarting the whole HA OS, and also re-starting the MariaDB add-on, neither of which helped. If I create new cards with numerical entities (Entity, Glance, Gauge) in Lovelace they get the “stuck” value of the entity, but new Plotly cards for instance show the expected traces and update as expected. If I create a new Statistics card I also get the expected statistics value, they don’t appear to be “stuck”.
I’ve looked through all the logs and cannot see any errors relating to this (I have a long running modbus error but that’s been there for weeks and has not changed).
Anyone any idea what’s gone wrong and how I can fix it? I don’t understand how one type of card is seeing the latest values and updating, but another type of card is just completely stuck on a past value!