HASSIO crashes, logs shows block of NULL

Installation Home Assistant OS
1

Hello,

From time to time my HA server just stops working after a few days. The only way for me to reset it is to unplug the power. The logs do not really help me to understand the issue in fact I am just seeing a long row of NULL.

2024-09-13 09:13:27.323 INFO (MainThread) [custom_components.localtuya.common] [bf1...ras] Trying to connect to 192.168.3.113...
2024-09-13 09:13:27.326 INFO (MainThread) [custom_components.localtuya.common] [bf4...v8l] Trying to connect to 192.168.3.147...
2024-09-13 09:13:27.328 INFO (MainThread) [custom_components.localtuya.common] [bfb...53x] Trying to connect to 192.168.3.207...
2024-09-13 09:13:27.415 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error in 'Close Bypass' trigger: In 'numeric_state' condition: unknown 'above' entity sensor.mouvement_escalier_air_temperature
2024-09-13 09:13:30.395 WARNING (MainThread) [custom_components.localtuya.common] [bfb...53x] Failed to connect to 192.168.3.207: [Errno 113] Connect call failed ('192.168.3.207', 6668)
2024-09-13 09:13:30.398 WARNING (MainThread) [custom_components.localtuya.common] [bf1...ras] Failed to connect to 192.168.3.113: [Errno 113] Connect call failed ('192.168.3.113', 6668)
2024-09-13 09:13:30.399 WARNING (MainThread) [custom_components.localtuya.common] [bf4...v8l] Failed to connect to 192.168.3.147: [Errno 113] Connect call failed ('192.168.3.147', 6668)
2024-09-13 09:14:08.875 INFO (MainThread) [habluetooth.scanner] hci0 (E4:5F:01:68:6E:A4): Bluetooth scanner has gone quiet for 90s, restarting
2024-09-13 09:14:27.324 INFO (MainThread) [custom_components.localtuya.common] [bf1...ras] Trying to connect to 192.168.3.113...
2024-09-13 09:14:27.327 INFO (MainThread) [custom_components.localtuya.common] [bf4...v8l] Trying to connect to 192.168.3.147...
2024-09-13 09:14:27.330 INFO (MainThread) [custom_components.localtuya.common] [bfb...53x] Trying to connect to 192.168.3.207...
2024-09-13 09:14:27.419 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error in 'Close Bypass' trigger: In 'numeric_state' condition: unknown 'above' entity sensor.mouvement_escalier_air_temperature
2024-09-13 09:14:30.395 WARNING (MainThread) [custom_components.localtuya.common] [bfb...53x] Failed to connect to 192.168.3.207: [Errno 113] Connect call failed ('192.168.3.207', 6668)
2024-09-13 09:14:30.397 WARNING (MainThread) [custom_components.localtuya.common] [bf4...v8l] Failed to connect to 192.168.3.147: [Errno 113] Connect call failed ('192.168.3.147', 6668)
2024-09-13 09:14:30.399 WARNING (MainThread) [custom_components.localtuya.common] [bf1...ras] Failed to connect to 192.168.3.113: [Errno 113] Connect call failed ('192.168.3.113', 6668)
NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL NULL

Concerning my installation : I have HASSIO installed on a Rasberry Pi4 of 4GB. My data is stored on a SSD connected with SATA/USB directly to the Pi. I also have a zwave dingle attached to my USB port. The Pi is powered with the standard Pi power cable which shouold deliver 3.5A.

Concerning my software : I am using HASSIO, I have several addons installed icl. Maria DB, Z-WAVE JS, AppDaemon and Music Assistant.

And here some screenshots on hardware usage. The server stopped working from the 13th to the 29th.

grafik
grafik2824×904 119 KB

grafik
grafik2824×904 117 KB

grafik
grafik2824×904 104 KB

Would be great if you could help me to discover the issue. It is really anoying when I am leaving for vacation, since I am totallly unable to restart the server remotely :frowning: .

Thanks !

2

Hello,
I seem to have the same problem. In my log, just like yours, there is a warning about the LocalTuya integration. Since the participants are disconnected from the network, they are queried every minute.
Then suddenly, without any indication of time, the NUL block occurs. The Pi4 appears to be restarting because a new log is being created.
I will deactivate the LocalTuya integration and observe it.

2024-10-12 09:35:21.658 WARNING (MainThread) [custom_components.localtuya.common] [bf4...tmz] Failed to connect to 192.168.2.26: [Errno 113] Connect call failed ('192.168.xxx.xxx', 6668)
2024-10-12 09:35:21.659 WARNING (MainThread) [custom_components.localtuya.common] [110...db4] Failed to connect to 192.168.2.28: [Errno 113] Connect call failed ('192.168.xxx.xxx', 6668)
2024-10-12 09:36:21.658 WARNING (MainThread) [custom_components.localtuya.common] [bf4...tmz] Failed to connect to 192.168.2.26: [Errno 113] Connect call failed ('192.168.xxx.xxx', 6668)
2024-10-12 09:36:21.661 WARNING (MainThread) [custom_components.localtuya.common] [110...db4] Failed to connect to 192.168.2.28: [Errno 113] Connect call failed ('192.168.xxx.xxx', 6668)
NULNULNULNUL...

Do you have any new insights?

3

Nope unfortunately not,
I am buying a separate power for my SDD to uplift its alimentation, maybe the SDD consumes too much power ???
I will also disable local tuya.
Let us keep posted if the issue arises again :grimacing:

4

Yep, power is the most likely culprit. The standard power supply is often not able to supply the SSD as well, and or power supplies tend to degrade. Try another power supply and use separate power supply for the SSD (if need be through a powered usb hub).

5

Last night the system rebooted with the NUL block. Disabling the Local Tuya integration was not helpful and seems not to be the trigger.

6

I increased my power supply from 5.1V to 5.3V and since then the system has not frozen or restarted. :+1:

2 Likes
7

I added an external power supply via USB Y cable and an usb power rack. I will keep you posted if this does not solve the issue.

8

That might work, although I heard someone suggest that the RPI board is not standard and might not be able to pass sufficient the power to all usb ports. I have no clue if that is true or not.