You can do something like this.
Make sure add a delay is the set response section of the security section of STHM.
1 Like
Does the Z-Wave Lock PH edge driver work with with Schlage Lock FE599NX? Works great with my BE469. Thank you in advance for your reply.
10 posts were split to a new topic: Problems setting autolock with Zwave Lock PH edge driver
A post was merged into an existing topic: Problems setting autolock with Zwave Lock PH edge driver
4 posts were merged into an existing topic: Schlage locks going offline/online
My lock was working on the beta driver since the switch to Edge, but sometime in the past few months it stopped reporting user codes. I had a couple of routines set up to run when specific codes were used, but they stopped working a long time ago and I didn’t realize until recently. I tried switching from the beta to the main driver release, it renamed all my codes to “Code 1,” etc. so I deleted them all and set them up again with the same names as before. The codes all work, the lock can be controlled through the app, but it reports “manual” for every unlock. Any suggestions on what I can try?
Edit: looking further into it, I don’t think the lock is reporting when it is unlocked by the keypad at all. When I go into the raw JSON in the web app, this is part of what I see:
“capabilities”: [
{
“id”: “lock”,
“version”: 1,
“optional”: false,
“status”: {
“supportedUnlockDirections”: {
“value”: null
},
“supportedLockValues”: {
“value”: null
},
“lock”: {
“value”: “locked”,
“data”: {},
“timestamp”: “2025-10-05T21:16:52.950Z”
},
“supportedLockCommands”: {
“value”: null
}
}
},
{
“id”: “platinummassive43262.unlockCodeName”,
“version”: 1,
“optional”: false,
“status”: {
“unlockCodeName”: {
“value”: “manual”,
“timestamp”: “2025-02-19T17:58:57.492Z”
}
}
}
The section for lock state correctly timestamps the last event from today. However, the section for unlocking, where the unlockCodeName is set to “manual,” is timestamped back in February. I’m thinking that is when it stopped reporting any keypad unlocks. I also noticed the lock state shows up correctly when unlocking via the app, but if I use the keypad, it doesn’t show as unlocked unless I also tap on it in the app. Any thoughts? These routines worked flawlessly for a long time and I’d love to get them working again!
The driver maintains the lockCodes capability which maps the codeSlot to the codeName and, unfortunately, any time you change the driver, it gets reset and the codeNames get changed back to the default of “Code x”.
It sounds to me like your lock is not reporting events correctly. What model is your lock and how old is it?
To see what is happening between the lock and your hub, I would suggest downloading the ST CLI so that you can do driver logging to see what is being sent to/received from the lock. From your Linux/Windows/macOS computer, use the command “smartthings edge:drivers:logcat” and select the lock driver. Then use the keypad to unlock/lock the lock using various codes, manually, and using the one touch. Cut and paste the output here using the Preformatted Text option in the + menu.
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.
I have that same lock (two actually) and it is correctly sending events. So yes, it should work.
Both the beta and production drivers should have that functionality, but if you change drivers you might have to re-enter names.
As for why your lock isn’t sending info, you can always try the “nuclear" option of factory resetting and then setting it up from scratch. Make sure you have a strong Z-Wave mesh to the lock location and that you get the S2 security to take.
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.
It does actually say ZWAVE_S2_ACCESS_CONTROL for Network Security Level. But underneath that, it says “Provisioning State NONFUNCTIONAL.” That seems like a problem - anything I can do about that?
That’s not a problem.
At this point, I’m concerned that there is something wrong with the lock itself. Couple of things you could try:
- Disconnect the battery for 30-60 seconds
- Factory reset the lock and then exclude/re-pair the lock
I’m also curious what firmware version the lock is running. That’s found on the back of the lock.
I’ve done battery pulls a couple of times in this process but I’ll do so again today. Unlikely to have a different result though. Firmware is version 0.11.0 per the label on the back of the lock. Manufacture date in 2021 if I’m reading it right. I found the Schlage device firmware page but not sure how to tell which firmware is the latest for my lock. Shouldn’t Z-wave+ devices do OTA firmware updates automatically?
11.0 does have a bug related to sending configuration reports after receiving the autoLock configuration command, but that wouldn’t be related to what you are experiencing. It sounds like the lock is simply not sending reports like it should after activities are being performed.
As far as updating the firmware, ST never made any provision for OTA for Z-Wave. You’d have to use a different Z-Wave controller that supports doing it.
I am having trouble with all 3 of my BE469ZP locks. Each time I go into the card for any of the locks I get an error message. The message is, “The device hasn’t updated all of it’s status information yet. Check again later.” If I swipe down on the card to refresh, I get a different message. The message is, “There was a problem connecting. Try again later.” I have swiped down more times than I can count but the errors persist. None of the features on the card are available except for the button to lock/unlock.
I have tried excluding and resetting the locks. I then add them again using your Edge driver, but the errors persist. All the locks have fresh batteries. One is 10 feet from my v2 hub and the other 2 are about 30 feet from the hub. All the locks worked perfectly before Edge drivers came out.
One of the locks also has a problem when I unlock the lock either using the card or in a routine. The lock will unlock and instantly lock again. When I reset the lock as I described above, the lock will unlock normally for a few times and then will revert to the problem I’m having with the lock/unlock issue.
What do I need to do to fix this? I have a lot of money tied up in these locks so replacing them with another lock is not a viable solution. I appreciate your time and effort.