C8 Pro Z-Wave Issues post ZwaveJS

I have a C8 Pro. It had been working well for months on a PoE to USB splitter, but I decided to up-size to a slightly larger On-Q in-wall enclosure than what I had been using and while doing that I switched around the power setup to use a single splitter per device (instead of using a single PoE splitter and a USB splitter to power multiple devices). I thought this would be an improvement, but no matter what I did, the Z-wave connectivity was spotty. While doing some looking around on the forum, I found that the C8 Pro is extremely finicky about it's power and isn't tolerant of any sorts of fluctuations. I tried buying higher quality PoE Splitters (suggested here) and still had very little luck.

I ended up with a combination of a pass-through charging power bank and one of the Procet adapters, which did seem to work fairly well. But I didn't feel super comfortable having a growing collection of stuff providing power to my Hubitat. So a couple weeks ago I decided to bite the bullet and run an outlet into my in-wall enclosure. Things were generally much better once I did this and the Hubitat seemed to be stable.

Last week or so, some of my Z-wave switches started having spotty reception. I'd click a switch and it wouldn't react, clicking it again usually worked, though. This began getting worse and worse. The two I had some of the worst problems with were my Inovelli Red switches and my Zen 37 Multi-button scene controllers. All these devices were joined using Z-wave 800LR with a proper SmartStart adoption.

In fact, except for a few locks (Yale) and two RGBW light controllers, everything in my Z-wave network is 800LR (a couple dozen contact sensors, some motion sensors, and some temp sensors, around 40 devices in all and all Zooz).

So in looking to try and figure out what was going on and if there was a solution, I saw that there was an option to switch to ZwaveJS. I remembered from reading the forums that adoption of this was in development and it meant a potentially better experience. So I did a full backup to my Hubitat cloud backup and pulled the trigger to move to it hoping that even if it didn't solve the problem, that it might be able to provide more insight into it. Unfortunately when it came up after the upgrade things were even worse. I let it sit for a few hours to do the interview process for everything, but afterwards, it was still hit-or-miss. Things that had issue before were now showing as pending and nothing I did (wake ups on sleepy devices, refreshing them in the UI), fixed it. I decided it was a bust and went back to the Legacy Zwave.

Things were again a little better, but still worse than they had been. I tried restoring from my backup, switching back to ZwaveJS and back to Legacy again. Restoring again. Restoring an older backup. Doing a soft reset. Resetting the Zwave radio. Unplugging and re-plugging the hub. All in varying combinations. I've also tried different USB power adapters with no luck. Now I'm at a point where when the hub boots, the Zwave radio crashes almost immediately.

I'm out of things to try. I have a spare C8 Pro that I might try getting set up, but I'm reluctant to deregister my main C8 Pro if I don't need to. Can anyone help? I'm not sure what else to try.

Since you mentioned the POE and different power adapters I’m going to jump in and ask if you’ve tried the factory USB adapter? I know that shouldn’t matter as long as the specs are correct but it has come up often as a troubleshooting step so it probably wouldn’t hurt to check.

1 Like

Yeah, I considered that but I didn't, because I really don't know which one of the 30-40 or so USB AC power adapters I own is the factory adapter. Until recently I didn't realize that the C8 Pro was so touchy about power, so I never really kept track. If you want to post a picture of your factory power adapter, it might help me identify mine.

This is where it all went wrong. Restoring a Z-wave backup had zero chance of fixing anything. All you did was blow away all the routing info causing more issues. Then you kept messing with it making it worse and worse.

The actual solution would have been patience.

If you have a reliable 2A or greater power block, then you should be fine.

At this point I suppose my next steps would be

  • Download you known good local backups for safe keeping. Can get from the main UI or diagnostic tool. I would earmark the one you think will be best to restore to.
  • Since you already reset the zwave radio, lets reset it again and make sure its clear.
    • After rebooting, go to z-wave details, it should be blank.
    • Make sure it is set to legacy / ZIP
    • Checking the zwaveversion endpoint can give a hint if the radio is online. /hub/zwaveVersion (if you get a not found error radio is offline for sure)
  • Now with the clear radio, I would restore your most promising cloud backup, maybe from before this all started. Restore the Hub DB and Zwave, you can skip zigbee.
  • After reboot, double check and again verify you are on legacy ZIP
  • All the routes and neighbors will be cleared from loading the radio backup, so things may not immediately work perfectly.
  • Test some close to the hub devices and see if they will work.
  • Restore your best local backup if cloud backup hub database did not get you to the right spot, but I suspect the cloud backup should be good enough.

If radio is dead this will be the next thing to try. No need to de-register anything, just unplug it for now. You should actually be able to just load your cloud backup on the spare and most devices will connect right up.

Then you could submit a claim on the busted hub to get a replacement. From there you could transfer your Protect subscription to the now live hub.

2 Likes

Although I agree that I've probably caused more problems than I solved here, I'm a little confused by this. Which routing? I'm using almost entirely 800LR devices which, as far as I'm aware, are point-to-point.

Thanks for the guidance, I'll give this a shot.

Awesome, I wasn't sure what was involved, and I didn't want to leave myself even more stranded. Thanks

--
Ryan

I missed that part in your first post.
I would guess that other info about the devices may be wiped when you restore. Either way, any time you migrate or restore a z-wave backup in any way it disrupts everything for a little bit until it can sort itself out. Can take up to 48hrs for everything to fully settle in again when you have a typical mesh setup. I don't really have any info for recovery time on a primarily LR setup.

1 Like

Sorry for the late reply- not sure if this helps but here goes

1 Like

So, I tried the steps you suggested @jtp10181. The radio crashed immediately on boot after doing the radio reset. So I went ahead and switched over to my spare C8 Pro which seems to be working fine. Restoring my migration backup even restored connectivity to all my Z-wave devices. I tried filling out the warranty claim form (three times) and each time after I hit submit it just returned me to an empty form with no confirmation that it was submitted correctly. @support-agent can you help me?

Yup, thats how it should work, pretty nice to have that option.

It probably went through, @bobbyD can confirm.

Definitely nice. I was worried since it's technically the latest backup, which was after the major issues started. I guess it wasn't a problem with the configuration(s). I'm glad I had a spare Hubitat around.

Thanks for the help @jtp10181