I assigned a static ip address(x.x.x.8) to the Hubitat2. About every 7-10 days, it will switch itself to a different static ip address(x.x.x.250). This is a problem because I also use Hoobs to enable Apple HomeKit support. I discover the switched ip address whenever my HomeKit stops working.
I think the following explains why the Hubitat2 picks the x.x.x.250 static ip address, but not why it randomly changes when it has been assigned a static ip address of x.x.x.8. This is my second Habitat2. When I added this particular Hubitat2, it was to replace my original Hubitat1 that was having problems. The Hubitat1 had a static ip address of x.x.x.8, and the Hubitat2 was temporarily given a static ip address of x.x.x.250 to facilitate transfer of settings/etc. After transfer, I removed Hubitat1 from network, and changed the Hubitat2 static ip from x.x.x.250 to x.x.x.8.
Anyway, does anyone have any suggestions to prevent the Hubitat2 from periodically changing its static ip address and consequently killing my HomeKit access?
some routers (comcast/xfinity for example) keep a local table of device name to ip. Search and destroy. Look in those tables if they exist and remove references to both ip's and let it pull the arp again.
Another is certain intellegent switches - i run 24 port lvl 2/3 switch with snmp so i can watch traffic, it has a tendency to lock a mac to a port table - flush and clear if you have that.
allocate a hard reservation in your dhcp server - so in case a device comes looking, only that mac will get the IP. same with DNS server if you have one, check the tables to be sure there isn't a reverse ip setup, they get overlooked on DNS refreshes by devices.
I strongly recommend adding a MAC to IP address entry on your router if it supports that feature and use DHCP, I do this for nearly 200 devices and it works really dependably.
I have found Hubitat hubs to revert occasionally to previous static entries as well as a couple of other manufacturer miscreants. It will pay dividends regarding IP address conflicts in the future too.
Setting Static IP address in dhcp server did solve the problem. For anyone with Unifi hardware, you will have to pick a different static ip address than the one that is currently set on the Habitat because the UDM-Pro, in this instance, will not allow you to set the same static IP address as what is set in the Habitat. Once I figured that out, then setting the static ip address in the dhcp server worked.
