So, does that mean this is an expected outcome of speeding up the loading times, rather than a bug in 2024.5? If so, anyone experiencing this problem is left to rebuild their home assistant install from scratch and hope they are able to make it work like it did before, or they are stuck at 2024.4.4 forever…I’ve been through the logs and there isn’t anything that stands out, so it’s trial and error to fix.
It means that the integration with the thread safety bug needs to be fixed or disabled, as it is more likely to cause a problem than before. If you don’t know which integration is causing the problem, follow the instructions above.
Did you follow the instructions I posted above in 2024.5+: Tracking down instability issues caused by integrations ?
When I update to 2024.5 HASS won’t start, so I can’t use any features introduced in that version. When I enable debugpy in configuration.yaml it doesn’t produce any “RuntimeError: Non-thread-safe operation” errors under 2024.4.4.
Edit: I reinstalled 2024.5 with debugpy enabled. Also no errors. The system gets so far in loading and then just crashes…hard…the CLI stops responding, Samba stops working (I was opening the logs as text files since the GUI wasn’t working properly).
On 2024.4.4 and prior the system has been perfectly stable - no gremlins or random crashes.
Sounds like its a bad loop in an integration instead of a thread-safety problem.
Try starting up in safe mode and re-enabling custom integrations one by one until you hit the problem.
disabling “Dreame custom integration” solved the problem for me and several others.
Edit: It is possible to do that before that integration starts at the startup after hard reboot.
for info,
It was a success to go back to previous core version from HA supervisor.
And I have Dreame Vaccum Custom Integration installed.
I’ve tried this integration thinking I can start the vaccum through google assistant but it is not the case, so no problem to remove it !
Thanks for the quick and efficient help !
Same problem here. After updating to 2024.05.1, system will start but crash shortly after. 2024.05.0 was fine.
Had to revert to 2024.04 to get it running again. Upgrading to current 05.02 makes it crash again.
Any ideas?
There were many in the previous posts above including:
2024.5+: Tracking down instability issues caused by integrations.
Did you try any of those?
I just wanted to reiterate the problem may be with the most recent update. I tried refreshing my browser (i.e. chrome) but unable to reach HA via my Nabu Casa address either. If I recall I had a similar instance with an update and had to power down my RaspberryPi and back up again which fixed the problem (although I’m not comfortable doing this on a regular basis). Just thought the community should know. P.S. I do not have the Dreame Vac Integration installed.
I am having the same problem after updating to 2024.5.0. In my case it’s Zigbee2MQTT the responsible: Home Assistant crashes and reboots; then, after a few seconds (when Z2M starts), it crashes and reboots again.
I managed to quickly stop the addon shortly after one of the boots and deselect “Start on Boot”, but I don’t know what to do next.
I’ve tried updating Z2M (I was on 1.36.0-1 and updated to 1.37.0-1) but the problem persists.
@iway and @Emile31 how do you downgrade the HA Supervisor?
Thank you very much
Same problem (I think) and this situation is pretty messed up. The only nonstandard integration I have is frigate, so there’s no way an update should be so catastrophic. I can’t even load into safe mode, so I’m hoping I can even recover. What a disaster…
I have zigbee2mqtt running as well an suspect it being the culprit.
1 Like
zigbee2mqtt at current 1.37.1-1: HA hangs after start and is unusable.
With zigbee2mqtt disabled, all works smoothly and fast.
1 Like
Same here. Tried with Z2M v1.36.0-1 and v1.37.0-1.
Now who should responsible for a fix? Z2M or HA? I don’t know if I should post a issue on Z2M’s GitHub.
What’s your MQTT broker?
I have all of those components at those versions in my prod install currently and it runs like a screaming banshee. (way fast)
Mines Mosquito 6.4.0
Mosquito 6.4.0 here too.
Running on a RaspberryPi 3.
The pi3 only has 1 Gb memory. With the Zigbee2MQTT add-on running, it probably runs out of memory. You can try to increase the swap size.
1 Like
Still, it was working beautifully until the Home Assistant Operating System 2024.5.0 update
Update: apparently, disconnecting the coordinator, rebooting and plugging it back in solves the problem.
Read it in an issue in HAOS github, just tested, and worked.
Update #2: Rebooting the system with the coordinator plugged in causes the problem to return.
1 Like