My hub never fully came back after this update, my c8 pro, my c8 updated just fine. The c8 pro is my main rules hub.
Anyone else noticing issues?
my rules hub quit working after the same update
2.4.3.167
The website for the hub will not even load, how can I roll back?
How can I rollback if cannot even get to the website?
What do you mean it never came back? What specifically?
1 Like
Normally http://<hubIPaddress>:8081 will give you the Diagnostic Menu even if the normal interface doesn't load.
I might try a database rebuild before rolling back though.
2 Likes
Every update results in a reboot, if your hub isn't on an IP reservation from your router, or fixed IP on the hub, then your IP address of your hub may have been changed by your router when the hub rebooted.
If you just want to roll back, and if your hub IP hasn't changed, then:
yourhubIPaddress:8081, PW is your hubs MAC address.
Choose the Restore Previous Version option.
But if you want to understand why things aren't working and fix them, answering Ricks question is a start...
4 Likes
What color is the hub's LED? Blue? Or green? If it is green, the most likely explanation is that your hub's IP address has changed. If it is blue, you should still be able to reach the diagnostic tool (port 8081) and roll back to a previous platform version.
1 Like
Use the Diagnostics Tool to roll back a version.
What color is the hub's LED?
1 Like
according to my router it is attached and ayt the ip it should be on, the site just will not load. I am not alone, search
2.4.3.167 and you will see others
one of my hubs a c8 does work, but it only handles zwave and just 1 or 2 rules. My main hub is the problem. I think it related to another post this morning about the hub unable to respond due to a heavy load
The indicator light is green. I did power it off and back on, it goes green as normal. This update did something.
This indicates the hub platform is running. Strongly suggests that the hub is not at the IP address you believe it should be at.
This happens after every single platform update. Some of them result from database corruptions. Many others from an unanticipated IP address change.
If you are unable to reach the Diagnostic Tool at port 8081, it would add credence to the consideration that the hub is not at the anticipated IP address. The Diagnostic Tool runs in a separate JVM from the hub platform. It is updated very infrequently. And was not updated recently.
5 Likes
I don't care about your credence, it IS on the right IP, I have confirmed. Initially right after the update it did boot but quickly became non-responsive, now it just hangs, but not like it cannot find it on the IP and it has a dhcp reservation..
What about the Diagnostic Tool? Are you also unable to reach that port?
1 Like
no, that hangs same, getting too long to respond, not 404
Is your hub connected via ethernet or WiFi? Can you ping the hub at the anticipated IP address?
does not ping. Router still says it is connected to 142, on a wire.. When the hub did geta new ip in the past I see it on the router and the android app, both say it is on 142
feels like hub factory reset time, waiting on @gopher.ny to get back on that
Can you try a network reset? Using the button on the underside of the hub?
Sometimes, if the hub doesn't get a DHCP response during boot, or if there's a malformed DHCP response, the hub gets a self-assigned IP address in the 169.254.0.0/16 range (APIPA range). And this APIPA address seems to stick until a network reset is performed.
When this happens, the DHCP server will continue to display the hub as being assigned the anticipated IP address.
How would one perform a factory reset if the Diagnostic Tool cannot be reached?
2 Likes
Please do the following on your PC. (I'm assuming that your hub is hard wired and not on wifi)
Step 1: Download advanced port scanner (free tool) and install it.
Step 2: Press and hold the NETWORK reset button on the bottom of the hub (THIS ONLY RESETS THE NETWORK NOT HUB) using a toothpick or paperlclip for 7 or more seconds. (Must be at least 7) This will be the only round hole out of all the square holes.
Step 3, Open advanced port scanner on your PC and run a scan of your subnet. Once you confirm the IP (we want to do this outside of your router) go to the hub using the browser on your PC. Then confirm you can get to yourhubip:8081
2 Likes
FWIW, it is rarely that time. Happens, but not common. 
1 Like
The network reset brought it back, can get to it now. And it is on the correct IP,
2 Likes
