2.4.4.132 Will not go past boot screen

I have a C8-Pro and can't upgrade to the latest hub version via the default Hub Upgrade tool. I have seen that issue three times in the past as well. First time I experienced this I could reboot the hub, and then the upgrade went through without issues. The second time, reboot did not help and I had to go via the Diagnostics Tools, but eventually the upgrade went through.

The failure mode in "standard hub upgrade" is always Download ... -> Verifying ... -> Extracting ... -> Download failed

This time however the hub won't boot up after updating to 2.4.4.132 (using the Diagnostics Tool). It gets stuck in the UI loading screen at 5%, and I had to revert to 2.4.3.177 to get the hub back. I have also tried a Soft reset of the hub without any different behaviour.

Any hints or help will be greatly appreciated.

I would try doing a soft reset, then before restoring the backup update via the diagnostic tool. See if it will boot with a clean database.

2 Likes

Yes, I had the same thought after writing this post.

I tried a soft reset, then selected the latest version (before I restored any databases), however, that did not make any difference, it is still stuck in the loading screen. I even left it for 20 min without anything happening.

I don't know much compared to everyone else here but have you tried changing the ethernet speed in settings to anything other than what it is?

use auto unless you're going to strap the link settings at both ends

The advice in these situations (communication issues between hub and WAN) has been to change from the current setting (100 to Auto or Auto to 100) and try again. Changing the Ethernet connection speed setting seems to jiggle things enough to get the hub/router to renegotiate their connection and start working again.

From my enterprise gear networking days. Choosing 10, 100, or 1000 turns off auto negotiation. Unless the other end is the like wise set, it's attempt at negotiating will fail and so will default to 10 half causing the link to not come up. So either auto on both ends or strapped on both ends but never a hybrid arrangement. Was a bit curious hubitat exposed settings for 10-100 without also exposing the hdx-fdx options as well for when connecting through a hub instead of a switch.

Thanks for the suggestion, but I already went down the ethernet speed route several times without any luck I am afraid.

I am curious to know if it is just me that see this issue. As I wrote in my previous posts, the experience I've had is that my hub has become increasingly more difficult to upgrade for each round. I wonder if it is an hardware issue, or if it is some weird combination with my setup.

What I do know is that I do want to avoid a full wipe as long as possible. I am not looking forward to rejoining 100+ devices.

Yup - I'm not the guy to try to explain why it works, but it does, consistently, clear up communication problems where the hub isn't completing platform FW downloads in particular. Might help here as well, but :man_shrugging:.

3 Likes

Just adding this here as a reference

As stated, if I try to force an update via the "Diganostic Tool" the hub never boots past 5% hanging on the UI loading screen.

Have you tried rebooting network (cable modem/ONT, router, switche(s) between your hub and WAN), and then lastly reboot the hub again after that?

Finally solved. After many reboots, rounds in the Diagnostic Tool menu, the final solution ended up being quite simple: shutdown the hub from the Settings menu, unplug, both power and network cable and leave it unplugged for 30 min. When I started it up, I was finally able to go through the normal firmware upgrade.

2 Likes

Glad to hear it.

The 30-minute shutdown will put your Zigbee devices in what's called panic mode, where they rebuild their neighbor tables.

This should not cause any problems, really, but you might find some Zigbee devices could need a restart (unplug/replug), to reconnect.

1 Like