Stuck Sensors. Rolling back to 2025.5.3 fixed

[haysdb]

The problem

I've been having a lot of issues with stuck sensors since installing 2025.6.0. Tried everything: restarting, rebuilding, rebooting, reloading integrations, clearing caches, restarting my browser, rebooting my computer, nothing worked. Finally rolled back to 2025.5.3 and the sensors starting working again. Multiple integrations were effected.

What do I mean by stuck? Dashboards were displaying old values. Clicking on a card to bring up more-info would show the stuck value in the header but history shows the changes. In the history chart the tooltip showed the stale value but the history showed the value changing.

What version of Home Assistant Core has the issue?

2025.6.x

What was the last working version of Home Assistant Core?

2025.5.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

More than one

Link to integration documentation on our website

No response

Diagnostics information

I saw nothing in the logs.

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[erkr]

I Think this relates to https://github.com/home-assistant/core/issues/146799

[haysdb]

I wasn't experiencing any slowdowns or high cpu use. This was the second time I had stuck sensors. The first time a reboot of the Pi got them unstuck. This time nothing I did got them unstuck until I rolled back to 2025.5.3. Maybe it was the full replacement of HA core rather than a specific version but I'm not inclined to re-install 2025.6.1 just yet. I'll wait a release or two before trying again.

[haysdb]

Well, this isn't a 2025.6.1 problem because it happened again with 5.3, so I re-installed 6.1 which fixed one sensor but multiple others are still broken.

What is stuck:

1. Dashboard Cards
2. The tooltip in the history graph

What is working:

1. states('sensor.xxxxxxx')
2. History graph

[Petro31]

Clear your frontend cache.

[erkr]

@Petro31 that was the first thing I tried 😉 But in my case only the history card loads delayed. And only the history cards populated by auto entities.

[Petro31]

@Petro31 that was the first thing I tried 😉 But in my case only the history card loads delayed. And only the history cards populated by auto entities.

I wasn't replying to you ;)

[haysdb]

Clear your frontend cache.

I clear frontend cache frequently.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.