My home assistant instance keeps crashing and looking at the Home Assistant Core log I can’t seem to find anything interesting. I always run the latest versions of everything when an update becomes available but what you see below (from the Home Assistant Core Log) happens a lot:
At 08:33 - it finished rebooting the instance but no more entries occur until at 15:25, when I noticed it’s not working anymore and I reset the RPi again.
Configuration is RPi-4 with SSD disc attached. Any idea where I should be looking next?
^[[36m2025-04-29 08:33:46.669 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_reported[L]: entity_id=switch.living_room_jet_mode, old_last_reported=2025-04-29T08:33:16.515597+01:00, new_state=<state switch.living_room_jet_mode=unavailable; device_class=switch, icon=mdi:turbine, friendly_name=Living Room Jet mode @ 2025-04-29T08:33:16.515597+01:00>>^[[0m
^[[36m2025-04-29 08:33:46.669 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_reported[L]: entity_id=switch.living_room_display_light, old_last_reported=2025-04-29T08:33:16.517987+01:00, new_state=<state switch.living_room_display_light=off; device_class=switch, icon=mdi:wall-sconce-round, friendly_name=Living Room Display light @ 2025-04-29T08:33:16.517987+01:00>>^[[0m
^[[36m2025-04-29 08:33:50.002 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_reported[L]: entity_id=sun.sun, old_last_reported=2025-04-29T08:33:35.001207+01:00, new_state=<state sun.sun=above_horizon; next_dawn=2025-04-30T05:09:27.262302+00:00, next_dusk=2025-04-29T19:57:49.535279+00:00, next_midnight=2025-04-30T00:33:48+00:00, next_noon=2025-04-29T12:34:00+00:00, next_rising=2025-04-30T05:38:58.483717+00:00, next_setting=2025-04-29T19:28:17.140471+00:00, elevation=20.51, azimuth=87.68, rising=True, friendly_name=Sun @ 2025-04-29T08:32:49.988052+01:00>>^[[0m
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
^[[33m2025-04-29 15:25:29.817 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^[[0m
^[[33m2025-04-29 15:25:29.821 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors 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^[[0m
^[[33m2025-04-29 15:25:29.828 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea_dehumidifier_lan 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^[[0m
I think it’s 4Gb but I can’t get in at all anymore now. It dies about 3 minutes after I cycled power. The unit is 500 miles from me so I may have to wait until I travel back to figure out what’s going on as I don’t believe I can access anything from overhere.
Like Francis said above, you will need to look at home-assistant.log.1 to see the errors from before the crash.
A couple more observations:
You seem to have debug logging enabled - depending on your system, you might be flooding it with too many logs (at both a memory level and disk space level).
You have an SSD, so you will need to rule out power issues. The RPI4 might not be providing enough power to your SSD, especially if you’ve got other stuff plugged in to the Pi’s USBs. Try a powered USB hub to see if it fixes the issue.
Thanks @ShadowFist - I think the power is fine as I bought a high Amp power supply to rule that out some time ago. Logging: good observation. I switched that on to try to figure out what the issue is. I’ll try to switch that back off.
I seem to get 30 seconds after it boots to do something - after that it dies again.
The warnings about custom integrations (hacs, smartthinq_sensors, midea_dehumidifier_lan) could be causing instability. Try disabling them to see if the issue persists. Also, monitor system resources (CPU, RAM) on your RPi and check for any OS-level errors. Ensure your Home Assistant and system updates were successful, and consider rolling back to a backup if issues continue.
I think I have to revisit what @ShadowFist is eluding to: Power and spotted a few recommendations for this hub
SABRENT Powered USB Hub, 4 Port USB 3.2x1 5Gbps, USB 3 Splitter
So I’ll spend some money and take to Portugal next time I go there and keep rebooting until that happens. I can’t think of anything else what it could be.
Those warnings are standard and come up for each custom integration you have installed, every time you restart.
It’s just HA’s way of saying “don’t complain to us if these integrations cause you issues - we’ve got nothing to do with them”
I found out that my HA was crashing due to out of memory.
I have a large plex library, and (seemingly) too much for music assistant.
I found the tip in the ‘host’ logs, which show OOM killer shutting down processes. I also caught it running out of memory watching the system hardware screen.
So far, shutting down MA seems to have stabilized things.
Hardware: home assistant blue, odroid n2/n2+, 4 gig ram.
I changed from the Rpi 4 set up with external hdd to one of these:
Blackview MP60 Mini Desktop PC - Intel Celeron N5095 8GB 256GB WIN 11 Pro
It’s been super stable and has never crashed. It has a great all in one form factor and you can pick them up second hand. Just buy a new hdd to flash HA on to, set the BIOS to boot from hdd before swapping over the hdd and you are good to go.