Raspberry pi crashing

Configuration
1

Hi,

I am very new to Home Assistant and tried to install it now twice on a raspberry pi 4B.

First try on an SD Card according to the instructions. Everything went well so I set up all my devices (A lot of stuff including several Tado in all rooms), then I installed Mosquitto Broker and a bit later home assistant was not reachable anymore.

Second try exactly the same but this time on a USB SSD and same thing. Now I connected a screen to see what’s going on and all I see in this color splash screen.
The power supply is the official Raspberry one with 15watts.

Any idea what’s happening?
What am I doing wrong?

Thanks in advance.

Best,
Lucas

2

Welcome! I’m guessing that you read

So, is there anything in the logs?

3

Mhhh I looked into it but I got the impression that I am unable to read the logs if the system doesn’t start anymore at all. Is there any way to get into the logs directly on the drive?

4

The logs can be found in the homeassistant directory. They are:

home-assistant.log
home-assistant.log.1
home-assistant.log.fault

.log is the current log file. .log.1 is the previous log file.

You should be able to read your SD or SSD from another computer to check these files.

5

Thanks for that. Unfortunately I couldnt find any *.log files on the drives. In Windows it only shows one partition with no log folder. I then installed Raspberry OS to check with Linux which was also successful but then in the logs folder are only two files *. journal.

I searched .log, .log, home-assistant and got no results on any of the partitions :frowning: I guess I am doing something wrong

6

Sorry, for Windows, you will need Linux Reader to read the SD card.

Once installed, you can drill down to /mnt/data (hassos-data) → supervisor → homeassistant

Then you can extract the home-assistant.log and home-assistant.log.1 files.

I would also suggest starting from scratch with a fresh install of Home Assistant then immediately going to Settings - > Add-on and installing the File editor add-on. This will allow you to read the log files when HA is booted to ensure that the fresh install is ok. If it is, you can start adding your integrations and devices one-at-a-time and recheck the logs after each addition to see if everything is ok.

7

Thanks a lot, now I found it. No Idea why the search didnt work but with your help I found it. Since I just started one till it crashed and didnt turn on I only have text in the .log file:

