Description
The problem
Home Assistant is starting, not everything will be available until it is finished.
This message persists despite home-assistant being started for over 4 hours:
4df9771ddee4 homeassistant/qemux86-64-homeassistant:0.113.1 "/init" 24 hours ago Up 4 hours homeassistant
Something is getting stuck during startup and Home Assistant cannot official complete startup (see additional info for reasons I believe that)
Environment
- Home Assistant Core release with the issue: 0.113.1
- Last working Home Assistant Core release (if known): 0.112.x
- Operating environment (OS/Container/Supervised/Core): Linux/Docker/HASSIO
- Integration causing this issue: ???
- Link to integration documentation on our website: N/A
Problem-relevant configuration.yaml
I don't know if there is a specific section of configuration that applied to this...
Traceback/Error logs
There's nothing specific I can see from the logs, if someone wants to suggest things to filter or grep for, I'm happy to do that.
Additional information
Since updating to 0.113.1:
- ZWave integration doesn't seem to start the zwave network automatically when HA starts, I have to manually start it in /config/zwave
- None of my ESPHome devices update temperature sensor readings -- The value change, but history does not reflect the change and statistics sensors don't work
- Scripts with triggers with Home Assistant Start have not fired since upgrading to 0.113.1
- There are no notifications for components that failed to start
- There are no notifications for configuration errors