#Suddenly RPi has no IP address

1 messages · Page 1 of 1 (latest)

quasi panther
#

My HAOS RPi system has suddenly become inaccessible following a restart. The HA is still operating to the extent that the zigbee devices are still operating and executing the automations, I just can't access the UI by IP. The RPi does not show up on my modem/router. Sadly, I am in a remote location and have no hdmi cable to connect to the RPi directly. Equally sadly, my last backup is 3 days out of date.

#

I've slipped in another SD card with a different HAOS installation and it gets an IP address as usual, so I don't think there is a hardware problem on the RPi.
I can also read the SD on my PC, so I also think the SD is OK. Also, the SD must be OK because as I said above, the HA automations are still working.
I'm out of ideas.

marsh mica
#

Interesting, yeah I'm not sure if my automations are working because I had all my automations turned off..

#

But other than that same issue as you

#

One would think if it isn't displayed on your network, then all your automations shouldn't be working..

quasi panther
#

My devices are on a Zigbee network. It's the ethernet/IP network that isn't connecting. The Zigbee is driven by a USB dongle.
The RPi isn't even being issued an address by the router, it is as if the HAOS has switched off the IP.

brazen rain
#

I had the same happen to me about a week ago. I use static DHCP to assign the address to my HA instance. For some reason after a reboot (could have been after an HAOS update, not sure) the auto flag for using DHCP was turned off. It took a bit to figure out what was going on but it could be fixed using the ha net command. I was fortunate to have a keyboard and monitor connected at the time.

#

FYI, I'm not on a RPi, its a x86 box.

quasi panther
#

Fixed now!
I found a micro HDMI adaptor and got a screen and keyboard connected.
Network info command indicated eth0 was disabled. I ran this command:
network update eth0 --ipv4-method auto
and now all working again.
It's a worry that this happened in the first place. Will it happen again sometime?
FYI I run DHCP from my modem/router with a static reservation for the RPi. It has been rock solid since installation about a month ago, until now.
Home Automation is not of much value if it isn't reliable, so this is a disappointing episode for me.

brazen rain
#

That was the same fix I used. I still wondering why it happened in the first place and I have new theory that was triggered by something you just said. We had a power outage. The x86 box may have come up before the router. Hence no ethernet and perhaps the auto "turned off". I'm going to try it out by unplugging my x86 box, unplugging the ethernet, repowering and see what happens. Then I can replug the ethernet to see what happens then.

#

Just tried the test. The box powers up, gets an automatic private IP address as expected. I plug in the ethernet and the address does not change, so box is not useable on my network. Reboot and everything work. auto configuration did not change, which is good. What is bad is that when the ethernet was plugged in again it did not get an address using DHCP. It is bad because in the power fail situation and everything is coming up again, the HAOS may boot sooner than the router with DHCP, then I have a lame HAOS box.

brazen rain