Persistent Issues with Home Assistant Update from 2024.2.x/2024.3.x to 2024.4.x

Installation
1

Home Assistant OS 12.1 on Intel NUC with 8GB RAm and 100GB SSD

Hi everyone,

I’ve been facing a recurring issue when updating Home Assistant from versions 2024.2.x/2024.3.x to any 2024.4.x versions. After the update, the system repeatedly indicates that it has not fully loaded, disabling automations and several home functions, like Zigbee-controlled buttons.

Interestingly, there are no significant errors in the Home Assistant Core Log. However, the Supervisor Log mentions minor errors (specifics currently unavailable), with the most notable one related to SQLite database not shutting down properly.

Here’s what I’ve tried based on forum advice:

  1. Attempted to repair the SQLite DB using sqlite3, but saw no improvement.
  2. Deleted the SQLite DB as suggested, which also didn’t resolve the issue.
  3. Reverted to version 2024.2.4 on OS 12.1, which works flawlessly.

Further attempts to update to versions 2024.4.1 and 2024.4.2 resulted in similar problems: the system takes about 10-15 minutes to start and functions initially but then fails after a few hours, displaying “Home Assistant is not fully started”.

I’ve been stuck on this issue for about 3-4 weeks and am desperately looking for any insights or suggestions.

Questions:

  1. Has anyone experienced similar issues and found a solution?
    2. Is there a way to update to an interim 2024.3.x version instead of the latest version offered?
  2. Any tips on how I can better diagnose these issues?

Thanks in advance for your help!

2

Try the upgrade again, when you encounter the above issue, go to Settings > System > Repairs > 3 dot menu (top right) > Integration Startup time.

That will give you an indication of which integration is causing the issue. I’m suspecting ZHA, but you’ll need to confirm.

3

Also check you are not low on disk space. Delete older backup files, especially large ones if they exist.

4

Thank you for this hint. This seems to be very helpful.

I found the command for updating ha to a special Build:
ha core update --version 2024.3.3

In this Moment I examine this build and how it works.
Afterwards I am going to update to the latest 2024.4.x.

I am using zigbee2mqtt.

I am saving my backups direkt on my NAS.
HA NUC computer still has 90GB free.
At this point I’m sure I won’t have a problem.

I am going to Update the addons, HA, HAOS step-by-step. Every time i build a Backup aftewrwards.
Maybe I have a long way to test, because I have to wait a lot of hours before updating the next Step.

Thank you at this point for the first point to analyze. I didn’t know this before.
I will come back later.
If any additional Hints available, I would be happy to read them.

5

The Problem still exitst unfortunately.

After a lot of hours it is restarting.

Is there anybody, who can read something in this log?
The caldav issue occours always, also the Version 2024.3 and older.

The Starttime of the Plugins are good or better as in 2024.3.x

Actual Version of this Log is 2024.4.3 on HAOS 12.1
It is installed direct on a intel nuc with 8GB and SSD of 100GB.

The Database seems to be a problem. But why?
I cannot believe, that the NUC is to slow. It is NO VM!

I point to this log-record:
The recorder backlog queue reached the maximum size of 305644 events; usually, the system is CPU bound, I/O bound, or the database is corrupt due to a disk problem; The recorder will stop recording events to avoid running out of memory

And I tried to delete this database - the issue will come back in approximately 12hours.

For information:
This LOG is everything from this day. I did not delete a row!
Strange, that gap between 6:56 and 11:06 :open_mouth:

