Lovelace History Graphs stop updating after some timeout?

Hello all,

I was having a similar problem on sqlite, but that turned out that sqlite just got locked. So I successfully moved to MariaDB. Now it’s slightly different–

I use latest version of Chrome, I keep HA running in a tab. It seems at some point, the history graph just stops updating and instead shows a flat line of the last value;
lost%20data

But, HA is definitely still receiving signals and recording properly, because if I look at my homepage from any other device, or just refresh the tab in chrome-- I get all the data that was missing;
lost%20data%20refreshed

This is a huge annoyance to me. I’ve tried different values of update rate in HA (which seems to always just go back to 24hrs / 0 update rate every time i hit edit?) , but nothing seems to stop this problem. I am about to find a solution that just auto-refreshes my tab in my browser every 5 minutes. But all the other switches/lights on my homepage reflect perfectly even if the graph has stopped. And, it occurs the exact same time to ALL history graphs on my homepage ( I have 4 total right now). So, I feel like there is someting I’m missing? Why does it work for a while but stop eventually? Is there a time-out somewhere I can adjust?

I want to eventually move to graphana etc. But I note that Node-Red iframe graphs DO NOT have this problem – so maybe I’ll just start showing the info via Node-red instead of native in lovelace history graph.

Anyone have input? Why is this happening?!

Here’s one to consider:

https://chrome.google.com/webstore/detail/auto-refresh/ifooldnmmcmlbdennkpdnlnbgbmfalko

To add some information to this issue-- I started running the page in Firefox and so far ( several hours today), I havent seen it “hold up” yet. Maybe what I’m dealing with is just a browser issue?

I will continue to explore that avenue since I wasn’t able to find any problems like this mentioned out there. I’d think it would be a lot more common if it was an HA or lovelace thing