The last big change is often the best suspect...have you confirmed that the router IP reservation for the hub is outside your DHCP range?
There is a new platform version, 2.3.8.117 - you should update to that version so you're on the latest.
After you update your hub, there is a network reset button on the bottom of the hub...under the one round hole. Press that button for 7-10s and the hubs network settings will be reset to default and the hub will reboot.
As noted it's an option on routers, access points (APs), or switches - if you aren't familiar with MTU settings and haven't changed settings on your networking gear it's probably not an issue for you. If you have or can download the user manual for your router you can search in it for MTU settings - if MTU is greater than 1500 on it or other networking devices then that can cause disconnect problems the HE hub.
@thebearmay has a cool driver that allows you to monitor your hub info, including IP address. Once you install and setup his driver (create a virtual device using his driver) you can then create automations based on the states it tracks...i.e., a rule that says if ip address changes, send notification to me/turn a light red, etc.
OK, after power reset, soft reset and network reset, I installed HPM and Hub Information Driver and just when I wanted to apply the new rule, it went down (lasted 38 min).
Frustrating.
Power reset again, created a rule once again and applied. Now waiting.
How can I set up a rule to reboot the hub when it's IP changes? I went through the provided actions but can't find how to reboot or restart the hub.
Update:
The hub went down and I didn't receive the notification for the IP change.
I would not set that up to run reboot/rebuild every time...I'd have the normal reboot in the rule, and use the reboot w/rebuild option when you do a reboot manually.
Didn't help. Hub went down and the rule didn't activate, meaning that maybe the IP address didn't change.
I will try connecting it to a different router, but even if it works there's nothing I can do because I can't change out the provided ISP's device.
It becomes inaccessible through the browser on devices connected to LAN. I described the situation at the beginning of the thread/post. It's like it is off, but the green LED on it is lit.
Saw that but wanted to make sure that another condition hadn’t crept in as “down” and “inaccessible” are two different conditions in my mind.
May want to consider enabling the Extended Network Data, and sending out a notice every 10-15 minutes with the localIP, lanIPaddr, dnsStatus, dnsServers attributes