-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
History & Logbook do not conform to "last-changed" #20813
Comments
Since this could be a core issue - here it is: home-assistant/core#117596 |
Did you restart Home Assistant at 00:37? Anyway this is not a frontend issue as it is show as it is being received from core. |
Since it's a core issue, probably there's a reload of the state somewhere what causes the change to happen. We show the datetimes as how we receive them from core. |
Do you know what causes |
A restart of Home Assistant forced the last-changed to be changed even when the state is the same. Probably there are also other ways that result in the same, like reloading parts of the configuration, but there are more knowledge people to find that out that read the core issue tracker. |
Thing is that there were no reboots / reloading integrations... Will keep observing. |
Checklist
Describe the issue you are experiencing
There is a
device_tracker
.Here is it's current state:
Note that "last-changed" is "May 17, 2024 at 00:37:59".
Same may be got by
But here is a History - and the state was not changed since 23:55:
Same with Logbook:
And same is shown by DB Browser:
The last change of a state was at same 23:55:
Now I wonder - why the last-changed value is shown differently?
Describe the behavior you expected
explained above
Steps to reproduce the issue
as above
What version of Home Assistant Core has the issue?
2024.5.3
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
Chrome 124.0.6367.202
Which operating system are you using to run this browser?
Win10x64
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: