Loading state history

Installation
1

After updating to core 2024-11-1 all my graphs are stuck in “Loading state history”.
I then made a “ha core update --version 2024.10.4” and the graphs loaded properly but i got a warning about a rtc component not found (one added in the failed relase).
I was told to retry installing the new version and did so with same result, but now the graphs are not working when roling back. So now I am really stuck with a not working system. What to do?

4 Likes
2

I have the same issue. Any help will be appreciated.

1 Like
3

After a day or so they started working again. Dont know why. Now I have installed a newer core update and the graphs still work.

1 Like
4

I am also experiencing an issue after upgrading from 2024-11-3 to 2025-1-0, where the state history is stuck on “Loading state history…”. I have checked the logs but nothing out of the ordinary there. Also, I deleted the home-assistant_v2 database file but that didn’t change anything for the better.

Any tips how to troubleshoot this further?

2 Likes
5

I have seen a couple of times where the graphs took a very long time to get up after updating the core version, but until now they have com back up every time. SO maybe patience is the best solution.

1 Like
6

is the problem database related?

I have the same problem sometimes.

And if yes, would changing to Maria db make a difference?

7

I found that the problem could be browser related.
If you reboot, or use a different machine, then it looks like the state history loads fast again.

8

I switched from Firefox to Chrome for testing purposes and the delay went away completely. So it definitively is browser related.

edit:

Same thing happened now with Chrome. After one week or so, I have now slow state history loading…

Just like in Firefox it gets fixed by closing the window and re-opening it.

I guess thats an easy enough fix.

9

If you’re leaving the browser window open for a week, that’s bound to happen.

The websocket message list will be huge and possibly timing out, since it’ll keep a message for every state change that occurred since you opened your browser.
Closing the browser shouldn’t be necessary - a refresh should fix it.

1 Like
10

I think I did as a reflex, but will definitively try that first.

11

not a browser issue- it happens on the IOS App too. Waiting 10mins now for the history to load- meanwhile I see the records updating every thirty seconds. I’m only asking for 24hours of data.
I checked the CPU usage and it hovers around 5% all the time- on a raspberry 5 8G.