[ST EDGE] Z-Wave Lock PH

[h0ckeysk8er (Bruce Pinsky)]

@mystwillow

Thank you, that was very interesting, if anticlimactic. Apparently the lock is sending nothing for events that happen at the lock (locking/unlocking manually, with user codes, or with the one touch button). It can still be locked/unlocked via the app and will show the correct status when doing that, but if I lock it from the app and then unlock it at the door by any method, it will still show as locked until I reload the app or restart the hub. It does get the correct status at those initial polls, but the timestamp is when the app or hub were restarted, not when the door was actually unlocked. The driver log only outputs anything at those times as well (locking/unlocking from the app or restarting app or hub).

So there is some connection/communication happening, but the lock itself is not talking, only answering. Is this something that would likely be solved by deleting and re-pairing? That’s a huge pain in the butt so I’d rather not choose the nuclear option if there’s anything else that could be tried first. Lock is a Schlage BE469zp and it was installed on the door in 2023. Worked flawlessly for over a year until a few months ago, likely February as noted in my previous post. Nothing else out of the ordinary happened on that date that I can recall. Any advice appreciated.

From the CLI, do “smartthings devices” to find the device number for the lock. Then do “smartthings devices device-num”. In the output, you will see the Network Security Level. I would be interested in what it says. If I were to take a wild guess, I’m guessing that S2 security is not properly negotiated between the hub and the lock. And in the Edge architecture, the hub is much more picky about it than in the old Groovy days. If it’s anything other than “ZWAVE_S2_ACCESS_CONTROL”, you’re probably going to have to exclude the lock and re-pair it to the hub. I would certainly try that before doing a factory reset.