I have the hubitat C8. One of the draws I had for initially moving to hubitat is that I could have more things local. However, when my internet goes out, or has to be reset, I usually have to reset my hubitat as well for things to work properly. For example, my router updated overnight the other night, and when my alarm went off, none of my lighting routines had started like they should. This kinda defeats the purpose. Any ideas if I am doing something wrong?
Several ways of attacking this, but I generally start with what devices and protocols are you using?
4 Likes
Or to take a more "wild stab" approach.... Could it be you have not reserved an IP address for your Hubitat on your router?
Also, how is your hub connected to your LAN? Ethernet cable or Wi-Fi?
3 Likes
I will be honest.... I do not think I have reserved an IP nor do I know how. My hubitat is connected wirelessly.
Best way is to do a DHCP reservation in the router.
2 Likes
It is hard to be 100% sure that will be the cause, but if not, it will likely cause other problems eventually (not having a static IP using a DHCP reservation, like @thebearmay suggested).
Best option would be to configure the IP address in your router and then see if the problem continues.
1 Like
If all of your devices are Z-Wave or Zigbee, then all your automations should continue to work even if your router is turned off.
What protocol are your alarm system and lighting control devices? If any of them are Wi-Fi devices, or require access through the manufacturer's API, the problems you experienced may not be entirely the fault of the Hubitat.
1 Like
DHCP reservation is usually a good idea but I agree with starting here.
1 Like
A DHCP reservation may not solve it. You want to do a static IP outside of the DHCP pool. Then you need to determine what you think of as the internet going out. The router itself going down or just the service from the ISP. If your router goes down, either way your boned controlling it. If your service from the ISP goes down you're fine. The upside is that hub will run normally and process stuff locally. (Unless your router goes down then only z-wave and zigbee will run)
Never understood why most people prefer DHCP reservations over setting a static IP address on the device itself (unless the device doesn't allow it or it makes it difficult to do).
For most average-joes (including me!), DHCP reservations are MUCH easier to set up & manage, and 99% of the time, they work equivalently as well a static IP.
After many many years of using them, I have yet to experience any sort of failure or miss that I could attribute to DHCP-reservation wonkiness (where a static IP would've been better).
6 Likes
Another thing to remember is that your device still needs to be on your local network after internet failure in order to reach local IP addresses. If the device reroutes to another network (such as when my mobile device changes from Wifi to mobile internet provided by my carrier) then any mobile apps or dashboards that try to access a local IP stop working unless I disable the mobile internet (which re-enables the wifi network connection). Of course the Hubitat cloud connections will still work in that scenerio
1 Like
Easier to maintain, easier when you replace devices, easier to keep track of at a glance. The only things I give true static ip's to are Servers, switches, and firewalls. Everything else (even member servers) get a reservation, and workstations get full DHCP,
4 Likes
I often prefer to use static IP over a DHCP reservation too. However unless you’ve maintained a list of static IPs used you could accidentally use it again causing a clash. I’ve also known people to use static IP on a device without first checking and altering the router DHCP pool so later on the router assigns an IP that clashes (plenty of routers have a default DHCP pool that includes all available addresses on the subnet)
2 Likes
Me 
Me Me
3 Likes
I keep my DHCP scope to 10 addresses. If something gets one of these addresses, either I don't know what it is - so I hunt it down, it is a known MAC address that changes - so I change it to fixed MAC address, which leads to I know what it is, so I give it a reservation in the IP range for that device type. Example,
15 - 20 : Apple TV's
21 - 40 : Apple HomePods & HP Mini's
41 - 50 : Apple iPhones and iPads
(Yes, we have a ton of Apple stuff, because it works (usually))
51 - 60 : Nest Smoke Alarms
You get the idea. I'm crazy.
Not crazy, just particular. I've done similar - media stuff, hubs, AP's and switches, appliances etc grouped. It's no fun when you look down a sequential list of IPs in your Unifi device list or IP scanner app and see that your Lounge ATV 4K is not immediately adjacent to your Bedroom ATV 4K - action is needed!
2 Likes