2024-04-16 05:06:34.983 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration dwd_pollenflug which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.985 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration goecharger which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.986 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration dwains_dashboard which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.987 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration adaptive_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.989 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration fontawesome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.990 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.992 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration landroid_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.993 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration homematicip_local which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.995 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration bosch which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.996 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration xiaomi_cloud_map_extractor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.997 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:34.999 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration waste_collection_schedule which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:35.000 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration dwd which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:35.001 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration webrtc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-16 05:06:35.586 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2024-04-16 05:06:35.634 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=254 from 2024-04-16 02:43:41.696859)
2024-04-16 05:06:41.876 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-04-16 05:06:43.795 WARNING (ImportExecutor_0) [slixmpp.stringprep] Using slower stringprep, consider compiling the faster cython/libidn one.
2024-04-16 05:06:49.242 WARNING (ImportExecutor_0) [homeassistant.const] TEMP_CELSIUS was used from goecharger, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please report it to the author of the 'goecharger' custom integration
2024-04-16 05:06:49.256 WARNING (ImportExecutor_0) [homeassistant.const] ENERGY_KILO_WATT_HOUR was used from goecharger, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please report it to the author of the 'goecharger' custom integration
2024-04-16 05:06:49.273 WARNING (ImportExecutor_0) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from goecharger, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please report it to the author of the 'goecharger' custom integration
2024-04-16 05:06:49.283 WARNING (ImportExecutor_0) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from goecharger, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please report it to the author of the 'goecharger' custom integration
2024-04-16 05:06:51.367 ERROR (SyncWorker_2) [caldav] Possibly the server has a path handling problem, possibly the URL configured is wrong.
Path expected: /caldav/, path found: ['/caldav.php/'] Please raise an issue at https://github.com/python-caldav/caldav/issues or reach out to [email protected], include this error and the traceback and tell what server you are using.
Continuing, probably everything will be fine
2024-04-16 05:06:52.599 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.total_daily_energy (<class 'homeassistant.components.esphome.sensor.EsphomeSensor'>) is using native unit of measurement 'kW' which is not a valid unit for the device class ('energy') it is using; expected one of ['kWh', 'Wh', 'GJ', 'MWh', 'MJ']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+esphome%22
2024-04-16 05:06:52.787 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.pws_solar_radiation (<class 'homeassistant.components.template.sensor.TriggerSensorEntity'>) is using native unit of measurement 'W/m²' which is not a valid unit for the device class ('illuminance') it is using; expected one of ['lx']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+template%22
2024-04-16 05:06:52.788 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.pws_uv (<class 'homeassistant.components.template.sensor.TriggerSensorEntity'>) is using native unit of measurement 'UV Index' which is not a valid unit for the device class ('illuminance') it is using; expected one of ['lx']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+template%22
2024-04-16 05:06:58.082 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for ulanzi @ 192.168.1.71: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.71', port=6053))]: [Errno 113] Connect call failed ('192.168.1.71', 6053) (SocketAPIError)
2024-04-16 05:06:58.084 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for az-nsp @ 192.168.1.82: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.82', port=6053))]: [Errno 113] Connect call failed ('192.168.1.82', 6053) (SocketAPIError)
2024-04-16 05:07:00.604 WARNING (MainThread) [homeassistant.components.media_player] Setup of media_player platform dlna_dmr is taking over 10 seconds.
2024-04-16 05:07:05.631 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback Task.task_wakeup(<Future finished result=0>)
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
RuntimeError: Cannot enter into task <Task pending name='EntityPlatform async_add_entities_for_entry cover.homematicip_local raspberrymatic homematicip_local 20d53f3664f911219ab1ac13ec123cb8' coro=<EntityPlatform.async_add_entities() running at /usr/src/homeassistant/homeassistant/helpers/entity_platform.py:629> wait_for=<Future finished result=0> cb=[set.remove(), set.remove()]> while another task <Task pending name='Task-2761' coro=<Entity._async_process_registry_update_or_remove() running at /usr/src/homeassistant/homeassistant/helpers/entity.py:1504>> is being executed.
2024-04-16 05:07:29.654 WARNING (MainThread) [homeassistant.components.dlna_dmr] Failed connecting to recently alive device at http://192.168.1.95:8080/dd.xml: UpnpConnectionError("UpnpConnectionTimeoutError('TimeoutError()', None)", None)
2024-04-16 05:07:31.662 WARNING (MainThread) [homeassistant.components.media_player] Updating dlna_dmr media_player took longer than the scheduled update interval 0:00:10
2024-04-16 05:07:31.663 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.digitradio_110_ir_00226131fe0c_2 is taking over 10 seconds
2024-04-16 05:07:41.663 WARNING (MainThread) [homeassistant.components.media_player] Updating dlna_dmr media_player took longer than the scheduled update interval 0:00:10
2024-04-16 05:18:42.998 ERROR (MainThread) [homeassistant.components.shelly] Error fetching shht_temp_sauna data: Sleeping device did not update within 600 seconds interval
2024-04-16 06:56:07.331 WARNING (Thread-17) [pychromecast.socket_client] [MIBOX4(192.168.1.33):8009] Heartbeat timeout, resetting connection
2024-04-16 06:56:29.808 ERROR (Thread-17) [pychromecast.socket_client] [MIBOX4(192.168.1.33):8009] Failed to connect to service MDNSServiceInfo(name='MIBOX4-ab579765d533f227a8caa69637e00bd3._googlecast._tcp.local.'), retrying in 5.0s
2024-04-16 11:06:35.723 ERROR (MainThread) [homeassistant.components.recorder.core] The recorder backlog queue reached the maximum size of 305644 events; usually, the system is CPU bound, I/O bound, or the database is corrupt due to a disk problem; The recorder will stop recording events to avoid running out of memory
6

It looks like you might need to update your custom homematic integration.

7

Thank you.

In the last 24h it will work without hanging up.
I have installed the last 1.59.0.