HA constantly crashing on a NUC

[Ron_Bln]

Hi there,

after 1 year of pause I decided to “re-start” with HA in our new home. For this I bought a brand new Intel NUC7i5 DDR4 16GB NVMe 256GB which I thought should be more powerful than enough to run HA OS on. But even when only having some few integrations running on it yet, the system is regularly crashing (about once every 24 hours) so I have to unplug the NUC to get it starting again.

OS Version: Home Assitant OS 10.3
Home Assistant Core: 2023.6.3

Did anyone here have the same issues with HA on a NUC or has an idea how to find the source of the problem? Every hint is welcome!!!

[anon63427907]

Out of topic: why did you require more power at the beginning? Too many cameras?

[Ron_Bln]

I didn´t require more power. I just decided that, once I´m starting all over new with HA, to choose a hardware setting that should be “future savvy” with regards to any possible use case in the future (that was one of my key learning from my past PI3 experiences)

[fleskefjes]

A good place to start is to look at the logs.

[mamoel]

Before asking for help, you should read this thread.

Especially #10 is very important.

We don’t know anything about the software part of your HA config and I’m quite sure the hardware (NUC) is not the problem.

What about your error log?

[Ron_Bln]

My bad - I updated the initial post with the missing information on configuration and this is the content of my home-assistant.log:

2023-07-01 12:16:47.579 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration alexa_media 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
2023-07-01 12:16:47.580 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
2023-07-01 12:16:47.580 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration landroid_cloud 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
2023-07-01 12:16:47.580 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration auto_backup 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
2023-07-01 12:17:08.505 WARNING (MainThread) [homeassistant.components.netatmo] Webhook not registered - https and port 443 is required to register the webhook
2023-07-01 12:19:09.189 ERROR (MainThread) [homeassistant.components.xiaomi_ble] C4:7C:8D:6C:5D:5A: Bluetooth error whilst polling: C4:7C:8D:6C:5D:5A - C4:7C:8D:6C:5D:5A: Failed to connect: Timeout waiting for connect response while connecting to C4:7C:8D:6C:5D:5A after 20.0s, disconnect timed out: True,  after 5.0s
2023-07-01 12:21:18.879 ERROR (MainThread) [homeassistant.components.xiaomi_ble] C4:7C:8D:6B:6B:49: Bluetooth error whilst polling: C4:7C:8D:6B:6B:49 - C4:7C:8D:6B:6B:49: Failed to connect: failed to discover services, device disconnected

[fleskefjes]

This is the log after restart. Try looking in the log file called log.1, this should contain relevant info.

[complex1 (Frank)]

I’m running HA on an Intel NUC7i3BNH, 4GB DDR and 120GB m.2 SSD without any issues.

I did install HA using this link and till now I have no issues:

Install Home Assistant to Intel NUC m2 nvme ssd with previous windows partition. Ubuntu/Balena Etcher did not work

Spent around 2 hours trying to use Ubuntu Live with Balena Etcher to install the generic Intel img. Balena kept throwing very unhelpful errors, and I tried multiple HAOS releases and versions of Etcher, and one other Live distro, just in case it was an incompatibility between the Linux / Etcher releases. I was installing to used hardware that had a previous Windows 10 install, in preparation for restoring a backup. I’d previously done this for a move from a VM to an ODRIOD. I have used the l…

[Ron_Bln]

Alright, now I have a huge log.1 file with a whole lot of information. What should I do now?

[lordwizzard]

Well we can’t help if we can’t read it. How big is the file?

[fleskefjes]

Find the point in time where you crashed, and look for log entries leading up to that point in time.

[Ron_Bln]

So even after a complete redo of my HA installation, my NUC keeps crashing at least once every 48 hours (often every day). As requested here goes the content of my “home-assistant.log.1.txt”

