I've been bench testing the HE for a couple of weeks, and everything was working fine. Initially, I used DHCP to dynamically assign an IP address, which turned out to be 10.x.x.154 (my DHCP range is 101 to 200). I like to use static IP addresses once everything "settles down", so today I changed the IP settings in HE to use 10.x.x.54, which I know isn't in use. I rebooted, and I could get to the HE using that IP address.
Next project was to install HPM. I got an error when adding the app (after pulling it in from git and saving it) that, based on some other threads, might be a DNS issue. Since I had just changed the IP address and added DNS servers, I figured I would go back to getting a dynamic DHCP address and dynamic DNS servers, so I made that change and rebooted.
Now I can't get to the HE at all. Neither IP address works. I opened Chrome, went to find.hubitat.com, and step 4 showed it as 10.x.x.154. I clicked on the link on that screen, and it timed out again. I tried getting to the HE diagnostic tool at port 8081, and that time out (for 10.x.x.54:8081 and 10.x.x.154:8081).
Any ideas? Assuming the IP address changed to some default value, any idea what that would be?
If you are accidentally blocked from accessing your hub due to an incorrect or unknown IP address setting, turn the hub over and use the point of a pen to press the small button just beneath the surface of the hub casing for at least 7 seconds.
Problem with that is my DHCP server forces you to use an IP address in its range. I have a habit of using the same IP address - 100, e.g., if the dynamic IP address for the device was 10.5.16.154, I use IP address 10.5.16.54 when I change it to static. No real reason for doing it that way, other than to let me know what devices were defined as static.
Why is a DHCP reservation address recommended over a static address?
To avoid the problem you just had. I couldn't give you much more than that. The NIC/driver on HE gets weird (technical term there) when you mess with the IP settings too much.
