You can do something like this.
Make sure add a delay is the set response section of the security section of STHM.
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.
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.
My Schlage z wave (non-plus) lock has always shown battery level at 100%. This happens with ST driver and your driver. Any idea why? I’ve been using your driver for a couple years and battery always shows 100%. Thanks for any help you can provide.
The driver reports the value that the lock returns. Use the ST CLI to do driver logging via “smartthings edge:drivers:logcat”. Do a refresh on the lock in the app and look for the battery value being returned from the lock.
Hey Bruce,
I’m a mid-level user of ST so I’m not sure what I’m supposed to do with the info you provided me. Can you explain?
The ST CLI is a command line tool that runs on Linux/Windows/macOS that allows you to interact with the ST APIs and with your hub. Using the command I cited, you can see what the hub is sending to the device and vice versa. Once you have it downloaded to a computer and are running the command, you can refresh your lock status by either pulling down on the device detail page in the ST app or by using the Refresh command in the AWA. That will force the device to send a configuration report to the hub which includes the battery level allowing you to see what battery level the device is reporting to the hub.
My battery level is also reporting as 100% on two locks. In the AWA, I’m seeing that the last battery update for one lock was February 2 and the other was March 3. I did start CLI and enabled logging for the BP driver. I then refreshed the page. Here’s the log; I don’t see any mention of a battery level.
23 550e992e-d432-429b-9a61-5e906b735f03 Z-Wave Lock BP
...
──────────────────────────────────────────────────────────────────────────────────
? Select a driver. 23
connecting... connected
2026-05-22T03:41:22.115063157Z TRACE Z-Wave Lock BP Received event with handler capability
2026-05-22T03:41:22.116320323Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"main","named_args":{},"positional_args":{}}
2026-05-22T03:41:22.125774282Z TRACE Z-Wave Lock BP Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:22.141106823Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={}, cmd_class="DOOR_LOCK", cmd_id="OPERATION_GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2026-05-22T03:41:22.159996657Z TRACE Z-Wave Lock BP Z-Wave command(95849b97) queued for radio transmission: CC:Door Lock, CID:0x02
2026-05-22T03:41:22.167672782Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=3}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x03", src_channel=0, version=1}
2026-05-22T03:41:22.183731157Z TRACE Z-Wave Lock BP Z-Wave command(a9dc4680) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.202425698Z TRACE Z-Wave Lock BP Z-Wave command(ecfd20dc) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.203411323Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=4}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x04", src_channel=0, version=1}
2026-05-22T03:41:22.227034948Z TRACE Z-Wave Lock BP Z-Wave command(506b9003) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.228218323Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=5}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x05", src_channel=0, version=1}
2026-05-22T03:41:22.247073240Z TRACE Z-Wave Lock BP Z-Wave command(4bfc1533) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.248063240Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=7}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x07", src_channel=0, version=1}
2026-05-22T03:41:22.267417073Z TRACE Z-Wave Lock BP Z-Wave command(45505ae1) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.268416157Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=8}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x08", src_channel=0, version=1}
2026-05-22T03:41:22.274683032Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=9}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload=" ", src_channel=0, version=1}
2026-05-22T03:41:22.290719865Z TRACE Z-Wave Lock BP Z-Wave command(919dfff1) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.297076157Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=10}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="
", src_channel=0, version=1}
2026-05-22T03:41:22.313411198Z TRACE Z-Wave Lock BP Z-Wave command(f53f9482) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.334363740Z TRACE Z-Wave Lock BP Z-Wave command(0a7c59d6) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.335378573Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=11}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="♂", src_channel=0, version=1}
2026-05-22T03:41:22.358127532Z TRACE Z-Wave Lock BP Z-Wave command(083b4497) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.359106532Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=15}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x0F", src_channel=0, version=1}
2026-05-22T03:41:22.364679240Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:22.370218573Z TRACE Z-Wave Lock BP Received event with handler capability
2026-05-22T03:41:22.374291157Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received command: {"args":{},"capability":"refresh","command":"refresh","component":"settings","named_args":{},"positional_args":{}}
2026-05-22T03:41:22.377546323Z TRACE Z-Wave Lock BP Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:22.382538240Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={}, cmd_class="DOOR_LOCK", cmd_id="OPERATION_GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2026-05-22T03:41:22.399054907Z TRACE Z-Wave Lock BP Z-Wave command(499d6450) queued for radio transmission: CC:Door Lock, CID:0x02
2026-05-22T03:41:22.427959448Z TRACE Z-Wave Lock BP Z-Wave command(17ca68c0) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.428961240Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=3}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x03", src_channel=0, version=1}
2026-05-22T03:41:22.448388782Z TRACE Z-Wave Lock BP Z-Wave command(17463ebc) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.449390657Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=4}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x04", src_channel=0, version=1}
2026-05-22T03:41:22.455622698Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=5}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x05", src_channel=0, version=1}
2026-05-22T03:41:22.470639365Z TRACE Z-Wave Lock BP Z-Wave command(3eda6aca) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.489959782Z TRACE Z-Wave Lock BP Z-Wave command(2d8200f2) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.490978323Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=7}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x07", src_channel=0, version=1}
2026-05-22T03:41:22.496712573Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=8}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x08", src_channel=0, version=1}
2026-05-22T03:41:22.510921740Z TRACE Z-Wave Lock BP Z-Wave command(d8b75682) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.515935448Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=9}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload=" ", src_channel=0, version=1}
2026-05-22T03:41:22.532214865Z TRACE Z-Wave Lock BP Z-Wave command(e65f795b) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.550955698Z TRACE Z-Wave Lock BP Z-Wave command(67fcfe2a) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.551947823Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=10}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="
", src_channel=0, version=1}
2026-05-22T03:41:22.572560407Z TRACE Z-Wave Lock BP Z-Wave command(b96c2b44) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.573574990Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=11}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="♂", src_channel=0, version=1}
2026-05-22T03:41:22.593850490Z TRACE Z-Wave Lock BP Z-Wave command(6c48e29c) queued for radio transmission: CC:Configuration, CID:0x05
2026-05-22T03:41:22.594924698Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> sending Z-Wave command: {args={parameter_number=15}, cmd_class="CONFIGURATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x0F", src_channel=0, version=1}
2026-05-22T03:41:22.599457365Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:25.240743407Z TRACE Z-Wave Lock BP Z-Wave command(95849b97) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:25.830433365Z TRACE Z-Wave Lock BP Z-Wave command(a9dc4680) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:25.854978157Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:25.864502324Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=-1, parameter_number=3, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x03\x01\xFF", src_channel=0, version=1}
2026-05-22T03:41:25.868949324Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:25.871699490Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"keypadBeep","capability_id":"platinummassive43262.keypadBeep","component_id":"settings","state":{"value":"beep"}}
2026-05-22T03:41:25.885182407Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:26.551235199Z TRACE Z-Wave Lock BP Z-Wave command(ecfd20dc) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:26.849898491Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:26.854380991Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=0, parameter_number=4, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x04\x01\x00", src_channel=0, version=1}
2026-05-22T03:41:26.855654157Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:26.856399366Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"vacationMode","capability_id":"platinummassive43262.vacationMode","component_id":"settings","state":{"value":"off"}}
2026-05-22T03:41:26.883950699Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:27.141038782Z TRACE Z-Wave Lock BP Z-Wave command(506b9003) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:27.184945991Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:27.196662574Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=-1, parameter_number=5, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x05\x01\xFF", src_channel=0, version=1}
2026-05-22T03:41:27.197889866Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:27.201278782Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"lockAndLeave","capability_id":"platinummassive43262.lockAndLeave","component_id":"settings","state":{"value":"lockandleave"}}
2026-05-22T03:41:27.211432407Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:27.631573949Z TRACE Z-Wave Lock BP Z-Wave command(4bfc1533) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:27.654974199Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:27.656188157Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=3, parameter_number=7, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x07\x01\x03", src_channel=0, version=1}
2026-05-22T03:41:27.661780824Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:27.665165157Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"alarmMode","capability_id":"platinummassive43262.schlageLockAlarm","component_id":"settings","state":{"value":"forcedentry"}}
2026-05-22T03:41:27.677223907Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:28.132015157Z TRACE Z-Wave Lock BP Z-Wave command(45505ae1) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:28.154997407Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:28.159543241Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=5, parameter_number=8, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x08\x01\x05", src_channel=0, version=1}
2026-05-22T03:41:28.169184824Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:28.172007241Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"activitySensitivity","capability_id":"platinummassive43262.schlageLockAlarm","component_id":"settings","state":{"value":5}}
2026-05-22T03:41:28.183205491Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:28.630479407Z TRACE Z-Wave Lock BP Z-Wave command(919dfff1) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:28.654999241Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:28.656022741Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=5, parameter_number=9, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x09\x01\x05", src_channel=0, version=1}
2026-05-22T03:41:28.658943407Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:28.661745241Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"tamperSensitivity","capability_id":"platinummassive43262.schlageLockAlarm","component_id":"settings","state":{"value":5}}
2026-05-22T03:41:28.673102866Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:29.090524991Z TRACE Z-Wave Lock BP Z-Wave command(f53f9482) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:29.113805408Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:29.118250866Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=5, parameter_number=10, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x0A\x01\x05", src_channel=0, version=1}
2026-05-22T03:41:29.123500158Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:29.127466199Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"forcedEntrySensitivity","capability_id":"platinummassive43262.schlageLockAlarm","component_id":"settings","state":{"value":5}}
2026-05-22T03:41:29.138574741Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:29.542063324Z TRACE Z-Wave Lock BP Z-Wave command(0a7c59d6) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:29.565040991Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:29.567800199Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=-1, parameter_number=11, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x0B\x01\xFF", src_channel=0, version=1}
2026-05-22T03:41:29.573666449Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:29.577238574Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"interiorButton","capability_id":"platinummassive43262.schlageInteriorButton","component_id":"settings","state":{"value":"enable"}}
2026-05-22T03:41:29.591592949Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:30.031394574Z TRACE Z-Wave Lock BP Z-Wave command(083b4497) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:30.054952908Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:30.058553116Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=-1, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x0F\x01\xFF", src_channel=0, version=1}
2026-05-22T03:41:30.068016658Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:30.070821324Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"autoLock","capability_id":"platinummassive43262.autoLock","component_id":"settings","state":{"value":"autolock"}}
2026-05-22T03:41:30.082401824Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:30.244610366Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:30.254970491Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={door_condition=0, door_lock_mode="DOOR_SECURED", inside_door_handles_mode=0, lock_timeout_minutes=254, lock_timeout_seconds=254, outside_door_handles_mode=0}, cmd_class="DOOR_LOCK", cmd_id="OPERATION_REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\xFF\x00\x00\xFE\xFE", src_channel=0, version=1}
2026-05-22T03:41:30.259064699Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock
2026-05-22T03:41:30.264277949Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"locked"}}
2026-05-22T03:41:30.273860074Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:30.579861241Z TRACE Z-Wave Lock BP Z-Wave command(499d6450) transmit status: TRANSMIT_COMPLETE_FAIL
2026-05-22T03:41:33.699886533Z TRACE Z-Wave Lock BP Z-Wave command(17ca68c0) transmit status: TRANSMIT_COMPLETE_FAIL
2026-05-22T03:41:34.180205491Z TRACE Z-Wave Lock BP Z-Wave command(17463ebc) transmit status: TRANSMIT_COMPLETE_FAIL
2026-05-22T03:41:34.683340242Z TRACE Z-Wave Lock BP Z-Wave command(3eda6aca) transmit status: TRANSMIT_COMPLETE_FAIL
2026-05-22T03:41:34.921936533Z TRACE Z-Wave Lock BP Z-Wave command(2d8200f2) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:35.221549908Z TRACE Z-Wave Lock BP Z-Wave command(d8b75682) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:35.245152825Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:35.249533158Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=-1, parameter_number=3, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x03\x01\xFF", src_channel=0, version=1}
2026-05-22T03:41:35.254098950Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:35.256884617Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"keypadBeep","capability_id":"platinummassive43262.keypadBeep","component_id":"settings","state":{"value":"beep"}}
2026-05-22T03:41:35.265852992Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:35.521597242Z TRACE Z-Wave Lock BP Z-Wave command(e65f795b) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:35.544957825Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:35.556014700Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=0, parameter_number=4, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x04\x01\x00", src_channel=0, version=1}
2026-05-22T03:41:35.557251242Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:35.558004200Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"vacationMode","capability_id":"platinummassive43262.vacationMode","component_id":"settings","state":{"value":"off"}}
2026-05-22T03:41:35.562398658Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:35.821793325Z TRACE Z-Wave Lock BP Z-Wave command(67fcfe2a) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:35.844988075Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:35.846717742Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=-1, parameter_number=5, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x05\x01\xFF", src_channel=0, version=1}
2026-05-22T03:41:35.852292742Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:35.855758825Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"lockAndLeave","capability_id":"platinummassive43262.lockAndLeave","component_id":"settings","state":{"value":"lockandleave"}}
2026-05-22T03:41:35.865766908Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:36.123491575Z TRACE Z-Wave Lock BP Z-Wave command(b96c2b44) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:36.144981867Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:36.154792825Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=3, parameter_number=7, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x07\x01\x03", src_channel=0, version=1}
2026-05-22T03:41:36.160273533Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:36.163267533Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"alarmMode","capability_id":"platinummassive43262.schlageLockAlarm","component_id":"settings","state":{"value":"forcedentry"}}
2026-05-22T03:41:36.172519783Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:36.421889242Z TRACE Z-Wave Lock BP Z-Wave command(6c48e29c) transmit status: TRANSMIT_COMPLETE_OK
2026-05-22T03:41:36.455438408Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:36.468274533Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=5, parameter_number=8, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x08\x01\x05", src_channel=0, version=1}
2026-05-22T03:41:36.469490075Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:36.470225283Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"activitySensitivity","capability_id":"platinummassive43262.schlageLockAlarm","component_id":"settings","state":{"value":5}}
2026-05-22T03:41:36.474916075Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:37.104144617Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:37.105149908Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=5, parameter_number=9, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x09\x01\x05", src_channel=0, version=1}
2026-05-22T03:41:37.106396533Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:37.107795617Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"tamperSensitivity","capability_id":"platinummassive43262.schlageLockAlarm","component_id":"settings","state":{"value":5}}
2026-05-22T03:41:37.126678950Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:37.685050742Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:37.686064575Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=5, parameter_number=10, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x0A\x01\x05", src_channel=0, version=1}
2026-05-22T03:41:37.687288534Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:37.688041867Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"forcedEntrySensitivity","capability_id":"platinummassive43262.schlageLockAlarm","component_id":"settings","state":{"value":5}}
2026-05-22T03:41:37.697486534Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:38.308365284Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:38.313111367Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=-1, parameter_number=11, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x0B\x01\xFF", src_channel=0, version=1}
2026-05-22T03:41:38.323725325Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:38.326597325Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"interiorButton","capability_id":"platinummassive43262.schlageInteriorButton","component_id":"settings","state":{"value":"enable"}}
2026-05-22T03:41:38.335907700Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:38.946752200Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:38.947772825Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={configuration_value=-1, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x0F\x01\xFF", src_channel=0, version=1}
2026-05-22T03:41:38.949012159Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2026-05-22T03:41:38.949772159Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"autoLock","capability_id":"platinummassive43262.autoLock","component_id":"settings","state":{"value":"autolock"}}
2026-05-22T03:41:38.953903784Z DEBUG Z-Wave Lock BP Front door lock device thread event handled
2026-05-22T03:41:39.944819950Z TRACE Z-Wave Lock BP Received event with handler unnamed
2026-05-22T03:41:39.950337200Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> received Z-Wave command: {args={door_condition=0, door_lock_mode="DOOR_SECURED", inside_door_handles_mode=0, lock_timeout_minutes=254, lock_timeout_seconds=254, outside_door_handles_mode=0}, cmd_class="DOOR_LOCK", cmd_id="OPERATION_REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\xFF\x00\x00\xFE\xFE", src_channel=0, version=1}
2026-05-22T03:41:39.954604784Z TRACE Z-Wave Lock BP Found ZwaveDispatcher handler in zwave_lock
2026-05-22T03:41:39.959109659Z INFO Z-Wave Lock BP <ZwaveDevice: d1f82018-57ed-45f5-bea2-fd92c988e39f [6F] (Front door lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"locked"}}
2026-05-22T03:41:39.968491909Z DEBUG Z-Wave Lock BP Front door lock device thread event handled