History does not work after update to core-2024.10.3

Configuration
1

Hi! After migrating to core-2024.10.3 my history stopped working. Sensors show only the actual state and recent history. When I try to analyze the longer history using the “History” card, the cursor is endlessly spinning without showing anything. I did not manage to gather any clarifying logs.

I have discovered that multiple users reported this issue in the past. I seems to me that nobody was able to provide solid explanation and solution to this issue. Is it usually resolved during some bugfix release of HA core?

My configuration of HA system is here:

## System Information

version | core-2024.10.3
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.12.4
os_name | Linux
os_version | 6.6.54-haos
arch | aarch64
timezone | Europe/Prague
config_dir | /config

<details><summary>Home Assistant Community Store</summary>

GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
HACS Data | ok
GitHub API Calls Remaining | 5000
Installed Version | 2.0.1
Stage | running
Available Repositories | 1442
Downloaded Repositories | 6

</details>

<details><summary>Home Assistant Cloud</summary>

logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Home Assistant OS 13.2
-- | --
update_channel | stable
supervisor_version | supervisor-2024.10.2
agent_version | 1.6.0
docker_version | 27.2.0
disk_total | 28.0 GB
disk_used | 8.8 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization | 
board | green
supervisor_api | ok
version_api | ok
installed_addons | Studio Code Server (5.17.2), Tailscale (0.23.1), Advanced SSH & Web Terminal (19.0.0), Home Assistant Google Drive Backup (0.112.1), Firefox (1.3.2)

</details>

<details><summary>Dashboards</summary>

dashboards | 3
-- | --
resources | 3
views | 5
mode | storage

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | October 9, 2024 at 20:31
-- | --
current_recorder_run | October 19, 2024 at 15:19
estimated_db_size | 213.59 MiB
database_engine | sqlite
database_version | 3.45.3

</details>
2

Look in your logs for errors.

3

Hi! Thanks for the reply.

I have checked system logs. There was no related error there.

I shold be more clear on this one. When I wrote:

I did not manage to gather any clarifying logs.

I meant that I checked the system logs and did not see any error related to history.

The issue resolved itself miraculously.

Meanwhile, the issue resolved itself miraculously. When digging deeper, I have found out that the inaccessibility of history was probably caused by the inability of history integration to query data from the underlying storage DB.

Although I am happy the problem vanished, I have absolutely no clue, what actually happened. I would like to ask somebody more experienced to give me guidance where to look next time, how to debug such problems and how to get to the correct logs which clarify such problems. Thank you.

4

That means it was browser cache. Ie. You just needed to hard refresh your page

5

Interesting idea but I think that it is not correct solution. I was able to observe the same problem both on a laptop browser an in a mobile app.

6

Depending on the version you updated from, there might have been database updates that needed to run. Sometimes those take a while, and histories don’t work until they’re done.