I have been using HassIO since the beginning on a Raspberry Pi 4 4GB model. The unit uses the RPi4 power supply and has always been directly connected via ethernet into my router. The unit also has a dedicated static IP (set both on my router and on HassIO).
I’ve been running for half a year on this configuration and it’s been great. However, this past weekend I was gone and went to check the status of my lights and was not able to access HomeAssistant. I was able to log in to the Orbi and check and the Raspberry Pi was showing that it was not connected to the router (I only have 4 ethernet connections, so it was easy to check).
Came home the next day, could not access it whatsoever so I pulled the plug and let it reboot. Rebooted fine, but could not find any logs. I went in and updated everything (no auto-updates) so everything is new and updated and restarted. Went to bed last night, and woke up to it being unresponsive again. Tried going through SSH to see if I could find anything but I could not.
- The home-assistant.log file only shows information from the current boot, and since I restarted it this morning it had no logs
- I only run Phillips Hue lights (6 of them), my garage door, and a boolean switch to activate some MQTT sensors for use in Node-RED, so nothing too heavy
Already tried searching for this issue but only came up with threads that were created >2 years ago.
Any idea of what is happening here? Any tips on how I should debug this?
After the problem started a month ago, I went ahead and created a NodeRed automation to reboot my Pi everyday around 6PM. I have not encountered the problem of freezing/crashing since. While this is definitely not a permanent fix, it works for the time being until such a fix is deployed.