My Orbi router reassigned my Hubitat ip and it seems all is broken at this point. Here is some info. As I said it is a Netgear orbi router. I use only Zigbee devices at this point both plugs and lights, and sensors (motion and contact). All automations and Alexa and google assistant voice commands are also broken. Devices can’t be controlled through IP interface although I am able to connect to Hubitat through the new IP assigned by the orbi. I did reserve an IP address for the Hubitat in the Advanced LAN settings of the orbi which it apparently ignored. I can’t seem to go in and assign an IP address or I would change it back. Now the question: will I have to re-pair each device every time this happens? I have not attempted to re pair devices yet - honestly just too frustrated. The Hubitat locked up while I was on a trip. I reset device upon return and then did latest update - sometime during that is when the Orbi gave the device a new IP.
The IP address of the device shouldn't affect Zigbee or Z-wave devices at all It would just affect integrations with things like other hubs/services that interact directly with your hub, and the ease of connecting. If the IP is the only problem it shouldn't affect the automations, it sound like there may be other issues with the hub, have you tried turning it off and unplugging it for more than 20 minutes this should cause it to refresh the Zigbee network when it comes back up. Do you still see all the Zigbee devices on the hub? What firmware is it at currently, I wouldn't update if there is an update available until you get it stable again though as that may just confuse the issue.
Check to see what the default lease time is on your router. A device won't ask for an address if the lease time hasn't expired. At least temporarily you should shorten the lease time to whatever is the lowest time while noting that zero is usually forever. Shutting the Hubitat hub down for 30 minutes as @Terk suggested may help with DHCP as well. Check to make sure the reserved address is correct. Some routers don't allow reservations within the DHCP and some even force reservations to within the DHCP range. Make sure you haven't run afoul of any such rules.
I have turned off and back on but by unplugging but without a 20 minute delay - I will try that. Yes I still see all Zigbee devices and as I went through them there were 3 of over 30 that would still operate from the web interface. Thank you.
Here is what the manual says:
Manage Reserved LAN IP Addresses
When you specify a reserved IP address for a computer on the LAN, that computer always receives the same IP address each time it accesses the router's DHCP server. Assign reserved IP addresses to computers or servers that require permanent IP settings.
Reserve an IP Address
To reserve an IP address:
- Launch a web browser from a WiFi-enabled computer or mobile device that is connected to the network.
- Enter orbilogin.com.
A login window opens. - Enter the router user name and password.
The user name is admin. The default password is password. The user name and
password are case-sensitive.
The BASIC Home page displays. - Select ADVANCED > Setup > LAN Setup.
- In the Address Reservation section of the page, click the Add button.
- In the IP Address field, type the IP address to assign to the computer or server.
Choose an IP address from the router's LAN subnet, such as 192.168.1.x. - Type the MAC address of the computer or server.
Tip: If the computer is already on your network, you can copy its MAC address from the Attached Devices page and paste it here. - Click the Apply button.
The reserved address is entered into the table.
The reserved address is not assigned until the next time the computer contacts the router's DHCP server. Reboot the computer, or access its IP configuration and force a DHCP release
and renew
The odd thing is that the router reserved IP table (mentioned in step 8) still showed the Hubitat with the reserved IP address I had assigned it, but it had given that IP address to a different device and assigned a different IP address to the Hubitat in spite of the IP reservation. Obviously I had to access the Hubitat through the new IP address the router had assigned to it. But the worst part is this seems to have little to do with why my devices and automations have mostly stopped working. As I mentioned I returned from a trip and found my Hubitat locked up... pulled plug... restarted... did most recent update (2.1.1) causing a second lock up and most of my devices stopped working.
Contacting support@hubitat.com is probably your best bet at this point.
@genbap, I’d also check with Netgear in case this issue was identified in their firmware and can be corrected by up dating the routers firmware.
Noting of course that it wont do anything for HE but if Netgear have fixed their IP reservation table then you shouldn’t have the problem again.
Great advice. Thank you.
For some reason my router shifted everything from 192.168..:. To 10.0... Not all devices wanted to follow, especially those with reserved IPs. The result was a very broken system. It was a long night and early morning and my familiarity level with my system has grown exponentially. But all is back to normal including Hubitat. Thanks for all the advice.
That should not happen. Could you have two devices doing DHCP on your network ??
More research to do but I think it’s possible my managed switch was giving different IPs if that is even possible. Right now I took it out of my system.
Some switches can have DHCP server capabilities.
