Closed thomluther closed 4 months ago
Make sure you have read the issue guidelines and that you filled out the entire template.
If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a :+1: reaction to the issue description. Thanks! :+1:
Post a diagnostics bump file for any integration
Here is the HACS diagnostic dump file config_entry-hacs-efd0e4f2507410ebd7f65292d2d6b0ba.json
I really think it is a timing problem during restart. Today there was no problem during one restart, but again on another restart. The HACS reload once all is started never failed. I assume the hass object has not created the hass.data['integrations'] entry yet when HACS is querying it? File "/usr/src/homeassistant/homeassistant/loader.py", line 1307, in async_get_loaded_integration cache = hass.data[DATA_INTEGRATIONS]
KeyError: 'integrations'
So maybe a delay must be introduced, or proper error handling when hass.data.get(DATA_INTEGRATIONS) is None
It is not HACS that is requesting it, that is core.
And hass.data['integrations']
is initialized before any integration is loaded.
The current suspicion is that you have some custom integration that is messing with that.
https://github.com/emontnemery/home-assistant/blob/04072cb3c1a2447200b322043a89c89e7e39d8ac/homeassistant/bootstrap.py#L262
https://github.com/emontnemery/home-assistant/blob/04072cb3c1a2447200b322043a89c89e7e39d8ac/homeassistant/loader.py#L241
Can you try to remove constant_modifier
and then restart to see if that helps?
If it still is not working without that, can you post your logs from startup with debug enabled for custom_components.hacs
?
Hello This seems indeed to be related to constant_modifier which loads very early during startup. Its not really an integration, but a custom component that I use to modify some hard coded ZHA device timeouts for Aqara sensors since I did not get that to work with ZHA quirks.
I disabled the component and had no further errors on 2 restarts. Since that component is not maintained anymore, I'll have to see what to do with it and need to start research again how to reduce the ZHA device sensor timeouts otherwise...
Thanks for you assistance, I think this HACS issue can then be closed.
System Health details
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4345 Installed Version | 1.34.0 Stage | running Available Repositories | 1481 Downloaded Repositories | 54 HACS Data | okHome Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.04.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 234.7 GB disk_used | 26.2 GB healthy | true supported | true board | odroid-n2 supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (17.2.0), Studio Code Server (5.15.0), SQLite Web (4.1.2), File editor (5.8.0), Samba share (12.3.1), Home Assistant Google Drive Backup (0.112.1), Mosquitto broker (6.4.0), Whisper (2.0.0), ZeroTier One (0.18.0), Dnsmasq (1.6.0)Dashboards
dashboards | 5 -- | -- resources | 49 views | 21 mode | storageRecorder
oldest_recorder_run | 27. März 2024 um 21:56 -- | -- current_recorder_run | 9. April 2024 um 17:04 estimated_db_size | 1448.32 MiB database_engine | sqlite database_version | 3.44.2Checklist
Describe the issue
Since I upgraded to core 2024.3, I have issues during restart. Each time HACS does not load correctly, showing the extract from the log below. When I then reload the integration from the frontend, it reloads without error.
Could this be a timing issue that was introduced along with the boot improvements from core?
Reproduction steps
Debug logs
Diagnostics dump
No response