I’ve got several entities that get data from MQTT that report every 5 minutess, When I view the graphs, the text legend will show “1 hour ago” or more; but if I hover over the graph itself, the timestamp shown is current.
Is this “normal”?
Can you post screenshots describing what you mean?
This one illustrates it perfectly. The time I took this was 15:59:30
You see it says 24 minutes ago in the legend; but the time on the graph is 15:58
OK, the last point on the graph is “15:58:48”, and a time span = 24hrs.
Means - 25 minutes = ~1/48 part, and it could be a flat line in the end.
Are you asking why the “23 minutes ago” doesn’t match wherever you are pointing on the graph?
Oh, looked at your graph and missed your first part. Could it be that the state hadn’t changed in that 24 minutes? What does it say if you hover your mouse over that “x minutes ago”?
That 23 minutes ago is the last time the sensor updated, not where you are pointing on the graph.
Or are you asking how to have a sensor report “x minutes ago”?
It says last updated and last changed the same - both earlier than what I see hovering over the graph. I get last changed; but shouldn’t last updated really reflect the time HA saw an update?
As I said - the last part looks like a flatline & the last change looks like happened 25 minutes ago.
I am not following. Last-changed = time when a state was last changed. Last-updated - when any attribute or state was changed. In fact, some integrations renew “last_updated” even when nothing is changed but a physical state was retrieved from a physical device (even if no attrs & state have been changed). But anyway, last-updated has nothing with your graph.
Can you show us the 30 min from that point backwards in more detail? The way I read it, considering Ildar’s comment, is that the value you see now (at that point in time) was set 23 min ago and was unchanged during that period. There are meta attributes for sensors and one of them are last_changed. Others are last_updated and last_reported.
OK - that definition makes sense. As @parautenbach suggests, what I’m really looking for is “last reported”. I might suggest changing the “legend” to that, or at least including that in the “tooltip”
Minor note on that. Last week I was testing something in an integration that polls and noticed that the last_reported was updated even if the integration set the entity to “unavailable” (or even “unknown” by returning None).
I didn’t pay much attention at the time, and maybe integrations can have more control over that timestamp. Worth testing how the actual integration handles that.