Raspberry Pi 3 overheated and crashed

Hello guys,

I have been running Home Assistant on my thrusty old Rapsberry Pi 3 (or 3B, not sure) for a couple weeks now and until this weekend it all went as expected.

I have a pretty basic small setup, nothing special:

  • 5 Tuya light bulbs connected through official Tuya Cloud integration.
  • Logging some hardware data (cpu temp, ram usage, network usage, etc.)
  • DuckDNS.
  • 2 Garbageday integrations.
  • ESPHome with 1 device.

Like I said, it all worked pretty stable, until 2 days ago. Suddenly, HA wasn’t reachable anymore. Not from the app, not from a browser (directly by ip). I wasn’t at home at the time, so I couldn’t check the Pi right away what was happening.
When I came home, the Pi was hot af. It didn’t burn my finger, but I could not touch the CPU for more than 2 or 3 seconds before having to let go.
I pulled the power from the Pi, and connected the power again. HA loaded just fine, and it all seems to be working fine again.

After HA loaded up, I could see it was reading 70C CPU temp, cooling down slowly. So it must’ve been even higher before, while it was crashed/stuck. After a while, it stabilized at 45-46C, where it normally swings around.

I wonder what could have happened? At the time it crashed, I don’t believe I was doing anything with it. I didn’t even notice until next morning. If you look at the cpu temp log, it seems like it started heating up more than usual, and stopped logging at 52C. Does this perhaps sound familiar to anyone? I will add the log and some sensor graphs below in a minute.

Log (what am I doing wrong with the ‘’’ code block thing?):
’ ’ ’
2021-10-31 21:27:04 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration afvalbeheer 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
2021-10-31 21:27:04 WARNING (SyncWorker_1) [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
2021-10-31 21:27:04 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration afvalinfo 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
2021-10-31 21:27:08 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2021-10-31 21:27:08 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=63 from 2021-10-24 15:20:55.108321)
2021-10-31 21:27:28 WARNING (MainThread) [homeassistant.components.esphome] Can’t connect to ESPHome API for esp-dsmr (192.168.1.184): Error connecting to (‘192.168.1.184’, 6053): [Errno 113] Connect call failed (‘192.168.1.184’, 6053)
2021-10-31 21:28:11 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from HR-Router (192.168.1.1). (Mozilla/5.0 (Linux; Android 11; Mi MIX 2S Build/RQ3A.210905.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/93.0.4577.82 Mobile Safari/537.36)
’ ’ ’



Many people’s HA crashed yesterday morning around 1-2am at the change over from daylight savings time.


My own rp3b heat up from it’s usual 33 degree c.

There was an announcement by balloob on discord about this:

We encountered a daylight savings bug last weekend when Europe transitioned last weekend. A restart will resolve the issue. If you are yet to transition to a new summer/winter time, a fix is included in 2021.10.7 thanks to OttoWinter bdraco and emontnemery