I tried already to upgrade from HA Core 2024.10.4 to 2024.11 and now lately to 2024.11.2. In each case HA assistant is not starting properly and obviously gets stuck while starting the recorder. I needed to restore always the “old” 2024.10.4 again to keep a productive system.
Do other users see the same issue? Any support for this issue?
Please share your logs after the update. Settings → System → Logs.
Exactly the same issue here. Just updated. This is the log I have:
2024-11-20 10:53:29.201 WARNING (SyncWorker_0) [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-11-20 10:53:29.215 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ecoflow_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-11-20 10:53:29.228 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nordpool 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-11-20 10:53:29.234 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ecoflow 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-11-20 10:53:29.244 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration energyscore 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-11-20 10:53:40.053 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
2024-11-20 10:54:29.886 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('recorder', None): 3524298.198100731}
2024-11-20 10:55:29.960 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('recorder', None): 3524298.198100731}
2024-11-20 10:56:30.026 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('recorder', None): 3524298.198100731}
2024-11-20 10:57:30.096 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('recorder', None): 3524298.198100731}
2024-11-20 10:58:30.053 ERROR (MainThread) [homeassistant.setup] Setup of 'recorder' is taking longer than 300 seconds. Startup will proceed without waiting any longer
2024-11-20 10:58:30.169 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('hassio', '8c5725a63f7e08e798e7eea259032005'): 3524598.30652694}
2024-11-20 10:58:43.900 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.servis_import (<class 'homeassistant.components.template.sensor.SensorTemplate'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total_increasing', 'total'; 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-11-20 10:58:43.909 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of 'history'. Setup failed for dependencies: ['recorder']
2024-11-20 10:58:43.909 ERROR (MainThread) [homeassistant.setup] Setup failed for 'history': Could not setup dependencies: recorder
2024-11-20 10:58:43.909 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of 'energy'. Setup failed for dependencies: ['history', 'recorder']
2024-11-20 10:58:43.909 ERROR (MainThread) [homeassistant.setup] Setup failed for 'energy': Could not setup dependencies: history, recorder
2024-11-20 10:58:43.924 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of 'logbook'. Setup failed for dependencies: ['recorder']
2024-11-20 10:58:43.924 ERROR (MainThread) [homeassistant.setup] Setup failed for 'logbook': Could not setup dependencies: recorder
2024-11-20 10:58:45.475 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.emoncms_skorsten (<class 'homeassistant.components.emoncms.sensor.EmonCmsSensor'>) took 1.525 seconds. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+emoncms%22
2024-11-20 10:58:49.346 ERROR (MainThread) [homeassistant.components.notify] Failed to initialize notification service slack
2024-11-20 10:58:49.417 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'energyscore' calls async_forward_entry_setup for integration, energyscore with title: VVB and entry_id: 01J6AGQ20JNPZP08CEEZVKDDV5, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/energyscore/__init__.py, line 31: await hass.async_create_task(, please create a bug report at https://github.com/knudsvik/energyscore/issues
2024-11-20 10:58:51.247 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.ecoflow_energi_ut (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using state class 'total_increasing' which is impossible considering device class ('power') it is using; expected None or one of 'measurement'; 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+utility_meter%22
2024-11-20 10:58:51.248 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.ecoflow_energi_in (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using state class 'total_increasing' which is impossible considering device class ('power') it is using; expected None or one of 'measurement'; 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+utility_meter%22
2024-11-20 10:58:52.386 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of 'default_config'. Setup failed for dependencies: ['energy', 'history', 'logbook']
2024-11-20 10:58:52.386 ERROR (MainThread) [homeassistant.setup] Setup failed for 'default_config': Could not setup dependencies: energy, history, logbook
2024-11-20 10:58:54.437 ERROR (MainThread) [homeassistant.components.sensor] slack: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 728, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1302, in async_device_update
await self.async_update()
File "/usr/src/homeassistant/homeassistant/components/slack/sensor.py", line 50, in async_update
if _time := (await self._client.dnd_info()).get(ATTR_SNOOZE):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/slack/web/base_client.py", line 226, in _send
return SlackResponse(**{**data, **res}).validate()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/slack/web/slack_response.py", line 176, in validate
raise e.SlackApiError(message=msg, response=self)
slack.errors.SlackApiError: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'missing_scope', 'needed': 'dnd:read', 'provided': 'chat:write'}
2024-11-20 10:58:54.770 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.12/site-packages/stringcase.py:247: SyntaxWarning: invalid escape sequence '\W'
return re.sub("\W+", "", string)
2024-11-20 10:58:54.894 ERROR (MainThread) [homeassistant.components.climate] Platform esphome does not generate unique IDs. ID 0C:B8:15:F8:62:40-climate-vp_termo already exists - ignoring climate.vp_termo
2024-11-20 10:58:54.894 ERROR (MainThread) [homeassistant.components.light] Platform esphome does not generate unique IDs. ID 0C:B8:15:F8:62:40-light-ili9341_display_backlight already exists - ignoring light.ili9341_display_backlight
2024-11-20 10:58:55.251 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.wifi_signal_percent (<class 'homeassistant.components.esphome.sensor.EsphomeSensor'>) is using native unit of measurement 'Signal %' which is not a valid unit for the device class ('signal_strength') it is using; expected one of ['dBm', 'dB']; 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-11-20 10:58:57.502 ERROR (MainThread) [homeassistant.components.home_connect.switch] An error occurred: {'description': 'HomeAppliance is offline', 'key': 'SDK.Error.HomeAppliance.Connection.Initialization.Failed'}
2024-11-20 10:58:58.006 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-radiation @ x.y.x.237: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='x.y.x.237', port=6053))]: [Errno 113] Connect call failed ('x.y.x.237', 6053) (SocketAPIError)
2024-11-20 10:59:01.665 WARNING (MainThread) [homeassistant.components.generic_thermostat.climate] The climate mode is OFF, but the switch device is ON. Turning off device switch.shelly_mang1_switch_1
2024-11-20 10:59:30.157 ERROR (MainThread) [homeassistant.components.shelly] Error fetching Ismaskin data: Error fetching data: DeviceConnectionTimeoutError(TimeoutError())
2024-11-20 10:59:54.889 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-kontor-display @ x.y.x2.128: Timeout while connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='x.y.x2.128', port=6053))] (TimeoutAPIError)
2024-11-20 10:59:54.897 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-vp-display @ x.y.x.239: Timeout while connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='x.y.x.239', port=6053))] (TimeoutAPIError)
2024-11-20 10:59:54.897 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-vp-display @ x.y.x.239: Timeout while connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='x.y.x.239', port=6053))] (TimeoutAPIError)
2024-11-20 10:59:54.899 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-ledring @ x.y.x.228: Timeout while connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='x.y.x.228', port=6053))] (TimeoutAPIError)
2024-11-20 11:00:06.153 ERROR (MainThread) [homeassistant.components.shelly] Error fetching Sadelkammare Frys data: Error fetching data: DeviceConnectionTimeoutError(TimeoutError())
1 Like
I tried it again to move from 2024.10.4 to 2024.11.2 and the following log entries are created:
Home Assistant Core
2024-11-21 15:16:26.515 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration presence_simulation 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-11-21 15:16:26.551 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dwd_weather 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-11-21 15:16:26.572 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration victron 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-11-21 15:16:26.585 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration mbapi2020 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-11-21 15:16:26.592 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sun2 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-11-21 15:16:26.595 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration solcast_solar 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-11-21 15:16:26.640 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sunspec 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-11-21 15:16:26.657 WARNING (SyncWorker_0) [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-11-21 15:16:26.682 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration portainer 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-11-21 15:16:26.699 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nodered 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-11-21 15:16:26.735 WARNING (SyncWorker_0) [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-11-21 15:16:39.365 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
2024-11-21 15:17:29.900 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {(‘recorder’, None): 141812.039567657}
2024-11-21 15:18:29.983 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {(‘recorder’, None): 141812.039567657}
2024-11-21 15:19:30.078 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {(‘recorder’, None): 141812.039567657}
There are no other issues shown in the system. If I skip the recorder, HA starts incomplete and e.g. all Energy data is not available anymore. It is the first time that I have a serious issue to update the HA Core part.
Does recorder start in safe mode? Just to eliminate side effects from any of your custom integrations?
You are using a SQLite-Database? No separate database like MySQL, MariaDB or Postgres?
with SQLite, does recorder start when you stop HA, rename home-assistant_v2.db and start HA. Of course this builds a new database, but this would check if recorder does not start because of a corrupt database file
how do I force the safe mode?
Actually I use the HA OS thus I never installed the SQL myself. Where can I easily check on the database?
How can I stop HA and rename the DBS file?
I am familiar with linux systems etc. but spontanuously never touched the console fo the HA OS. Thus I am lost if I see this screen how get to the ground.
ok, I figured out how to start in safe mode.
Settings > System > Restart Home Assistant (top right) > Restart Home Assistant in safe mode .
And I figured out that I only need to enter ha core stop/start in the console of the HA OS.
But then I am lost with this command interpreter how to move around in the system to find the DBS file and to rename it.
I installed the SQLlite browser from the add-ons.
The tables structure looks like this, since there is an SQLlite table inside, I assume that SQL lite is also running on the OS.
One step after another? Any luck with recorder in safe mode?
I’m running HA OS only on a test system, my main system is HA Core in python venv. Thus I’m struggeling a bit in how to access the file system, that’s different in HAOS.
Do you have the Samba Share Addin installed and configured? This would give you access to the filesystem, the database is in folder config.
And… before doing all these things… you do have a backup?
My HA is running on a proxmox environment and of course backups are available. But I do not have a test system installed.
Thus, I cannot stop HA currently since it needs to control my energy system in high price hours 
I will try it later tonight.
Please answer the question.
Does your recorder start correctly when you restart into safe mode?
I was now able to do further testing:
a) After I executed again the upgrade from 2024.10.4 to 2024.11.2 it took a long time until the system was in the situation that I was able to restart in safe mode
b) safe mode start afterwards created the same error messages again
The log file size even exceeds the limits of posting something here.
yes, no complains
Should I know replace the db file? It would be a pitty since I have massive Energy data stored here that I would loose. I have to check how much is already transferred to the influx side.
As a test:
Copy the database file off your system so you have a backup off it (/config/home-assistant_v2.db)
Delete the database file from your system and restart.
If the system starts normally (it should create a new empty database) then you know there is an likely a corruption issue with your database.
Your options from there are to either say goodbye to your data and start afresh with the empty database or copy the file back to the system (and restart) then search the forum for database repair topics. Some people have had success with simple repair commands.
ok this worked indeed, thanks to guide me through now 
Looks that the db file was corrupted. Not sure why this happened.
Unfortunately the energy data history is to a certain extend now lost.
Preserving all this energy data if such issues pop up is still a weak point of the system.
As I said: