Hubitat (sensibly) doesn't predict release dates for updates or fixes...best you'll get is "It's in the next release..." They are actively working on Z-Wave issues, but that's all we have at the moment.
3 Likes
Yeah, predicting future releases is a recipe for disappointment for sure. Though, so is this bug. It is an SI bug, so not the hubitat team's fault, per se. That being said would still like to know it hasn't fallen off the radar.
4 Likes
Hubitat engineers have this very high up on their radar. And a large engineering effort is directed solely at zipgateway issues. I would bet that we’ll see their engineering solution enter beta test within Q1 2025.
4 Likes
@aaiyar throwing down the (non-binding) date gauntlet to @bcopeland . 
Get cracking!
5 Likes
Right?! So brave of him...
4 Likes
I just had another GE switch go bad So I needed a replacement and I never got around to contacting Zooz about getting the Zen71 I thought was bad swapped out. So I decided to try one more time and see if I could get it to pair. I got it paired and it is working. It took a few tries and it, of course, created some ghost, but I got it going. Luckily this time all the ghost were able to be removed without breaking out the Z-Stick.
I think my problem was I kept trying to exclude and since it wouldn't, I never tried to include. Looking on the Zooz support site I happen to notice the quote below and never realized the 800 series chipset was different.
However, please note that exclusion before inclusion applies to the 700 series and earlier chip sets. The 800 series devices will not exclude before they have been included; please factory reset the unit instead, then try inclusion again.
Is this the case with all 800 series units? I don't remember ever seeing this mentioned before.
2 Likes
I got into a pickle when I tried to S2 pair all the new ZEN73 800LR switches on the second floor at the same time. I wanted to avoid walking up and down to the basement to flip breakers. Big mistake. I'd recommend only one at a time. This was pairing as LR. I wound up factory resetting them because of no response. Ghost city.
I'm now up to 10 irremovable ghosts, that seem to be just cosmetic because of LR. Hopefully that issue will be cleared up along with this one.
Starting to lose faith this will be addressed for non c8-pros. The gateway replacement (zwavejs) has mostly been an improvement on my c8-pro setups (after initial hiccups). However, none of those had this issue. The c8s apparently don’t have the resources needed to move to the new gateway code.
I know Hubitat is a small team and they are working hard on a lot of things but if the long term fix for this issue is zwavejs and c8s can’t run zwavejs, then what are c8 users suppose to do? Is the plan to just make c8 users pay more to update to a c8-pro? To make a warranty claim? Or am I just wrong in one of my assumptions?
I did upgrade from a C8 to C8Pro and I still have the same issue.
Did you try zwavejs? As I think the explanation we got for the issue was it had something to do with the SI Zip Gateway code being buggy. Switching to zwavejs should cut that out entirely.
I did.
I discuss in this thread, starting with that post.
Well dang it... I wish hubitat let us get access to the raw ZWave backups, at this point reverse engineering and patching the backup seems increasingly like the only course of action.
Pairing my first LR device and got this error. Looking through this thread it looks like I'm out of luck?
I just did a cloud restore, shutdown and re-joined but issue still persists. I have too many Z-Wave devices to start fresh.
What hub do you have. If it is a C8 Pro are you running zwave JS or thr legacy software.
I'm using c8 pro with legacy software. Is zwave JS recommended?
I have 32 Z-wave devices on my hub currently.
I would suggest switching to zwave JS and seeing if that resolves the issue. I am not 100% sure it will though unfortunately. This isn't something i have seen being stated that has been explicitly adressed with the switch.
Zwave JS has been shown to have its own set of issues for some users unfortunately. So it is understandable to hesitant to switch without a reason. Also immediately after the switch things can be a little rocky until the setup settles down and you may need to exclude and repair a few devices if they dont convert fully. I have a few Zen 34 remote switches i had to fix afterwards.
I also believe in 2.4.2 firmware it was made the standard zwave software for new setups. So it is in a way recommended when you consider that.
1 Like
Thanks for the insight. This hub is at my parent's house 400 miles away from me so will give it a try when I'm back in town for an extended period of time (during the holidays). Can't risk breaking everything during my short visits 
1 Like
This is absolutely the right choice. The update to zwavejs is not something which works well remotely. Especially if you have battery powered devices.
2 Likes
Or GoControl garage door openers. 
2 Likes
