I just changed routers, and on my old router I had 172...., now I have 192... with my new router setup. I did a search on my habitat phone app, and still cannot find my Hubitat device. How can I change my Habitat device to 192.... from the 172.....?
Did you setup your hub with a static IP or did you use DHCP on the old router with a DHCP reservation.
I think it was a DHCP, as it was a long time ago. Not 100% sure. If I use my dashboard on the phone it works, but I cannot access the router itself
Well if it is DHCP then hubitat would just grab a new ip from the new router on the new IP Range. Is your phone connected to the router and have you used the find my hub option in the configuration?
You may want to put your old router in place for a short time just to make sure Hubitat is set to DHCP and doesn't have anything specified in the network setup page
You can also use the little partially hidden reset button on the bottom of the hub. It only resets your network settings to re-enable DHCP. It does not reset anything else.
4 Likes
Thank you. I will try that. I was able to put my old router on, and found it on the 172.... network, but I do not know how to change it to the 192.... network, once I change over to the new router. If I reset it, like you said above, will it find the new 192... hub?
lol yea.. ignore what i said earlier and do that
1 Like
Once you get it configured to grab an IP from your new DHCP server, best practice is to create a DHCP reservation. Different routers call this different things, but basically it ensures that every time your hub asks for an IP address from your DHCP server, it gets the same one.
Don't forget other LAN-based integrations you may have. If they rely on a fixed IP they'll need to be modified as well.
Ok, so I did reset for 7 seconds. Habitat hub went blue, and then green. Did a find hub, and it will not find the hub
I'd first validate that the hub has a new IP and is talking to the network. Easiest way to do that is to go to your router's admin page, find the hub in the DHCP server's client list, and get its IP address from there. Once you have that, you can use a browser from any machine on the same network to get to the hub's admin page.
I've had routers that just refuse to cooperate.
Every change, no matter how simple, the router needed a power cycle to implement.
Ok, thank you all so far. I found the hub, it now knows it is at 195..... I went to execute a command, like turn pin Hue light, and it does not work. If I tell Alexa to turn it on, it does. Do all my apps have to be rewritten now?
Not at all.
It sounds like you have a Hue hub and when you moved the Hue hub to the new router it changed IP addresses and broke the integration between HE and Hue. If so you'll need to either rediscover the Hue hub or change the IP address, depending one which Hue integration you use. You just have to be careful not to accidentally delete or recreate all your Hue devices on HE. I'd make a backup just in case 
BTW it also sounds like you may have the Alexa Hue skill enabled as well. You just want to be sure you don't accidentally create duplicate Hue devices on the Alexa side by using both the Alexa Hue skill and including those devices in the HE Alexa skill.
But make sure all your hubs (HE and Hue) have DHCP reservations... you don't want the addresses to change again!
2 Likes
Thank you all for your help today. I am up and running again. My heart stopped when I could not access Hubitat. Thank you all.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
