Zwave Lock Error with latest 2.2.4.156 on a C4 HUB

My Yale Zwave lock is now showing this error in the log. I'm using the "generic Zwave lock" driver.
Screen Shot 2020-12-04 at 11.18.43 AM

Update: I'm on a C4 HUB

I get a different result:

dev:128 2020-12-04 11:39:56.100 am info Yale Lever Lock was unlocked by Her[6:6]
dev:128 2020-12-04 11:39:56.080 am debug alarmv2.AlarmReport: AlarmReport(alarmLevel:2, alarmType:19, eventParameter:[99, 3, 2, 1], numberOfEventParameters:4, zensorNetSourceNodeId:0, zwaveAlarmEvent:6, zwaveAlarmStatus:255, zwaveAlarmType:6)
dev:128 2020-12-04 11:39:56.006 am debug parse: zw device: 33, command: 7105, payload: 13 02 00 FF 06 06 04 63 03 02 01 00 , isMulticast: false
--- Live Log Started, waiting for events ---

C-7 with v2.2.4.156

dev:128 2020-12-04 11:43:20.642 am info  code:8 fetched
dev:128 2020-12-04 11:43:20.637 am debug no changes to codeNumber:8, code:null, codeMap:[:]
dev:128 2020-12-04 11:43:20.629 am debug UserCodeReport- cmd: UserCodeReport(userIdentifier:8, userIdStatus:0, userCode:null)
dev:128 2020-12-04 11:43:20.620 am debug parse: zw device: 33, command: 6303, payload: 08 00 , isMulticast: false
dev:128 2020-12-04 11:43:20.004 am debug fetchLockCode- 8
dev:128 2020-12-04 11:43:19.999 am trace trying to fetch code:8
dev:128 2020-12-04 11:43:19.994 am info  code:7 fetched
dev:128 2020-12-04 11:43:19.989 am debug no changes to codeNumber:7, code:null, codeMap:[:]
dev:128 2020-12-04 11:43:19.984 am debug UserCodeReport- cmd: UserCodeReport(userIdentifier:7, userIdStatus:0, userCode:null)
dev:128 2020-12-04 11:43:19.978 am debug parse: zw device: 33, command: 6303, payload: 07 00 , isMulticast: false
dev:128 2020-12-04 11:43:19.407 am debug fetchLockCode- 7
dev:128 2020-12-04 11:43:19.402 am trace trying to fetch code:7
dev:128 2020-12-04 11:43:19.397 am info  code:6 fetched
dev:128 2020-12-04 11:43:19.392 am debug no changes to codeNumber:6, code:null, codeMap:[:]

Interesting.. power cycled it by doing batteries pull and now it's working. No more error.

1 Like

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