I’ve got hassio supervised running in VM on my windows 10 machine with a good zwave plus mesh network (aeotec z-stick gen 5, 24 devices around the ~1800sqft house). I am trying to replace my front door lock with a schlage be469zp but am having some trouble:
I was able to include the lock relatively painlessly (using Add Secure Lock) but had to do it by bringing the lock down to the basement right next to my VM/z-stick. Everything works great down there, but my front door is on the other side of the house. Now, there are at least 12 devices that are between the z-stick and where the lock would be installed, including 3 within 5 feet of the lock, so there should be no issue using the mesh network to route messages to the lock.
After inclusion, I’ve tried moving the lock halfway, doing a network heal, and then moving to its final spot but this doesn’t work. The lock always ends up being reported as Dead once it is moved to the front door.
Is the lock unable to use the network to communicate because it was added securely vs all the other lights/switches weren’t?
Couple of thoughts.
1st - Are all of the other devices between the USB stick and the lock powered vs battery?
2nd - When you add it and then move it farther away after inclusion, it’s Neighbors (the other devices it’s gonna reach out to talk to when zwave starts) are no longer close to it. It “should” not be a problem, but definitely can be.
Try adding it in your basement where your stick is.
Restart HA/zwave. Verify it’s good to go and complete’s the zwave startup
This might be unneeded, but…
move it about 1/2 way. Do a zwave network heal. That will cause the devices to update thier neighbors.
move it the rest of the way, wait a few minutes, heal again. last, unplug lock, and plug back in. Wait a few more min,
Restart HA/zwave again, and see if it’s any better.
These steps are based on my not knowing how far away your lock really is from the USB plug, and how many devices you have that are powered (not battery) between the USB and lock. I will say that almost every time a person has an issue like yours its usually the zwave mesh. Even though it seems like it should not be an issue.
All the devices between the stick and the front door are powered. And the 3 devices within earshot of the front door where the lock would be never have any issues responding. I haven’t tried restarting HA in between, so I’ll give that a go and report back
So I removed the node, factory reset the lock, excluded, re-included, restarted, made sure it completed startup. I then moved the node halfway (which is still within 20ft of its original neighbor nodes) but the neighbor update failed
Trying to ‘refresh node’ leads to it being presumed dead
Did I get a dud?
Also I stumbled on another issue while verifying the lock completed zwave setup when it was right next to my zstick: HA is able to see me lock/unlock manually/using the keypad and reports those changes almost instantly. However, when i try to lock/unlock remotely using the lock.schlage… entity, nothing happens
Looks all good on the surface. I also think that the old OZW has a bit better stability at the moment.
I will say I dont think you have a dud, When you say mention unlocking/locking from HA, you mean it does not lock/unlock or does not report lock/unlock
Thanks. I do add via ‘add secure node’ and also have a network key set. The OZW logs dont give me any error that the network key was not set upon starting the network.
I did swap the unit for another one and I am getting the same issue. I can include it right next to the stick, but once I move it ~15 ft away I can’t update neighbors and it gets reported as dead
My only other thought here is that all of my other 25 devices were added as non-secure nodes. I had thought that these would still be able to route messages between my lock and my zstick, but perhaps I was wrong? Should I try readding some of these devices as secure nodes?
I don’t really want to start my zwave network from scratch but I’ll do it if it really comes to that