Hub not responding after upgrade to 2.3.4.150

🛎️ Get Help
6

Ok, I tried a few more things:

  • Another soft reset. Powered down and unplugged for a few minutes, then let it reboot. No change.
  • Tried to put it into Safe Mode. No change.

The LED on the front is blue. I don't know what all that means. But it sure seems bricked.

7

Just linking this thread for reference

From the FAQ

My hub shows a permanent blue light, now what?

Try performing a factory reset by following the >following steps while you are on the local network:

  • Go to >http://192.168.X.XX:8081/factory/recovery and >select Start Factory Recovery. Then select >confirm.
  • Go to http://192.168.X.XX:8081/ and select >Download Latest Version. Then select >confirm.
  • Go to http://192.168.X.XX:8081/setup and wait >until it says You will be automatically redirected >to your Hubitat Elevation.
  • Unplug the hub from the wall outlet, wait 15 >seconds, then plug it in again.
  • NOTE: replace 192.168.X.XX IP with actual IP >address of your new hub as assigned by your >router.
8

Hmmm, if I click the "Download Latest Version" button, it asks me to confirm. I do, and then I get a big red error box saying "Could not fetch latest version information." That doesn't seem good.

9

Did your factory recovery work ok? I saw that there was a typo in the link and just fixed that

10

If you haven't already you probably should engage @support_team so they can start to look at your hub.

1 Like
11

For C-5 and newer hubs, a blue LED means that platform isn't starting. For C-4 hubs is normal. Can you please send a private message to @support_team so we can further investigate?

2 Likes
12

Yes, I will do that. Thanks!

3 Likes
13

Possibly hub cannot resolve the host name due to a dns issue?

Try doing a network reset with the hidden button on the bottom of the hub. Hold for 7-10s and let go, light should flash and it will reboot.

14

Ok, Hubitat support is working with me. Hopefully we'll find something in the engineering logs. And fortunately this isn't my main hub. Only 10 or 15 devices on it.

2 Likes
15

Ok, I wanted to circle back with the resolution. @gopher.ny was awesome to work with and ran me through some stuff. Looks like the startup "stuff" for the platform got messed up, in a way that soft resets wouldn't fix. (At least, that's my understanding.) Seems to have been a rare thing. I've never had an issue like this, through many many updates.

But here's what got me back working:

  • I ended up having to do a full reset.
  • When it came back, I used the Diagnostic Tool to set the platform to the same version as my latest backup.
  • After a few minutes, the "get started" pages appeared. Hooray!
  • I restored from my backup. Note that I was NOT expecting z-wave devices to work. I expected the full reset to reset the z-wave radio.
  • Well, I got lucky. It looks like the z-wave radio did not reset. All my z-wave devices are still working! I think that was also a bug, but I'm not complaining.
  • And then when I re-ran the 2.3.4.150 upgrade, it did it quickly with no problems.

Thanks to the folks in Hubitat support!

6 Likes
16

I have this same issue right now. Working with support to try and resolve it. The fact you had to do a factory reset doesn't give me hope. This is my main hub with 30+ devices on it.

That being said it makes me wonder how many of you run multiple hubs. If I'm going to stick with this platform I'm wondering if it would make sense to split my set up on to addition hubs so everything isn't affected when one hub goes down with an update.

17

A FULL reset, which @jwetzel1492 did, is not the same as a FACTORY reset. In fact, a factory reset is no longer available via the Diagnostic Tool.

It should be noted that a full reset does NOT reset either the z-wave or zigbee radios.

Therefore, a full reset followed by restoring a backed up database essentially restores your hub to a fully functional state. There is no need to re-pair any device, or recreate any app.

Not a bug. A full reset is designed not to touch either the zigbee or z-wave radio.

5 Likes
18

This is the only time since I have been on here I have seen an update take down a hub, so I would consider it rare. Especially rare since a soft reset did not easily fix it. Also, you have the choice of when to update, a some users only update when the major version has stabilized (so final 2.4.x version). Some people only update if there is a new feature they want to take advantage of.

4 Likes
19

That's interesting. In the diagnostic tool, the button says "Full Reset (deletes radio settings)".

2 Likes
20

Confirming that it does say it deletes.

image

2 Likes
21

Weird. I've done this once. And was explicitly told it did not touch the radios. That warning wasn't there in the diagnostic tool either.

22

Im thinking it was an ip address change. Just cause you could ping it doesn't mean it was the hub. Im thinking something else grabbed the ip. If it happens again check the router the see mac address.

23

This is a genuine, if rare, issue. We'll be rolling out an update to prevent it shortly.

6 Likes
24

Prevent is good, but will I be able to apply the update to restore my current nonworking hub?

25

@gopher.ny and @bobbyD set me up with some instructions on a FactoryRecovery and the new 2.3.4.153 version. Hub is operational again. The thought of potentially having to redo my full Zwave network had me stressed a bit. Not looking to spend more money on additional hubs, but it might be the best option. At least then if one hub goes down I'm not completely down. I really only use the hubs for the Zwave radio, all automation is done in HA