Yes, another thread by someone who changed their HA IP address and now cannot connect…
I have a HA Green connected directly to a Unifi UDR7.
I was trying to move the HA from the default VLAN to a new IoT VLAN.
My HA already had a fixed IP address 192.168.1.13. I wanted to continue having a fixed IP addres for it in the IoT VLAN.
So I changed network settings in HA for
IP = 192.168.20.13 (within the IoT VLAN range)
Gateway = 192.168.20.1
DNS = 192.168.20.1
I wasnt sure about this configuration but I thought “hey, how bad can it be?”…
I then also set the client settings for HA in the Unifi UDR to Virtual Network Override = IoT and Fixed IP Address to 192.168.20.13 (to match the above).
After I saved and refreshed I cannot connect to HA.
I tried restarting the HA Green, now I see a comple pattern of flashes on the green and amber LEDs - Google tells me this means there is likely some networking issue.
EDIT: LED pattern seems to have settled to 1 green flash, 2 amber flashes - Nabu Casa website seems to indicate this is normal behaviour, but I still cannot connect.
I’m not sure how to rescue this.
I’ve tried undoing the settings on the Unifi UDR but this does not seem to make any difference.
How can I undo the changes on the HA Green or otherwise connect to it?
It is rarely the changing of the IP that cause the problems, but rather people thinking VLANs are just splitting a network up in smaller bits.
VLANs are much more about routing and proxying and for that to work the person that configures and administrate the VLANs needs to know which protocols all the devices use and how they are routed, if they need be.
That means understanding IPv4 and IPv6in depths and IPv6 is not at all the same as IPv4, so a deep study is needed of that protocol.
On top of those transport protocols are a lot of communication protocols and those needs to be understood too, especially the many open and proprietary discovery protocols, which are often not routable with standard IP routing and therefore need special proxying setup.
OK - but how do I now connect to my HA?
It was working fine directly before my changing the IP settings in HA.
The Unifi network shows the HA Green now has an IP of 172.30.232.1.
Which seems odd - all the other client’s IPs are 192.168.xx.xx.
Seems like something has gone “wrong” with DHCP, but I dont know how to resolve without having access to HA.
Thankfully I’ve ben able to rescue connectivity to the device.
Started by plugging in a monitor and keyboard directly to the HA green (quick trip to PC World to get a HDMI cable and wired keyboard - few poeple have these lying around anymore!)
Then at the CLI shown on the screen
ha> network update end0 --ipv4-method auto
The command appeared to time out but confirmed the interface now uses automatic IP assignment using:
ha> network info
Then restart the device using the button on the case.
After it came back up I told UniFi to Remove (forget) the device.
Waited a few mins for DHCP to do its thing and viola, HA gets an IP of 192.168.1.22 on the default VLAN and homeassistant.local:8123 starts working again!
To others that may have the same issue, I did not see any option other than connecting directy to the device like this.
Set static IP’s in the DHCP, it will be easier and you will be able to change it back without shopping if it goes wrong. It will also allow you to spot IP address clashes easily.
