Changed home router now HAOS isn't contactable

Hi All,

I have a big problem I have no idea how to solve. I just changed my router at home and am having issues getting HAOS back on the network, or rather, it appears to think it is on the network but nothing can access it.

I am using an X86 machine with HAOS, I plugged in a monitor and keyboard and was able to get to the command line. Now I don’t know much about HAOS command line but I found the “network info” command and it shows the machine with an IP and the gate way address.

I think I set the install as a static address so my first thought was to change it to DHCP but I don’t know how to do that without access to the GUI. I found a post about changing it but it lead to another post that said don’t use this anymore.

I have found a command that is supposed to change it back to default DHCP here: operating-system/Documentation/network.md at a2ff594a7513828220f60b3aff0185bfdd17c484 · home-assistant/operating-system · GitHub

ha network update default --ipv4-method auto

but I am not sure it worked, certainly I can’t access the install still:


“context deadline exceeded (Client.timeout exceeded while awaiting headers)”

I am not sure where to go from here :pleading_face:

Everything else is accessing the network perfectly fine (the machine I am typing this on is connected via the same hub HAOS is on, and the LAN lights on the HAOS machine are illuminated and flashing.

Is there a way to get to the linux command line and manually reset the network interface to DHCP?

OMG(oodness) I am an idiot. I hadn’t notice the network cable into the switch (from the router) was not fully seated :sweat_smile: :smiling_face: now seems to be back up and running.

I’ll leave this here in case anyone else makes the same error and can learn from my stupidity!

3 Likes