@mike.maxwell bump?
i need the following.
- enable debug logging in the driver.
- open a live logging window
- unlock the lock if its locked
- lock the lock via the schlage button
- unlock the lock via whatever...
- lock the lock via the driver command
- post the results
that is what i provided above..? 
it isn't, i need the debug logs to see the actual data sent from the lock, not just what the driver is reporting to hubitat
@mike.maxwell @rvrolyk my apologies then in that case! I enabled debug on the front deadbolt and the digital lock events app and filtered them to just those 2. Then I locked the door using the keypad logo press, unlocked it with the interior thumb turn, then locked it via hubitat. So the first lock event should be captured as 'physical' and the second lock event as digital.
There is a lot of log data here, but I only did those 3 things.
I learned from @aaiyer you can log the event description then have your code look for specific word "digital" from the event to trigger and execute your desired actions.
Maybe that'll work for your needs. Can you post a screenshot of your rule?
I used "Digital Lock Events", which to your point, scrapes the events and looks for 'physical' to trigger the virtual lock 'on' which turns back off in a second. The virtual lock on is the trigger for my subsequent rule that sets the virtual presence sensor for "Family misc," to departed.
The current issues is that keypad press isn't triggering the digital lock events even though it seems it should be. So we're looking at the events coming out of the lock to see if they're even being sent back to the hub correctly.
I apologize, I am not familiar with a virtual lock that looks at physical lock actions. Is that the "reliable lock" virtual driver from HPM? It didn't work for me when I tried it out.
I do know that that provided description logging method works without any additional apps or devices with the BE469.
thanks, i'll get back to you once I get a chance to go through this.
1 Like
i don't suppose you can send me the text of that, or a screen cap from a desktop browser, with so many line wraps from your cell phone its difficult to decode...
dev:4562023-04-04 16:17:27.585infoFront Door Deadbolt battery is 79%
dev:4562023-04-04 16:17:27.583debugBatteryReport: BatteryReport(batteryLevel:79)
dev:4562023-04-04 16:17:27.578debugparse: zw device: 3F, command: 8003, payload: 4F , isMulticast: false
dev:4562023-04-04 16:17:27.008warnskipped alarmType:24
dev:4562023-04-04 16:17:27.004debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:24, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:3, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:4562023-04-04 16:17:26.997debugparse: zw device: 3F, command: 6C01, payload: 04 08 71 05 18 01 00 FF 06 03 , isMulticast: false
dev:4562023-04-04 16:17:26.430infoFront Door Deadbolt is locked [digital]
dev:4562023-04-04 16:17:26.427debugDoorLockOperationReport: DoorLockOperationReport(doorLockMode: 255, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 0, doorCondition: 0, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)
dev:4562023-04-04 16:17:26.412debugparse: zw device: 3F, command: 6C01, payload: 03 07 62 03 FF 00 00 FE FE , isMulticast: false
dev:4562023-04-04 16:17:23.023debugrefresh()
dev:4562023-04-04 16:17:22.805warnskipped alarmType:24
dev:4562023-04-04 16:17:22.802debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:24, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:3, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:4562023-04-04 16:17:22.795debugparse: zw device: 3F, command: 6C01, payload: 02 08 71 05 18 01 00 FF 06 03 , isMulticast: false
dev:4562023-04-04 16:17:22.217infoFront Door Deadbolt is locked [digital]
dev:4562023-04-04 16:17:22.214debugDoorLockOperationReport: DoorLockOperationReport(doorLockMode: 255, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 0, doorCondition: 0, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)
dev:4562023-04-04 16:17:22.208debugparse: zw device: 3F, command: 6C01, payload: 01 07 62 03 FF 00 00 FE FE , isMulticast: false
dev:4562023-04-04 16:17:21.635warnskipped alarmType:24
dev:4562023-04-04 16:17:21.632debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:24, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:3, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:4562023-04-04 16:17:21.624debugparse: zw device: 3F, command: 6C01, payload: 20 08 71 05 18 01 00 FF 06 03 , isMulticast: false
app:18762023-04-04 16:17:21.098debugFront Door Deadbolt was unlocked
app:18762023-04-04 16:17:21.095debugUnlock event: lock : Front Door Deadbolt was locked [digital]
dev:4562023-04-04 16:17:21.048infoFront Door Deadbolt was locked [digital]
dev:4562023-04-04 16:17:21.045debugDoorLockOperationReport: DoorLockOperationReport(doorLockMode: 255, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 0, doorCondition: 0, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)
dev:4562023-04-04 16:17:21.037debugparse: zw device: 3F, command: 6C01, payload: 1F 07 62 03 FF 00 00 FE FE , isMulticast: false
dev:4562023-04-04 16:17:16.776debugsupervision report for session: 24
dev:4562023-04-04 16:17:16.773debugparse: zw device: 3F, command: 6C02, payload: 18 FF 00 , isMulticast: false
dev:4562023-04-04 16:17:15.820debugsupervision report for session: 24
dev:4562023-04-04 16:17:15.817debugparse: zw device: 3F, command: 6C02, payload: 98 01 07 , isMulticast: false
dev:4562023-04-04 16:17:12.985debugnew supervised packet for session: 24
dev:4562023-04-04 16:17:12.982debuglock()
dev:4562023-04-04 16:16:57.952infoFront Door Deadbolt battery is 79%
dev:4562023-04-04 16:16:57.949debugBatteryReport: BatteryReport(batteryLevel:79)
dev:4562023-04-04 16:16:57.931debugparse: zw device: 3F, command: 8003, payload: 4F , isMulticast: false
dev:4562023-04-04 16:16:57.135infoFront Door Deadbolt is unlocked [digital]
dev:4562023-04-04 16:16:57.133debugDoorLockOperationReport: DoorLockOperationReport(doorLockMode: 0, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 0, doorCondition: 2, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)
dev:4562023-04-04 16:16:57.130debugparse: zw device: 3F, command: 6203, payload: 00 00 02 FE FE , isMulticast: false
dev:4562023-04-04 16:16:55.604debugrefresh()
dev:4562023-04-04 16:16:53.351infoFront Door Deadbolt was unlocked by thumb turn [physical]
dev:4562023-04-04 16:16:53.347debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:22, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:4562023-04-04 16:16:53.341debugparse: zw device: 3F, command: 6C01, payload: 1E 09 71 05 16 01 00 FF 06 02 00 , isMulticast: false
dev:4562023-04-04 16:16:52.765infoFront Door Deadbolt is unlocked [digital]
dev:4562023-04-04 16:16:52.762debugDoorLockOperationReport: DoorLockOperationReport(doorLockMode: 0, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 0, doorCondition: 2, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)
dev:4562023-04-04 16:16:52.755debugparse: zw device: 3F, command: 6C01, payload: 1D 07 62 03 00 00 02 FE FE , isMulticast: false
dev:4562023-04-04 16:16:52.197debugskip cmd: ApplicationBusy(status:0, waitTime:0)
dev:4562023-04-04 16:16:52.170debugparse: zw device: 3F, command: 2201, payload: 00 00 , isMulticast: false
dev:4562023-04-04 16:16:47.624debugsupervision report for session: 23
dev:4562023-04-04 16:16:47.620debugparse: zw device: 3F, command: 6C02, payload: 17 02 00 , isMulticast: false
dev:4562023-04-04 16:16:47.084debugsupervision report for session: 23
dev:4562023-04-04 16:16:47.078debugparse: zw device: 3F, command: 6C02, payload: 97 01 07 , isMulticast: false
dev:4562023-04-04 16:16:45.547debugnew supervised packet for session: 23
dev:4562023-04-04 16:16:45.532debuglock()
dev:4562023-04-04 16:16:43.069infoFront Door Deadbolt was unlocked by thumb turn [physical]
dev:4562023-04-04 16:16:43.066debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:22, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:4562023-04-04 16:16:43.059debugparse: zw device: 3F, command: 6C01, payload: 1C 09 71 05 16 01 00 FF 06 02 00 , isMulticast: false
dev:4562023-04-04 16:16:40.810infoFront Door Deadbolt was unlocked by thumb turn [physical]
dev:4562023-04-04 16:16:40.807debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:22, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:4562023-04-04 16:16:40.798debugparse: zw device: 3F, command: 6C01, payload: 1A 09 71 05 16 01 00 FF 06 02 00 , isMulticast: false
dev:4562023-04-04 16:16:40.218infoFront Door Deadbolt was unlocked [digital]
dev:4562023-04-04 16:16:40.215debugDoorLockOperationReport: DoorLockOperationReport(doorLockMode: 0, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 0, doorCondition: 2, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)
dev:4562023-04-04 16:16:40.210debugparse: zw device: 3F, command: 6C01, payload: 19 07 62 03 00 00 02 FE FE , isMulticast: false
dev:4562023-04-04 16:16:39.634infoFront Door Deadbolt was locked by keypad [physical]
dev:4562023-04-04 16:16:39.631debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:18, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:5, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:4562023-04-04 16:16:39.624debugparse: zw device: 3F, command: 6C01, payload: 18 09 71 05 12 00 00 FF 06 05 00 , isMulticast: false
dev:4562023-04-04 16:16:39.047infoFront Door Deadbolt is locked [digital]
dev:4562023-04-04 16:16:39.044debugDoorLockOperationReport: DoorLockOperationReport(doorLockMode: 255, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 0, doorCondition: 0, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)
dev:4562023-04-04 16:16:39.037debugparse: zw device: 3F, command: 6C01, payload: 17 07 62 03 FF 00 00 FE FE , isMulticast: false
dev:4562023-04-04 16:16:34.468debugsupervision report for session: 22
dev:4562023-04-04 16:16:34.462debugparse: zw device: 3F, command: 6C02, payload: 16 02 00 , isMulticast: false
dev:4562023-04-04 16:16:29.054infoFront Door Deadbolt is locked [digital]
dev:4562023-04-04 16:16:29.050debugDoorLockOperationReport: DoorLockOperationReport(doorLockMode: 255, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 0, doorCondition: 0, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)
dev:4562023-04-04 16:16:29.044debugparse: zw device: 3F, command: 6C01, payload: 15 07 62 03 FF 00 00 FE FE , isMulticast: false
dev:4562023-04-04 16:16:25.255infoFront Door Deadbolt was locked by keypad [physical]
dev:4562023-04-04 16:16:25.252debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:18, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:5, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:4562023-04-04 16:16:25.183debugparse: zw device: 3F, command: 6C01, payload: 14 09 71 05 12 00 00 FF 06 05 00 , isMulticast: false
app:18762023-04-04 16:16:24.652debugFront Door Deadbolt was unlocked
app:18762023-04-04 16:16:24.649debugUnlock event: lock : Front Door Deadbolt was locked [digital]
dev:4562023-04-04 16:16:24.596infoFront Door Deadbolt was locked [digital]
dev:4562023-04-04 16:16:24.593debugDoorLockOperationReport: DoorLockOperationReport(doorLockMode: 255, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 0, doorCondition: 0, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)
dev:4562023-04-04 16:16:24.561debugparse: zw device: 3F, command: 6C01, payload: 13 07 62 03 FF 00 00 FE FE , isMulticast: false
@mike.maxwell hope these are better, agreed it's a lot to look through. Same steps - physical lock was done first, then manually unlocked with thumb turn, then locked through hubitat command.
It definitely looks like the lock is sending 'mixed messages' when locking via keypad press, but even so, it's sending that event (along with digital for some reason), but not sure why 'digital lock events' isnt' picking it up.
1 Like
The driver is processing two sets of commands related to the lock/unlocked status.
The events being processed buy the DoorLockOperationReport do not reflect the correct physical/digital status.
I'm going to add a preference in the driver to ignore these reports, once enabled that should allow you to process digital/physical correctly.
2 Likes
Ok, awesome and thanks so much for digging through this and being patient with me!
What do I need to do on my end? Will this just be in the next platform update release for me to update as normal or do I need to get the driver version specifically somewhere else?
one of the next releases will have a preference for this in the Schlage BE468/BE469 Lock driver
5 Likes
Hey Mike -
I was messing with this again the other day and couldn't remember why I had untoggled that option you created for the driver.
Turns out, if the option is toggled true, the lock button press from the exterior side shows the door as locked properly but unfortunately it shows as unlocked if locked either from a hub command or physically turning the thumblock from the inside.
If I disable that toggle, the lock reports properly as locked from either of those, but then of course the lock button on exterior doesn't register.
:-/ anything jump out or should I grab logs etc again? sorry to resurface this one...
Ill have a look
Great, thanks so much!
I'm hoping to be able to leverage that specific event to trigger other actions if at all possible.
