Yale YRD226-C42 yale-control4-3.c4z driver issue
Quote from C4Happy on February 25, 2023, 12:09 pmI installed a new Yale lock - YRD226-C42-619 into a 250 controller project - 2.10.6.
I have the yale-control4-3.c4z driver as shown on the C4 website - Control4 Driver Search
It identifies to the project with no problem and is connected to the General Control 4 relaysingle_doorlock_c4.c4i
The lock does provide feedback to composer showing its status as locked or unlocked
However I cannot control the lock using composer or the Android Lock.
I have done a device reset and removed everything from the project and re-added but no change.
My old Yale locks works when I re-add it to my project (but it has issues with battery drain and hence my reason for changing it)
When doing debugging in Lua it does show results but not conclusive to issues.
I have a custom button programmed to lock or unlock with the Android App
ReceivedFromProxy(): LOCK on binding 5001; Call Function PRX_CMD.LOCK()
PRX_CMD.LOCK
LockDevice:PrxLock
LockCom_Lock
Task Queue Add: name[lock] id[16]
Task timed out.
Task Failed: name[lock] id[14]
Re-queueing task (0 retries left).
Task Queue Insert: name[lock] id[14]
Invoking task: name[lock] id[14] (3 in queue)
ZL.logPacketTransmission(): class[Outbound] frameType[ClusterSpecific] clusterId[0x0101][DoorLock] commandId[0x00][LockDoor] sequenceNumber[0x1f]
ZigBee Details: disableDefaultResponse[false] manufacturerSpecific[false] manufacturerCode[] direction[ToServer] profileId[0x0104] sourceEndpoint[1] destinationEndpoint[1] packet[01 1F 00] payload[]
Task timed out.
Task Failed: name[lock] id[14]
ZL.logPacketTransmission(): class[Outbound] frameType[ClusterSpecific] clusterId[0x0101][DoorLock] commandId[0x00][LockDoor] sequenceNumber[0x20]
Invoking task: name[lock] id[15] (2 in queue)
ZigBee Details: disableDefaultResponse[false] manufacturerSpecific[false] manufacturerCode[] direction[ToServer] profileId[0x0104] sourceEndpoint[1] destinationEndpoint[1] packet[01 20 00] payload[]
Does anyone have any suggestions on what I may have overlooked?
Thanks everyone for your time reading this.
I installed a new Yale lock - YRD226-C42-619 into a 250 controller project - 2.10.6.
I have the yale-control4-3.c4z driver as shown on the C4 website - Control4 Driver Search
It identifies to the project with no problem and is connected to the General Control 4 relaysingle_doorlock_c4.c4i
The lock does provide feedback to composer showing its status as locked or unlocked
However I cannot control the lock using composer or the Android Lock.
I have done a device reset and removed everything from the project and re-added but no change.
My old Yale locks works when I re-add it to my project (but it has issues with battery drain and hence my reason for changing it)
When doing debugging in Lua it does show results but not conclusive to issues.
I have a custom button programmed to lock or unlock with the Android App
ReceivedFromProxy(): LOCK on binding 5001; Call Function PRX_CMD.LOCK()
PRX_CMD.LOCK
LockDevice:PrxLock
LockCom_Lock
Task Queue Add: name[lock] id[16]
Task timed out.
Task Failed: name[lock] id[14]
Re-queueing task (0 retries left).
Task Queue Insert: name[lock] id[14]
Invoking task: name[lock] id[14] (3 in queue)
ZL.logPacketTransmission(): class[Outbound] frameType[ClusterSpecific] clusterId[0x0101][DoorLock] commandId[0x00][LockDoor] sequenceNumber[0x1f]
ZigBee Details: disableDefaultResponse[false] manufacturerSpecific[false] manufacturerCode[] direction[ToServer] profileId[0x0104] sourceEndpoint[1] destinationEndpoint[1] packet[01 1F 00] payload[]
Task timed out.
Task Failed: name[lock] id[14]
ZL.logPacketTransmission(): class[Outbound] frameType[ClusterSpecific] clusterId[0x0101][DoorLock] commandId[0x00][LockDoor] sequenceNumber[0x20]
Invoking task: name[lock] id[15] (2 in queue)
ZigBee Details: disableDefaultResponse[false] manufacturerSpecific[false] manufacturerCode[] direction[ToServer] profileId[0x0104] sourceEndpoint[1] destinationEndpoint[1] packet[01 20 00] payload[]
Does anyone have any suggestions on what I may have overlooked?
Thanks everyone for your time reading this.

