Hi,
I’ve been using HASSIO on a NUC for quite some time (months) now, but I’ve experienced two occasions on which the entire home stopped responding, even Telegram and all other things that rely on a router connection.
Today it did it again - at 4:30am - hurray. It turned on the water tank because it was below 80% and then simply disconnected(?) from the LAN. This caused the water tank to overfill and made quite a mess in my garden, which I had to solve … in the middle of the night.
The lights on the LAN port were still blinking, but yet, nothing worked. No Web interface, no wall tablets, no Telegram, no nothing.
Well… Before I restarted it, I checked all sorts of logs and things (Monitor and Keyboard are hooked up 24/7 to solve this kind of problem, which happen randomly). Checking the logs, I saw nothing unusual, just normal template errors from lacking WiFi sensors. I’ve tried disconnecting the LAN and reconnecting it physically. It showed up (on the console) that the link was back “up”, but Telegram, wall tablets and all other things still weren’t responding. I even restarted the router - to no avail.
The problem seems to be on the “Hassio/Hassos level”.
Only a restart fixes it… but honestly… like … really?
The NUC image I had downloaded and flashed straight from the Hassio page, so no DIY mess with Linux and Docker.
Have a look for newer firmware/BIOS those boards normally sit around for a while in a warehouse before getting shipped out.
You may find that it’s out a few revisions which fixes the issue.
I already updated the BIOS, because before it wouldn’t even let me install Hassio, for some reason.
It isn’t a hardware problem, the NUC’s been running fine on Windows before, for literal years. I really didn’t want to manually install Linux, then mess around with docker and things to install it.
Furthermore, some things that depend on Hassos wouldn’t work anymore.
Were you able to still ‘ping’ the HassOS machine on the network?
I had a similar sounding issue here:
Where the HA container simply crashes, but the HassOS is still running.
If you are using any custom components you could try disabling them, I have not had this happen to me more than once, so I’m not sure if my issue was caused by the trakt custom component.
This is still happening on a quite frequent basis. It’s beginning to annoy me quite a lot.
Do you know if there’s a changelog for the Intel NUC image? Seems like since I’ve installed mine, there’s been an update from 2.11 to 2.12. Have they done anything to the LAN interface or similar? If not, I’ll really install Docker and screw that out-of-the-box image.