2023-07-19 07:16:05.435 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration alexa_media 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
2023-07-19 07:16:05.436 WARNING (SyncWorker_4) [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
2023-07-19 07:16:05.436 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration dwd 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
2023-07-19 07:16:05.437 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration remote_homeassistant 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
2023-07-19 07:16:06.306 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=64 from 2023-07-18 04:56:44.541097)
2023-07-19 07:16:13.217 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up fitbit platform for sensor
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 353, in _async_setup_platform
await asyncio.shield(task)
File “/usr/local/lib/python3.11/concurrent/futures/thread.py”, line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/fitbit/sensor.py”, line 243, in setup_platform
redirect_uri = f"{get_url(hass, require_ssl=True)}{FITBIT_AUTH_CALLBACK_PATH}"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/network.py”, line 167, in get_url
request_host = _get_request_host()
^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/helpers/network.py”, line 206, in _get_request_host
raise NoURLAvailableError
homeassistant.helpers.network.NoURLAvailableError
2023-07-19 07:16:19.044 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘Ventilator’ for xiaomi_miio integration not ready yet: Unable to discover the device 192.168.178.40; Retrying in background
2023-07-19 07:16:24.175 WARNING (MainThread) [homeassistant.components.netatmo] Webhook not registered - https and port 443 is required to register the webhook
2023-07-19 07:16:36.265 ERROR (MainThread) [frontend.js.latest.202307051] https://smartron.online/hacsfiles/light-entity-row/light-entity-row.js?hacstag=151318225025:10:47 ReferenceError: Can’t find variable: Polymer
2023-07-19 07:32:15.083 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 07:57:56.819 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 07:58:11.505 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data for 192.168.178.87: Timeout waiting for response for <class ‘api_pb2.DeviceInfoRequest’> after 10.0s
2023-07-19 07:59:59.196 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: EOF received
2023-07-19 08:02:29.374 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: Ping response not received after 90.0 seconds
2023-07-19 08:03:49.875 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 08:03:56.603 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities cover.pi4schlafzimmer_jalousie_cover or it is/they are currently not available
2023-07-19 08:12:26.102 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 08:12:49.271 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data for 192.168.178.87: Timeout waiting for response for <class ‘api_pb2.DeviceInfoRequest’> after 10.0s
2023-07-19 08:13:13.890 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can’t connect to ESPHome API for atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Hello timed out (TimeoutAPIError)
2023-07-19 08:13:13.893 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: Connection lost
2023-07-19 08:14:20.872 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data for 192.168.178.87: Timeout waiting for response for <class ‘api_pb2.ListEntitiesRequest’> after 60s
2023-07-19 08:15:33.879 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can’t connect to ESPHome API for atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Error connecting to (‘192.168.178.87’, 6053): (SocketAPIError)
2023-07-19 08:15:52.363 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data for 192.168.178.87: Timeout waiting for response for <class ‘api_pb2.DeviceInfoRequest’> after 10.0s
2023-07-19 08:17:07.764 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: EOF received
2023-07-19 08:22:26.688 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: EOF received
2023-07-19 08:26:28.852 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: EOF received
2023-07-19 08:27:50.602 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 08:28:58.268 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-833ce8 @ 192.168.178.87: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 08:43:05.966 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 08:43:44.904 ERROR (MainThread) [frontend.js.latest.202307051] http://192.168.178.90:8123/hacsfiles/light-entity-row/light-entity-row.js?hacstag=151318225025:10:40 Uncaught ReferenceError: Polymer is not defined
2023-07-19 08:44:39.432 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 08:48:45.211 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 08:58:35.633 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 09:03:51.884 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 09:23:27.951 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 09:26:29.599 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 09:26:39.709 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can’t connect to ESPHome API for atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Hello timed out (TimeoutAPIError)
2023-07-19 09:26:39.711 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: Connection lost
2023-07-19 09:50:41.974 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 09:50:53.260 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can’t connect to ESPHome API for atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Hello timed out (TimeoutAPIError)
2023-07-19 09:50:53.262 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: Connection lost
2023-07-19 09:55:58.283 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 09:57:59.014 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 09:59:34.018 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 10:00:57.257 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 10:08:48.110 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 10:12:31.153 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 10:13:45.059 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 10:13:55.291 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can’t connect to ESPHome API for atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Hello timed out (TimeoutAPIError)
2023-07-19 10:13:55.293 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: Connection lost
2023-07-19 10:14:07.389 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: Connection lost
2023-07-19 10:16:00.446 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 10:16:50.237 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 10:18:35.166 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 10:20:36.009 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 10:21:21.174 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 10:22:09.008 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities cover.pi4schlafzimmer_jalousie_cover or it is/they are currently not available
2023-07-19 10:26:18.471 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities cover.pi4schlafzimmer_jalousie_cover or it is/they are currently not available
2023-07-19 10:26:57.802 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities cover.pi4schlafzimmer_jalousie_cover or it is/they are currently not available
2023-07-19 10:31:48.465 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 10:36:39.011 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: Ping response not received after 90.0 seconds
2023-07-19 10:36:50.296 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can’t connect to ESPHome API for atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Hello timed out (TimeoutAPIError)
2023-07-19 10:36:50.299 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: Connection lost
2023-07-19 10:38:52.934 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 10:40:14.609 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 10:40:26.907 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data for 192.168.178.96: Timeout waiting for response for <class ‘api_pb2.DeviceInfoRequest’> after 10.0s
2023-07-19 10:41:32.656 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 10:45:25.439 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: Ping response not received after 90.0 seconds
2023-07-19 10:47:14.265 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 10:49:56.157 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 10:51:37.140 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 11:01:18.691 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 11:02:48.283 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 11:04:56.669 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 11:05:57.618 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 11:06:35.500 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities cover.pi4schlafzimmer_jalousie_cover or it is/they are currently not available
2023-07-19 11:08:29.486 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: Ping response not received after 90.0 seconds
2023-07-19 11:10:07.055 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: EOF received
2023-07-19 11:10:45.311 WARNING (MainThread) [aioesphomeapi.connection] atom-bluetooth-proxy-83a9d8 @ 192.168.178.96: Connection error occurred: [Errno 104] Connection reset by peer
2023-07-19 11:10:45.314 WARNING (MainThread) [homeassistant.components.esphome] Error getting initial data for 192.168.178.96: Read failed

Does that help anybody to spot where the problem might be located?

[boheme61]

@Ron_Bln

Connection error occurred

Seems like a good initial starting point, in further troubleshooting

Also you apparently has a few Custom integrations, it might be a good idea, of “take it 1 by 1” … if you just installed again, after your previous problems, then maybe you should not be in a hurry, so you can “detect” when the problems are “starting to pile up”

[Ron_Bln]

Ok, thanks for the reply but is that really all I can do - complete start over AGAIN and then see what causes the crashes? Maybe someone has another suggestion based on the log file I shared…

[boheme61]

Try to disable/delete the integration esphome

[cassyoung (Cassian Young)]

I had exactly that problem.

Turned out that it was the NUC power supply.

Replaced it with one with high wattage - no more problems.

[Ron_Bln]

That sounds quit promissing! Could you maybe please tell me which power supply you got?

[Ron_Bln]

Will try that as well - Thanks much @boheme61 !

[Nick4 (Nick)]

I would also advise you to try with a live boot-able OS from a thumb drive to exclude it’s not your NUC that causes this.

[Ron_Bln]

It´s crazy but it seems to be true: I changed to a 119W power supply and since then the NUC didn´t crash one time in 72h! Sad Intel is obviously not delivering their products with sufficiently empowered equipment