[BUG] last_updated is incorrect · Issue #81069 · home-assistant/core (github.com)
[FR] please implement last_seen, as it is not possible to know when last data was received · Issue #81075 · home-assistant/core (github.com)
I have multiple integrations, some are zigbee, some BLE, some HTTP/cloud, some modbus-TCP…
And I have noticed that I can’t know when the last value was received, if it’s unchanged. I have no idea if the sensor is dead…
For example in the screenshot below, it says last updated 2 hours ago, when I know the sensor should send data every 10 seconds. In this case I have no way to implement a fail-safe timeout.
For example, I had an incident where my BLE climate sensor’s battery died and home assistant was completely unaware of it for quite some time. What happened is my heater went in to thermal runaway, which could have ended badly if I did not return home that day.
I understand that HA may be avoiding to log the same data over and over again to save disk space, but it should at least update the “last update” timestamp?! It could do it only in RAM, and write to disk every 10 seconds or so to save performance and disk wear, but I should still be able to see if any data is coming. Also I would like an option to log every value, even if it’s the same, for some corner cases, like data analysis, etc. I can afford a slightly larger disk.
Also this BLE sensor. Is it just reporting the same value, or is it dead? Or maybe the signal is weak and only goes through every 5 hours? How can I know?
And then there’s this. Sensor dead some time ago. Why is the graph still reporting the value of 18 %?
WTH, why isn’t this being discussed as a serious issue?