> 2024-01-27 19:05:29.643 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: hassio, hardware, cloud
> 2024-01-27 19:09:36.719 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from pixel-8.lan (192.168.86.189). Requested URL: '/auth/token'. (Home Assistant/2023.12.4-11898 (Android 14; Pixel 8))
> 2024-01-27 19:19:07.585 WARNING (Thread-5) [pychromecast.socket_client] [Wohnzimmer(192.168.86.24):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:19:07.591 WARNING (Thread-7) [pychromecast.socket_client] [Home group(192.168.86.24):32187] Heartbeat timeout, resetting connection
> 2024-01-27 19:19:07.593 WARNING (Thread-10) [pychromecast.socket_client] [Kitchen display(192.168.86.102):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:19:07.595 WARNING (Thread-6) [pychromecast.socket_client] [Tv(192.168.86.24):32223] Heartbeat timeout, resetting connection
> 2024-01-27 19:19:07.607 WARNING (Thread-8) [pychromecast.socket_client] [Wohnzimmer TV(192.168.86.42):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:19:07.608 WARNING (Thread-9) [pychromecast.socket_client] [Party(192.168.86.24):32101] Heartbeat timeout, resetting connection
> 2024-01-27 19:19:07.610 WARNING (Thread-4) [pychromecast.socket_client] [Hallway Wifi(192.168.86.158):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:19:11.202 ERROR (Thread-5) [pychromecast.socket_client] [Wohnzimmer([::ffff:c0a8:5618]):8009] Failed to connect to service ServiceInfo(type='host', data=('[::ffff:c0a8:5618]', 8009)), retrying in 5.0s
> 2024-01-27 19:23:02.078 WARNING (Thread-10) [pychromecast.socket_client] [Kitchen display(192.168.86.102):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:23:02.085 WARNING (Thread-9) [pychromecast.socket_client] [Party(192.168.86.102):32101] Heartbeat timeout, resetting connection
> 2024-01-27 19:23:02.100 WARNING (Thread-5) [pychromecast.socket_client] [Wohnzimmer(192.168.86.24):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:23:02.108 WARNING (Thread-7) [pychromecast.socket_client] [Home group(192.168.86.24):32187] Heartbeat timeout, resetting connection
> 2024-01-27 19:23:02.114 WARNING (Thread-4) [pychromecast.socket_client] [Hallway Wifi(192.168.86.158):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:23:02.126 WARNING (Thread-6) [pychromecast.socket_client] [Tv(192.168.86.24):32223] Heartbeat timeout, resetting connection
> 2024-01-27 19:23:02.136 WARNING (Thread-8) [pychromecast.socket_client] [Wohnzimmer TV(192.168.86.42):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:23:05.700 ERROR (Thread-5) [pychromecast.socket_client] [Wohnzimmer([::ffff:c0a8:5618]):8009] Failed to connect to service ServiceInfo(type='host', data=('[::ffff:c0a8:5618]', 8009)), retrying in 5.0s
> 2024-01-27 19:28:54.212 WARNING (Thread-10) [pychromecast.socket_client] [Kitchen display(192.168.86.102):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:28:54.221 WARNING (Thread-7) [pychromecast.socket_client] [Home group(192.168.86.24):32187] Heartbeat timeout, resetting connection
> 2024-01-27 19:28:54.221 WARNING (Thread-9) [pychromecast.socket_client] [Party(192.168.86.102):32101] Heartbeat timeout, resetting connection
> 2024-01-27 19:28:54.222 WARNING (Thread-5) [pychromecast.socket_client] [Wohnzimmer(192.168.86.24):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:28:54.226 WARNING (Thread-6) [pychromecast.socket_client] [Tv(192.168.86.24):32223] Heartbeat timeout, resetting connection
> 2024-01-27 19:28:54.233 WARNING (Thread-8) [pychromecast.socket_client] [Wohnzimmer TV(192.168.86.42):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:28:54.263 WARNING (Thread-4) [pychromecast.socket_client] [Hallway Wifi(192.168.86.158):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:28:54.300 ERROR (MainThread) [homeassistant.components.brother] Timeout fetching brother data
> 2024-01-27 19:28:57.951 ERROR (Thread-5) [pychromecast.socket_client] [Wohnzimmer([::ffff:c0a8:5618]):8009] Failed to connect to service ServiceInfo(type='host', data=('[::ffff:c0a8:5618]', 8009)), retrying in 5.0s
> 2024-01-27 19:30:21.990 WARNING (Thread-5) [pychromecast.socket_client] [Wohnzimmer(192.168.86.24):8009] Heartbeat timeout, resetting connection
> 2024-01-27 19:30:25.701 ERROR (Thread-5) [pychromecast.socket_client] [Wohnzimmer([::ffff:c0a8:5618]):8009] Failed to connect to service ServiceInfo(type='host', data=('[::ffff:c0a8:5618]', 8009)), retrying in 5.0s
> 2024-01-27 19:30:50.673 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.shelly1_c45bbe5645a0 are missing or not currently available
> 2024-01-27 19:30:53.275 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.shelly1_c45bbe5645a0 are missing or not currently available
> 2024-01-27 19:30:57.727 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.shelly1_c45bbe5645a0 are missing or not currently available

What I find weird is that I am unable to start the Raspberry again after it crashes. It just wont boot anymore. Well I will definitely do the next install the way you discribed.

8

Does the log give any indication what’s wrong?

9

I don’t see anything obvious that would cause a crash. The logs are throwing warnings and errors for chromecast, and some warnings about your Shelly switches. The chromecast warnings are for devices with an IPv4 network address but the errors are for a device, Wohnzimmer, with an IPv6 address. Are you running a duel stack (IPv4 and IPv6) network?

Are you using this Google Cast integration and this Shelly integration?

Are the Shelly devices running the latest firmware?

Again, I would try a fresh install and start adding your integrations and devices one-at-a-time and recheck the logs after each addition to see if everything is ok and let your system run for a while (a day or two) before adding the next integration. We are trying to see if a specific integration is causing the crash.

We also can’t rule out a hardware problem. It could be a faulty power supply, SD card, or something else.

The power supply could be overloaded if you have anything plugged into the USB ports that draws enough power to exceed its limits (like an SSD). Note: the recommended RP4 PSU is 3.0A. Do you have another power supply you can try? If you are using the SSD with this power supply, it will cause problems - you should have the SSD plugged into an independently powered USB hub and then the hub plugged into your RP4.

The SD card should be a high quality Application Class 2 card. Have you been using the same SD card or do you have a new one you can try?

This could be corruption caused by the crash. Or, if you pull the power without shutting down the system properly.

10

Max thanks a lot for your extensive analysis and tips. I will try to set it up again this weekend.

The Shelly and Chromecast are being used by me but I am not sure the Shelly is up to date. Will check that.

About my lan setup I am to be honest not sure what a duel stack (IPv4 and IPv6) network is. I have Google wifi (mash). Directly connected to the Google Wifi Base is a classic Hub for all the devices that need cable connection.
In Google Settings it says IPv6 is deactivated.

Will try around a bit. Let’s see :slight_smile:

(I also have a slim client somewhere, maybe I also try it with this. Then there are definitely not power or other hardware issues)