Z-wave enabled but offline after update

Get Help
1

Please provide your hub model (C7, C8, etc.) and its platform version from Settings>Hub Details.

Check out the following post for help troubleshooting problems and gathering details that will help others to identify and solve the problem you are experiencing: ‼ READ FIRST - Before Posting in Get Help

I just upgraded my C8-Pro from 2.5.0.159 to 2.5.1.139.

I did this using the “upgrade all devices" feature from other C-8 pro.

When it restarted, nothing (z-wave) was working. After a bit of digging, I saw this:

1000052452
10000524521344×2340 226 KB

I did a full power cycle and it came back working.

It just concerned and surprised me.

2

It is supposed to start on it's own.. And it did in beta.. Would you mind PMing me your hub id?

3

I just had the same thing happen to me after an update. Still down.

4

PMed you my HubID. After full 1 minute power down and reboot, everything seems to be up. So far.

5

Thanks

6

I had the same thing happen to me. Everything came back up after a restart.

7

I had the same issue. I attempted to disable the Z-Wave, thinking that restarting it would fix the issue. The Zwave settings screen stopped responding. I was able to reboot Hubitat (I have c8 Pro on Node zwave). It came up with Z-Wave disabled (my change). Re-enabling Z-Wave brought it back to the state it was before… enabled but offline.

I read this thread and tried another reboot. It came back fine.

8

Exact same thing is happening to me. I have two C8Pro hubs and updated the platform on both.

Both rebooted but showed no ZWave devices and ZWave not active. Rather than mess with it, I went back to the previous platform using the Diagnostics. That fixed it. I had just saved via a cloud backup so I restored just to be sure.

I’m a bit hesitant to try this again but, would like to have the latest platform.

Help!

9

Next build this will be fixed... If you already updated, a reboot will resolve it..

10

Thank you. I have not retried this. I’ll wait for the next rebuild.

11

Just noticed this part.. A restore is almost never needed and potentially a problem source as the entire NVM is erased and replaced.. I can only see a restore being needed if you accidentally factory reset the radio (this is not easy to do by mistake), and migration from one hub to another..