History/energy/logbook/default_config fail to load on 2024.7.2

[mihaitaiosub]

The problem

I updated yesterday from 2024.7.1 to 2024.7.2 and I'm very disappointed. None of the reported problems have been solved, that is, the history that is missing starting at 04:00 and the restart that takes a long time. What's more, they have now appeared and other error messages after restarting HA several times, and the history of the entities does not appear at all.. I am attaching a printscreen here with what has appeared. So I downgraded to 2024.6.4, which works without problems. I really I don't understand, doesn't anyone test these updates before releasing them? I'm seriously thinking of not making any more updates from now on, because I'm already wasting a lot of time with this activity.

What version of Home Assistant Core has the issue?

2024.7.2

What was the last working version of Home Assistant Core?

2024.6.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[Floppe]

Same here, history and energy stops at nights. Shutting down or restart takes forever, so I guess something is in a locked state.

[bdraco]

Please download and post the log https://my.home-assistant.io/redirect/logs when running 2024.7.2

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (history) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `history` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign history` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

history documentation history source _{^{(message by IssueLinks)}}

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (energy) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `energy` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign energy` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

energy documentation energy source _{^{(message by IssueLinks)}}

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (logbook) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `logbook` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign logbook` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

logbook documentation logbook source _{^{(message by IssueLinks)}}

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (default_config) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `default_config` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign default_config` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

default_config documentation default_config source _{^{(message by IssueLinks)}}

[tsrz]

same here, history and energy stops at 4:11 since 2 days restarting HA fixes the problem until the next night

[Floppe]

Sorry for hijacking this thread. I have no logs from around 4:11, but the restarting issue could be seen here where recorder cannot shutdown, timeouts and SQLite states are rebuilt on next start. I simply let it run for a while and restarted from developer tools. Lot's a warnings and errors from other things not related to this, I think.

home-assistant.1.log home-assistant.log

[bdraco]

Sorry for hijacking this thread. I have no logs from around 4:11, but the restarting issue could be seen here where recorder cannot shutdown, timeouts and SQLite states are rebuilt on next start. I simply let it run for a while and restarted from developer tools. Lot's a warnings and errors from other things not related to this, I think.

home-assistant.1.log home-assistant.log

2024-07-11 08:59:55.011 WARNING (Recorder) [homeassistant.components.recorder.migration] Rebuilding SQLite table states; This will take a while; Please be patient!

It looks like you restarted before the table rebuild finished. Please check the log to make sure its done before restarting as otherwise it has to start the rebuild over.

Also you have A LOT of custom integrations blocking the event loop. That is likely the tip of the iceberg, and you should check to see if anything worse is going on https://community.home-assistant.io/t/2024-5-tracking-down-instability-issues-caused-by-integrations/724441 with debug mode

Using Home Assistant's built-in debug mode in 2024.5.x or later (preferred) Enabling asyncio debug mode at run time (preferred)

[tsrz]

hi,

since two days, all is ok with no change in my configuration ...

[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.