Yale Conexis L1 Smart door lock status issues since 2.2.0 update

🛎️ Get Help
1

Since the 2.2.0 update I have had issues with my 2 Yale Conexis L1 smart door locks. Both are connected by the Yale z-wave module. I can lock and unlock them without issue however they will no longer recognise a change in lock state anymore. Maybe 1 out of ten times with the device lock status get updated. I have had to move to the generic z-wave driver to get them working reliably again but this looks like a driver issue since the update. Anyone else go the same issue or know of a fix

2

Is there anything showing up in the logs?

3

Logs below all operations except the most recent unlock that I did using the device page showed no change in the lock status. The door locks and unlocks fine with the device page and using dashboard, the the lock status that refuses to update

4922020-06-13 22:52:15.620 infoFront Door was unlocked via command [digital]

dev:4922020-06-13 22:52:15.617debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:25, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:0, zwaveAlarmStatus:0, zwaveAlarmType:0)

dev:4922020-06-13 22:52:15.609 debugparse: zw device: 0C, command: 9881, payload: 00 71 05 19 01 , isMulticast: false

dev:4922020-06-13 22:52:14.659debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:2, doorLockMode:0, insideDoorHandlesMode:0, lockTimeoutMinutes:254, lockTimeoutSeconds:254, outsideDoorHandlesMode:1)

dev:4922020-06-13 22:52:14.649 debugparse: zw device: 0C, command: 9881, payload: 00 62 03 00 10 02 FE FE , isMulticast: false

dev:4922020-06-13 22:51:33.499 infoFront Door was locked via thumbturn [physical]

dev:4922020-06-13 22:51:33.495debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:21, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:0, zwaveAlarmStatus:0, zwaveAlarmType:0)

dev:4922020-06-13 22:51:33.487 debugparse: zw device: 0C, command: 9881, payload: 00 71 05 15 01 , isMulticast: false

dev:4922020-06-13 22:51:32.508debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:1, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:0, lockTimeoutSeconds:0, outsideDoorHandlesMode:0)

dev:4922020-06-13 22:51:32.496 debugparse: zw device: 0C, command: 9881, payload: 00 62 03 FF 00 01 00 00 , isMulticast: false

dev:4922020-06-13 22:49:46.078 infoFront Door was locked via thumbturn [physical]

dev:4922020-06-13 22:49:46.075debugalarmv2.AlarmReport: AlarmReport(alarmLevel:1, alarmType:21, eventParameter:[], numberOfEventParameters:0, zensorNetSourceNodeId:0, zwaveAlarmEvent:0, zwaveAlarmStatus:0, zwaveAlarmType:0)

dev:4922020-06-13 22:49:46.034 debugparse: zw device: 0C, command: 9881, payload: 00 71 05 15 01 , isMulticast: false

dev:4922020-06-13 22:49:45.186debugDoorLockOperationReport: DoorLockOperationReport(doorCondition:1, doorLockMode:255, insideDoorHandlesMode:0, lockTimeoutMinutes:0, lockTimeoutSeconds:0, outsideDoorHandlesMode:0)

dev:4922020-06-13 22:49:45.129 debugparse: zw device: 0C, command: 9881, payload: 00 62 03 FF 00 01 00 00 , isMulticast: false

4

hmm .. interesting.
Did you try running a repair?

5

Not sure what you mean by repair. Switched them over to the generic z-wave lock driver and the lock status updates flawlessly. Switch back to cone is driver and stops updating again

1 Like
6

Worth noting this issue logged 23 hours ago, problems with an Alfred lock status, exactly same circumstances and started at the same hub update as me, maybe the issue not confined to just conexis, to much of a coincidence to to be connected

7

I'll check my locks for errors. I have a schlage and two Alfred

8

Ran a z-wave repair no change, everything must be working comma wise the the generic driver works perfectly