Skip to content
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

Closed
3 of 4 tasks
ildar170975 opened this issue May 16, 2024 · 7 comments
Closed
3 of 4 tasks

History & Logbook do not conform to "last-changed" #20813

ildar170975 opened this issue May 16, 2024 · 7 comments

Comments

@ildar170975
Copy link
Contributor

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

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

@ildar170975
Copy link
Contributor Author

Since this could be a core issue - here it is: home-assistant/core#117596

@silamon
Copy link
Contributor

silamon commented May 19, 2024

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.

@ildar170975
Copy link
Contributor Author

ildar170975 commented May 19, 2024

Did you restart Home Assistant at 00:37?

If you mean 17.05 00:37 - not.
Uptime graph, no reboots:
изображение

Anyway this is not a frontend issue

Well, the core issue was registered. No feedback))

@silamon
Copy link
Contributor

silamon commented May 20, 2024

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.

@silamon silamon closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2024
@ildar170975
Copy link
Contributor Author

Do you know what causes last-changed to be updated?
Is it a "state was changed & it is different" event - or is it a "update of state is called" event?
I mean - could the last-changed be updated even when a state is same?

@silamon
Copy link
Contributor

silamon commented May 20, 2024

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.

@ildar170975
Copy link
Contributor Author

Thing is that there were no reboots / reloading integrations... Will keep observing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants