This has been going on for some time, without anything major changing on my end. HA will just reboot without any obvious cause. Here are some logs if anyone can figure out what might be happening.
2026-08-22 03:46:48.748 INFO (MainThread) [supervisor.resolution.check] System checks complete
2026-08-22 03:46:48.748 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2026-08-22 03:46:48.810 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2026-08-22 03:46:48.811 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2026-08-22 03:46:48.811 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
2026-08-22 03:59:15.555 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:15.558 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:15.564 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:15.764 INFO (MainThread) [supervisor.api.proxy] [d5369777_music_assistant] Home Assistant WebSocket API closed
2026-08-22 03:59:15.764 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:15.765 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:15.768 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:15.769 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:15.770 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:15.774 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:16.123 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-08-22 03:59:16.149 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-08-22 03:59:16.154 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-08-22 03:59:16.159 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-08-22 03:59:16.162 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-08-22 03:59:16.173 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-08-22 03:59:16.181 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
2026-08-22 03:59:16.188 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
2026-08-22 03:59:16.208 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
2026-08-22 03:59:16.213 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
2026-08-22 03:59:16.217 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
2026-08-22 03:59:16.251 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-08-22 03:59:16.254 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
2026-08-22 03:59:16.256 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-08-22 03:59:16.261 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-08-22 03:59:16.277 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API proxy running
2026-08-22 03:59:16.290 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
2026-08-22 03:59:16.294 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API proxy running
2026-08-22 03:59:16.297 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
2026-08-22 03:59:16.301 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_vscode
2026-08-22 03:59:16.312 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API proxy running
2026-08-22 03:59:16.313 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API proxy running
2026-08-22 03:59:16.317 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API proxy running
2026-08-22 03:59:16.329 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API proxy running
2026-08-22 03:59:16.364 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API proxy running
2026-08-22 03:59:16.366 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API proxy running
2026-08-22 03:59:16.368 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API proxy running
2026-08-22 03:59:42.647 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:42.648 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:42.653 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:42.672 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:42.672 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:42.673 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:42.673 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:42.674 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:42.674 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closed
2026-08-22 03:59:47.201 WARNING (MainThread) [supervisor.homeassistant.core] Watchdog found Home Assistant exited with code 1, restarting...
2026-08-22 03:59:47.271 INFO (MainThread) [supervisor.docker.manager] Starting homeassistant
2026-08-22 03:59:47.699 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2026-08-22 04:00:09.300 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2026-08-22 04:00:09.351 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2026-08-22 04:00:13.644 INFO (MainThread) [supervisor.homeassistant.api] Connected to Core via Unix socket /run/os/core.sock
2026-08-22 04:00:13.695 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='NOT_RUNNING', offline_db_migration=False)
2026-08-22 04:00:49.208 INFO (MainThread) [supervisor.homeassistant.core] Still waiting for Home Assistant Core to start...
2026-08-22 04:01:50.471 INFO (MainThread) [supervisor.homeassistant.core] Still waiting for Home Assistant Core to start...
2026-08-22 04:02:50.787 INFO (MainThread) [supervisor.homeassistant.core] Still waiting for Home Assistant Core to start...
2026-08-22 04:03:51.089 INFO (MainThread) [supervisor.homeassistant.core] Still waiting for Home Assistant Core to start...
2026-08-22 04:04:51.452 INFO (MainThread) [supervisor.homeassistant.core] Still waiting for Home Assistant Core to start...
2026-08-22 04:05:51.748 INFO (MainThread) [supervisor.homeassistant.core] Still waiting for Home Assistant Core to start...
One thing from the logs, only run VSCode server when you are using it. It takes a poop-ton of memory and if you are not editing, it is not helping you.
Okay, I will change that to not start automatically. I only have it to edit when needed.
HA runs directly on a Raspberry Pi 4 Model B 2019 Quad Core 64 Bit WiFi Bluetooth (4GB).
I also noticed that the upgrade 2026.7.4 to 2026.8.2 took my average CPU usage from about 5-8% to 15-18%. There are no other changes, but HA is using about 10% more CPU since then.
Random reboots with Rpi"s are generally psu issues or sd cards. Rpi’s can also only supply limited power via the USB ports, so anything plugged into the USB can sometimes have power dropouts. This is often the case with USB powered ssd’s they just stop working for a second or so.
It’s still a power supply, POE or not. If you have a couple of dongles in there or an SSD those are using power as well.
Possibly a powered USB hub would unload some of the drain on the main supply to see if it is the supply bumping the limit.
Except that the Supervisor OS isn’t crashing, so the Raspberry Pi isn’t rebooting. Only the Home Assistant container crashes, and the Supervisor restarts it. If the power supply caused it to crash, the whole thing would reboot. They both run from the SD card.
And I have the Raspberry Pi Power Supply Checker integration running which is showing no issues whatsoever.
So what do you have powered by the usb ports? A pi4 can only supply 1200ma across all the ports, that’s not each it is a total, if any of those fail due to lack of power it could cause the crash. A pi will not report lack of power on the usb ports.
But as you say its running off an SD card then that is the most likely cause of the crash.
A Nortek Zigbee dongle I’ve had for many years. Nothing else connected to it… Again, if the card or PSU were the issue, how would the Supervisor be available to initiate a restart of the HA container and write log entries?
If the system just popped and rebooted, the entire Supervisor OS would be offline.
The extract of the logs you have posted just show normal startup processes, so the problem must be deeper, hardware, or power, or somewhere else in the logs. You have excluded power in your replies, so poor connections, hardware faults such as overheating or device faults should be checked.
Are you monitoring CPU and drive statistics on an ongoing basis. Any peaks?
Is your crashes following patterns, such as usage or time based auromation? Triggers based on external events?
Other than VSCode, a known memory hog, what other apps and integrations do you have installed? Is everything up to date with patches? Software as well as firmware?
You haven’t said much about your setup and configuration.
I’ve disabled automatically starting VSCode. I do monitor CPU and memory, and with that not starting, the unusual 10% rise in CPU use went away. I’m back to about 5-8% CPU since doing that. Other than that, no rhyme or reason. I’ve had it reboot when clicking a dashboard link, or just found it rebooted in the morning.
The hardware is as I’ve said. An RPi4 with a POE adapter, powered by a Netgear switch. The only thing connected is the Nortek USB dongle. The whole system does not reboot, as the logs and Supervisor continue running.
I keep it pretty lean, with the next biggest thing being Music Assistant. My RAM is steady at about 60% used, but I have noticed a small trickle upwards from 55% at boot. No spikes in CPU or anything that I can see. Just random.
I’m up to 4 days since disabling VSCode, and it rarely went a week without it happening. Let me sit on it for a while and see if it recurs now. If it does, what logs would be the most helpful?
Maybe carefully revisit the two references I posted and share your story more fully for better quality focused help, using the forum </> formatting for readability please.
We’re volunteers, but resent playing games of twenty questions.