August Pro Z-Wave Lock doesn't handle jammed lock alert

🛎️ Get Help
, ,
1

I was able to discover one of my August Pro locks with little difficulty, and it appears that it is paired to the C7 hub with S2 security. However, I tested and found that the driver logs a warning and doesn't change the lock state as I expected when the lock is jammed.

When this lock is jammed, the AccessAlarmReport (zwaveAlarmType == 6) is being sent with zwaveAlarmEvent == 11.

This is what the driver is logging:

2020-08-19 13:41:58.436 [warn]skipped zAlarmType:6, zAlarmEvent:11, alarmType:0]
2020-08-19 13:41:58.432 [debug]alarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:, numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:11, zwaveAlarmStatus:255, zwaveAlarmType:6)

Shouldn't this raise an event with lock status as unknown instead of being skipped?

2

this will be fixed in the forthcoming hotfix

1 Like
3

@mike.maxwell Thanks!
Could you also look at adding support for zAlarmEvent:5 and zAlarmEvent:6 (locked/unlocked with keypad, respectively)?

[dev:65] 2020-08-23 10:06:03.703 [warn] skipped zAlarmType:6, zAlarmEvent:6, alarmType:0]
[dev:65]2020-08-23 10:06:03.699 [debug] alarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:, numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:6, zwaveAlarmStatus:255, zwaveAlarmType:6)
[dev:65] 2020-08-23 10:06:03.691 [debug] parse: zw device: 09, command: 7105, payload: 00 00 00 FF 06 06 00 , isMulticast: false
[dev:65] 2020-08-23 10:05:52.645 [warn] skipped zAlarmType:6, zAlarmEvent:5, alarmType:0]
[dev:65] 2020-08-23 10:05:52.641 [debug] alarmv2.AlarmReport: AlarmReport(alarmLevel:0, alarmType:0, eventParameter:, numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:5, zwaveAlarmStatus:255, zwaveAlarmType:6)

These are triggered if you have the august keypad paired with the lock.
Side Note: There is also a longstanding bug in the August firmware that will result in these keypad events in response to the zwave lock and unlock commands, instead of the usual zwaveAlarmEvent:3 and zwaveAlarmEvent:4 in some scenarios.

4

these will be updated in platform 2.2.4

5

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.