Very irregular. Can’t pin it down to a time or event. Tonight again I noticed I can’t log in on the companion app. Waited a bit and it doesn’t re-connect. Only solution was to re-boot with the power button.
No error messages in logs after re-boot.
So tonight when it failed to respond I turned on the monitor that’s attached to the headless Intel NUC. I leave it powered off but connected for troubleshooting purposes. I was hoping to see an error message of some sort but the monitor reported no video signal despite HDMI cable being plugged in and power light on.
I re-booted and HA came up perfectly. Monitor displayed start-up. Logged into HA in desktop, no errors.
The fact that no display was showing, is that absolutely determinative of a hardware issue?
Sometimes when machines are started, without a monitor connected to therouterThe only fix I found that is reliable for this issue is to either restart the router or turn off the wifi on my ipad and turn it back on again.y will just not initialize the monitor, and therefore when you connect the monitor later, it will not display an image. Other times the operating system has going into power saving mode, and therefore the monitor is not displaying anything, even if you connected a monitor while the system started up. In the second case, you usually get a picture back by connecting a keyboard or a mouse and wiggling the mouse or touching a key.
That process might allow you to be able to log into the console on see what’s happening or maybe diagnose a crash. Do note that if the system has genuinely crashed, connecting a keyboard and wiggling a key is not going to bring a display back.
To me, what it seems to be the issue at home is that you’re having a networking problem and therefore the machine is not actually connected to the network or your companion machine is not connected to the network properly. To diagnose that issue, you would usually use a ping utility to try and ping the whole assisted machine from the companion machine.
I get a similar issue with my iPad at least twice a week, the iPad will remain connected to Wi-Fi, but it will stop responding to pings periodically. And when that happens I cannot, for the life of me get Home Assistans to load in the iPad and display anything. It just shows as if it was not connected. The only fix I found that is reliable for this issue is to either restart the router or turn off the WiFi on my iPad and turn it back on again. I am looking for a replacement router right now, but since I haven’t found one that meets my requirements, including support for VLANs, and the device tracking, I haven’t been able to reply to this flaky piece of shit I have at home.
@NathanCu thanks for the link to the Cookbook troubleshooting. I have the ssh addon already installed. I started it up. Here is what the docs say for easy reference:
Now there is one catch with this approach. The only way to read the journal is using journalctl . And journalctl isn’t available in this addon because it is alpine based and journalctl isn’t available in alpine based systems. So what you’ll have to do is copy the /var/log/journal folder and everything in it out of here to another linux system which has journalctl available (debian, ubuntu, etc.) You can do this with scp using scp -r root@<HA URL>:/var/log/journal . or by using the SFTP option in the addon. Note: you will have to set ssh.username to root in the config at least temporarily for either scp or the sftp option to work. You can change it back to non-root after as the addon’s documentation recommends.
When I move to /var/log, I see the journals folder. I tried typing “scp -r root@:/var/log/journal .” but it didn’t copy, instead I got a root login prompt. I tried to log in but it didn’t like the password.
Then I read the document more closely where it says to change the ssh username to root.
So in the ssh addon configuration tab, I changed the username from my current login name to “root”, left the same password. Re-started the addon. Still would not allow the login.
