Looking for inspiration before I declare a dead hub...
Returned to my office after the Xmas break. I have a C7 hub on my LAN, that I'm now unable to log into.
Hubitat Elevation C7
Running 2.3.6.142
Connected via StaticIP on Ethernet
It is NOT available on the Static IP I set
I have changed the Ethernet cable for a known working one. I have changed the ethernet Port on the switch, and also replugged directly to the Router, no change.
I have reset the connection by holding the round bytton o nthe base of the hub for 7+ seconds
I have power cycled the hub, and the lights goes from blue to green in the expected time.
I have also held the reset button for 7+ secods while the power was off.
I have rebooted the switch and the router
The Router (and Fing on my 'phone) shows that there is no connection for this device. (It is showing my other two hubs)
I have run the findmyhub.hub.com page, and advanced discovery on the MAC address, with no success.
I am aware of the diagnostic page (8081) but as I am unable to reach that, as I dont have an IP address for the device!
Network settings show it was on DHCP. Struggling to make it switch to static IP, as it's telling that not being on the 169.254.11. will make it unresponsive. 8081 is available.
Holding the reset button for 7+ seconds is not resolving the problem, as it keeps rebooting to 169.254.11.xxx and it wont let me set a static IP address in the right range. I can't switch the WiFi as there is no internet connection to download the drivers.
Any further suggestions before I reset the box and reapply the backup?
At this point, I dont mind a DHCP that I can use (192.168.0.xxx) or a staticIP. When it was working before xmas, I had reserved the same IP on the router. That has now been removed.
DHCP doesnt change with the reset button (it reboots to 169.254.11.xxx) but with 8.8.8.8 as the DNS (I had input 1.1.1.1,1.0.0.1, so the reset button is making some change)
I cant set staticIP as it wont allow/save anything outside of 169.254.11.xxx
So, I soft reset the hub, and the restored version holds the same IP address - arrghhh.....
I'm going to leave off overnight, and have a think. Maybe BobbyD or @support_team has a biright idea on resetting the network settings beyond the reset button?
Set a reservation for the hub on you router using the MAC address found on the bottom of the hub. Then do the network reset by holding the reset button and see what happens. That should get you going again.
Thanks for the suggestion - but no dice - it's still using 169.254.11.xxx with a reserved IP set on the router.
I tried setting a staticIP and the error message I get is IP address must belong to subnet 169.254.11.xxx or you will not be able to communicate with the hub
This is a special IP that devices will pick when they are set to DHCP and they do not get any DHCP response. Are you 100% certain your hub can reach and communicate with the DHCP server (probably your main router)?
Can you just click OK and set it anyway or is it not allowing it? If you do screw it up and cannot reach the hub, the network reset will bring it back to the state it is already in, so no harm in trying.
Hub is directly connected to router, with a tested cable, on a known working port. Driving me crazy.
not allowing it.
Yep, did this, forced an IP in range allowed (169.254.11.100) used royter gateway (192.168.0.1) and 8.8.8.8 as the DNS. Lost the connection, reset with undersdide button reset to DHCP using 169.254.11.xxx
Makes no sense at all. Are you sure you do not have some sort of MAC filtering on the router? I would also remove ANY reserved IP settings for the hub or anything tied to its MAC on the router in case it is causing an issue. There has to be something going on with the router that is preventing the hub from getting a DHCP address.
Make sure your clock is set correctly (can check in diagnostic tool or hub details)
There might also be an endpoint where you can force a new IP on the static setting. I don't have record of it, but I am guessing there is one. Maybe someone else will know what it is.
You could also use the diagnostic tool to download your local backups and then do a soft reset on the hub. This would rule out any sort of settings or hub database issue causing the DHCP problem. If that fixes it, not sure how to get back to a working state while also restoring your backup though.
I agree. No MAC filtering on the router at all. This hub, on this router was working just fine before Xmas, no chnages, just left in my office over XMas break.
I'm going to take it home and try on my home network over the weekend.
Yep, confimred correct time and date set.
Yep, I have a backup, so in the scheme of things, worst case I have a dead hub.
Did a soft reset by the IP remains the same.
