Be469 driver not logging some events


#21

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.


#22

I'll need to see the log events for the skipped ones as well as your description of what the event was...


#23

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


#24

This will be fixed in platform version 2.1.3


#25

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


#26

Was this ever fixed?

I have the 468 and the lock-initiated 30 second auto-lock is not captured


#27

Can you enable debug logging in the driver, then let it auto lock, looking for logs similar to those above your post...


#28

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


#29

This is fixed in platform 2.1.4


#30

Here you go


#31

Thanks, this was locked via auto lock correct?


#32

Yes. Unlocked through the dashboard then I let it auto lock on its own


#33

this is fixed in platform 2.1.4