Set static IP on Home Assistant Green, now can't access web GUI

Just got my Home Assistant Green yesterday and I’m not off to a great start with it.

First thing I did was connect it and power it on as directed, then I ran through the initial configuration. Once that was done, I went back to the settings page and changed from a DHCP address to a static IP. A warning appeared at the bottom of the page that I “may” lose connectivity after the change (obviously), and I gave it a few minutes before trying to reload the page with the new static IP, and nothing. I pinged the static IP and it responded just fine, so I rebooted the device, and still nothing.

Are these things really that fragile? What’s the best way to go about fixing this?

Fragile isn’t the right term in. This context if your ip setting is wrong HA has no chance…

What did you change it to.
(including the subnet mask)

What is the expected subnet info for the network you’re on.

What is the IP address and subnet mask of your local pc you’re connected from

Can you get a monitor attached.

You could try to reset it.

IP settings are correct. The static IP is 192.168.1.16/24 and there’s nothing complex about my home network. I use that subnet on everything behind my Opnsense firewall. 192.168.1.101 on up is my DHCP address pool, everything below 101 is set aside for static assigned addresses.

I might try getting a monitor attached later, but more than likely just go through the reset procedure. I’d already tried method of holding the button in while connecting the power supply, but the yellow LED never went solid. So I guess I’ll have to try the SD card method.

Great. Nice flat class C.

Thats said.I asked because your symptom is exactly the same as someone else who ‘fat fingered’ the subnet mask on the box effectively putting it outside the defined network and islanding it when doing the exact same thing you did.

Basically it’s worth a few seconds to hook up a monitor and verify the setting is ACTUALLY what you expect before blowing away the box. I can’t tell you how many times in 28 years I’ve mistyped an IP…

1 Like

As @NathanCu says, find out what the IP address is, then make that a reserved address on the router. You shouldn’t have to change anything in HA.

1 Like

Resolved. I reset to factory condition from SD card and repeated steps from yesterday to do initial config, then went to network settings to set static IP. I was very, VERY careful to make sure I entered the address correctly, then double checked the subnet mask, and it was 255.255.255.0 as expected. Saved the config, and once again couldn’t access, but the device was responding to ping.

Hooked up a monitor, and sure enough, the address was showing 192.168.1.16/32 instead of 24. Hooked up a USB keyboard and manually reset the IP address to DHCP successfully. Went back to the web GUI and once again entered the static IP and I noticed when I tabbed out of the IP address field, the subnet mask changed to 255.255.255.255. Set that last octet back to 0, saved and everything is fine.

So bottom line, bug in the UI.

EXACTLY that happened to me yesterday when i replaced SSD on my NUC. I’m sure that mask was 255.255.255.0 when i opened network settings, but it changed to .255 when i was entering IP. I did saw that, sadly a tiny bit too late - just already pressed “save”. So, manual change from SSH is only option then.
A bug, i agree.

Then someone needs to file a bug in github against HA core or it will never be fixed.