In the logs you posted there are several of the above entries.
Skipped here means this data from the lock didn't create an event in the driver.
If you can tell me which lock action triggered these, I can add the missing ones to the driver.
Got you. Missing ones: Manual Unlock, Manual Lock and Autolock
Manual Unlock
Generic driver
dev:11552019-06-14 09:13:39.236 infoFront Door Lock was manually unlocked [physical][6:2]
dev:11552019-06-14 09:13:39.233 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:11552019-06-14 09:13:39.176 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 02 00 , isMulticast: false
Custom driver
dev:11552019-06-14 09:28:42.996 warnskipped alarmType:0
dev:11552019-06-14 09:28:42.991 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:2, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:11552019-06-14 09:28:42.703 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 02 00 , isMulticast: false
Manual Lock
Generic Driver
dev:11552019-06-14 09:13:56.238 infoFront Door Lock was manually locked [physical][6:1]
dev:11552019-06-14 09:13:56.236 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:1, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:11552019-06-14 09:13:56.229 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 01 00 , isMulticast: false
Custom Driver
dev:11552019-06-14 09:32:54.592 warnskipped alarmType:0
dev:11552019-06-14 09:32:54.590 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:1, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:11552019-06-14 09:32:54.578 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 01 00 , isMulticast: false
Autolock
Generic Driver
dev:11552019-06-14 09:12:07.177 infoFront Door Lock was autolocked[6:9]
dev:11552019-06-14 09:12:07.175 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:9, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:11552019-06-14 09:12:07.159 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 09 00 , isMulticast: false
Custom Driver
dev:11552019-06-14 09:29:13.818 warnskipped alarmType:0
dev:11552019-06-14 09:29:13.817 debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:9, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:11552019-06-14 09:29:13.810 debugparse: zw device: 3D, command: 9881, payload: 00 71 05 00 00 00 FF 06 09 00 , isMulticast: false
perfect, thanks!
Having issues with my BE469's and trying to troubleshoot. I notice that both of them report "locked [digital]" for physically turning the deadbolt with the inside thumb wheel. =/
Mike -
Just setup my Hub yesterday and I am having the same issues with the BE469 customer driver as aryvin. Logging shows all actions as skipped using custom driver. My logs for Manual Lock/Unlock are identical to aryvin's. As with his, the generic lock driver works where the custom one does not. Below are the log entries my additional skipped events not reflected in Aryvin's logs above.
Locking with Schlage Button:
dev:652019-06-26 01:36:09.969 pm warnskipped alarmType:0
dev:652019-06-26 01:36:09.965 pm debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:5, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:652019-06-26 01:36:09.935 pm debugparse: zw device: 03, command: 9881, payload: 00 71 05 00 00 00 FF 06 05 00 , isMulticast: false
Unlocked with User Code:
dev:652019-06-26 01:34:32.253 pm warnskipped alarmType:0
dev:652019-06-26 01:34:32.250 pm debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[4], numberOfEventParameters:1, zensorNetSourceNodeId:0, zwaveAlarmEvent:6, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:652019-06-26 01:34:32.233 pm debugparse: zw device: 03, command: 9881, payload: 00 71 05 00 00 00 FF 06 06 01 04 , isMulticast: false
I had re-added my lock using the new driver (going by this process Sweet Jesus - do the new Schlage drivers make a difference or what?!) and I'm having what appears to be the same issue you are having. My initial troubleshooting seemed like it would simply skip some lock events. It will sometimes report my wife opening with her code but not me with my separate code an hour later, or manually opening the door at 8am but not 9am as other people left. Rule Machine automations I have based on changing status of the lock do not function any more, as the lock / unlock status doesn't appear to get reported. This will work when I set it up and test, but after any amount of time it fails to report correctly. That said, I hadn't done proper testing to confirm the patterns you are picking out here.
I will do that testing and report back. I'm hopeful the changes Mike appears to be making to the driver will fix us both up, though.
these missing events should be fixed in release 2.1.2
2 Likes
Updated the hub with the new firmware 2.1.2.115. The BE469 manual locking/unlocking events are now recognized. But locking with the Schlage button and unlocking with user codes are still being shown as skipped events.
I'll need to see the log events for the skipped ones as well as your description of what the event was...
Here are logs of the skipped events:
Lock with Schlage Button:
dev:1932019-07-03 03:03:40.449 pm warnskipped alarmType:0, zwaveAlarmEvent:5
dev:1932019-07-03 03:03:40.446 pm debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:5, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:1932019-07-03 03:03:40.415 pm debugparse: zw device: 04, command: 9881, payload: 00 71 05 00 00 00 FF 06 05 00 , isMulticast: false
Unlock with User Code 4:
dev:1932019-07-03 03:03:47.087 pm warnskipped alarmType:0, zwaveAlarmEvent:6
dev:1932019-07-03 03:03:47.084 pm debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[4], numberOfEventParameters:1, zensorNetSourceNodeId:0, zwaveAlarmEvent:6, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:1932019-07-03 03:03:47.052 pm debugparse: zw device: 04, command: 9881, payload: 00 71 05 00 00 00 FF 06 06 01 04 , isMulticast: false
Unlock with User Code 5:
dev:1932019-07-03 03:10:41.738 pm warnskipped alarmType:0, zwaveAlarmEvent:6
dev:1932019-07-03 03:10:41.734 pm debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[5], numberOfEventParameters:1, zensorNetSourceNodeId:0, zwaveAlarmEvent:6, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:1932019-07-03 03:10:41.699 pm debugparse: zw device: 04, command: 9881, payload: 00 71 05 00 00 00 FF 06 06 01 05 , isMulticast: false
3 Likes
This will be fixed in platform version 2.1.3
Mike,
Just updated to firmware 2.1.3.120. The Schlage button event is being reported incorrectly. The event is showing as unlock event and as interior button. The Schalge button is an exterior button and it should be a Lock event not an Unlock event. Here is the log of the event below:
Locking with Exterior Schlage Button:
dev:1932019-07-26 04:39:22.360 pm infoTest Lock 2 was manually unlocked via interior button [physical]
dev:1932019-07-26 04:39:22.356 pm debugalarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:5, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:1932019-07-26 04:39:22.317 pm debugparse: zw device: 04, command: 9881, payload: 00 71 05 00 00 00 FF 06 05 00 , isMulticast: false
Can you enable debug logging in the driver, then let it auto lock, looking for logs similar to those above your post...
I'll try when I get home tonight. I want to say I had enabled debug logging before opening that, but I'm not 100% sure
This is fixed in platform 2.1.4
Thanks, this was locked via auto lock correct?
Yes. Unlocked through the dashboard then I let it auto lock on its own
1 Like
this is fixed in platform 2.1.4
2 Likes
