I guess that answers my question above about why you needed to re-pair all of your devices.
But now the question is why did you think you needed to factory reset everything after upgrading?
So⊠the solution was to to fix the user error rather than ranting about Z-Wave being no good?
2 Likes
I wouldnât go that far⊠Z-wave is a pita. Pairing it can be a convoluted, time consuming process and not at all user friendly, especially on Home Assistant.
I havenât found that at all. Each to their own.
Yea. Which is why it isnât necessarily user error. Once you factor in things like network topography, building size and construction, number and type of devices, etc the experience is pretty variable between users.
For example most instructions say to bring the device close to the hub when being paired. I have a set of homeseer motion flood light sensors mounted and hardwired outside by the roof. My âhubâ is a VM on a qnap nas locked in a basement server cabinet. The z-stick it uses is in the kitchen via a USB extension cable fished though the wall. How the flying F* is one supposed to accomplish what is asked in the instructions? Further more one of the sensors is on a detached garage at the back of the lot. Iâve been lucky I havenât had to re-pair that one yet. And when I initially paired it I actually slapped something together using a metal junction box, appliance cord, and lamp holder to make it mobile while being setup. That is decidedly not a user friendly thing to do.
Well you can unplug the z-stick to take it closer to the end device, not that I have found I need to so far.
Last I read when using HA, you have to pair using the UI. Using the z-stick by itâs self wonât work. Or has that changed?
Also getting close to those sensors involves a ladder.
I havenât tried pairing with the z-stick removed in a long time so maybe that is the case now, not sure, but I wouldnât have thought so given that the stick holds all the paired device info.
I paired two new devices a couple of months ago in situ from about 20m away from the z-stick, through multiple brick walls. Wasnât an issue at all
With the old OSW based integration it needed to see the device inclusion into the network.
My testing with zwavejs indicates that it does not need that. It reads the network information from the stick and then queries the device itself. For battery operated devices it can take several horus of the device is asleep a long time.
Nope, I followed every guide, The Solution was to factory reset everything, use a different addon on and get lucky.
I factory reset everything after the devices failed to pair when upgrading to zwavejs from the original zwave integration. Factory reset was not the first stepâŠ
Good to be lucky then.
I am not using a zwave stick, I have one. I have tried it and removing the stick caused more issues then just leaving it plugged in. I am using a Go control zwave/zigbee stick. You canât remove it.
You do not need to pair anything when moving from the old OZW to zwave js. In fact, it is normal that pairing will fail if you try, the devices are already paired. You just have to patiently wait for zwave js to understand the network from what it finds in the stick and by interviewing the devices. By trying to repair and factory resetting, you have completely disrupted this process.
1 Like
Thatâs all well and good if it worked. It didnât, I left it over night and not a single device paired itself again. Itâs great when they work like should but when they donât some times you do need to start over. This is an on going issue that has been a much bigger issue then this one upgrade. Itâs always been a pain to add zwave devices.
OK, then that brings me back to the original questionâŠ
Why did you need to re-pair them to the stick/controller just because you updated to zwavejs?
They should have always stayed paired.
I never experience this and I have a pretty extensive zwave network, both in terms of devices and distances. Even on the old OZW 1.4, pairing was always entirely non-problematic even on devices that are on the other side of my rather large house.
Maybe itâs bad luck, but I also suspect that it is mostly likely user error. The fact that you tried to repair thing shows that you didnât really understand the migration process fully.
They didnât repair automatically⊠Read my earlier post explaining this.
Again, I left them over night to repair themselves. Not a single device did.
Thatâs the thingâŠthey never had to âre-pairâ themselves. They were always paired.
Now, if they never showed up as complete in the interview stage then that is a completely different matter. But you definitely didnât do yourself any favors by trying to re-pair devices that were already paired to the controller.
and as alluded to above, if you didnât factory reset every device (not just the controller) then I can see why you were struggling to get them re-paired.
If you waited over night to get the devices to complete the interview process (especially for mains powered devices - those should be almost immediate) then there is something wrong with the zwavejs set up or your network mesh sucks.
Where were you looking to see if they ever completed the interview process? IOW, why did you think they werenât âpairedâ?
1 Like