Quote from C4Happy on December 25, 2023, 12:15 pm

I have a YRD226-C42-619 with the AYR202-ZB-C4 module.

Project has an HC250 controllers. Patched to 2.10.6.561784.

Long story short - I had an older Yale lock that has worked perfectly for likely 8 years.  Module failed.

So bought a new Yale YRD226 with Control4 Zigbee Module.

It adds to the project with no issue.

I can get notifications of manual lock and unlock (through programming of events.)

Within 1 foot of lock is a LSZ-101 switch that controls the lights in the area of the entrance door.

Also within this space is a motion sensor that is connected for future alarm purposes but more so I have events that run that turns on the entrance lights.

Beyond the entrance is 3 more LSZ-101 switches that are basically 15 feet away from Door lock.

So everything else in the project works fine.  No delays, no anomalies.

So now to the issue at hand,  As mentioned the lock reports back to composer with its lock/unlock status. However I cannot use C4 to lock or unlock. I am using the driver  yale-control4-3.c4z which is the newest available.

Name:    Yale Smart Locks

Proxy:    lock
Manufacturer:    Yale
Model:    Assure, nexTouch, Doorman
Creator:    Yale
Control Method:    zigbee
Certified:    Yes
Creation Date:    06/07/2021 04:20 PM
Modified Date:    07/02/2021 03:46 PM
Version:    28
Device ID:    983
Proxy ID:    984
Device File:    yale-control4-3.c4z
Proxy File:    lock.c4i

So out of the blue on 3 occasions in the last year it will suddenly start working to lock and unlock and all control functions.  It works until I have an event such as a power outage or a controller reboot.

In terms of interference I have an AP in the Basement approx 20 feet from the entrance door above.

I have the 2.4 Channel down low and the Zigbee channel at 25 so no interference.

I have even shut off the wireless for testing and no difference.

I have even taken the lock out of the door and placed it in the middle of my house where there is definitely no concern of range or similar.

Thanks for any suggestions.  I have rebooted the lock(pulling batteries for hours at a time), wiped the lock and driver from my project, factor reset the lock many times and no change in behaviour.

The lock/driver is supposed to be compatible with the OS on my controller.

 

The strange thing is just out of the blue it starts working flawlessly.  It seems when it starts working it gets all the outstanding tasks as it will go through a lock unlock cycle for a while.  (I have nightly tasks for locking door so that would explain the catch up on events)

 

Thanks for any suggestions.  I don't think it has anything to do with interference and nothing in my project has changed prior to the lock replacement.   The old lock worked flawlessly until the module failed, so if interference etc it should have happened somewhere in the 8 years with the old lock.

 

 

Under the Driver Tab under LUA I get errors such as

Task Failed: name[set_time_zone] id[90]
Canceling task: name[set_dst_shift] id[89]. Task not run because previous necessary tasks failed.
Canceling task: name[set_time] id[88]. Task not run because previous necessary tasks failed.
Canceling task: name[get_date_time] id[87]. Task not run because previous necessary tasks failed.
Invoking task: name[end_super_procedure] id[86] (3 in queue)
Super Task Failed: name[sync_date_time] id[38]
Re-queueing task (0 retries left).
Task Queue Insert: name[sync_date_time] id[38]
Task Succeeded: name[end_super_procedure] id[86]
Invoking task: name[sync_date_time] id[38] (3 in queue)
Task Queue Insert: name[end_super_procedure] id[91]
Task Queue Insert: name[get_date_time] id[92]
Task Queue Insert: name[set_time] id[93]
Task Queue Insert: name[set_dst_shift] id[94]
Task Queue Insert: name[set_time_zone] id[95]
Super Task Start: name[sync_date_time] id[38]
Invoking task: name[set_time_zone] id[95] (7 in queue)
ZL.logPacketTransmission(): class[Outbound] frameType[Global] clusterId[0x000a][Time] commandId[0x02][WriteAttributes] sequenceNumber[0x16]
ZL.logPacketTransmission(): class[Outbound] frameType[Global] clusterId[0x000a][Time] commandId[0x02][WriteAttributes] sequenceNumber[0x16]
Task timed out.
Task Failed: name[set_time_zone] id[95]
Canceling task: name[set_time] id[93]. Task not run because previous necessary tasks failed.
Canceling task: name[set_dst_shift] id[94]. Task not run because previous necessary tasks failed.
Canceling task: name[get_date_time] id[92]. Task not run because previous necessary tasks failed.
Invoking task: name[end_super_procedure] id[91] (3 in queue)
Super Task Failed: name[sync_date_time] id[38]
Task Succeeded: name[end_super_procedure] id[91]
Invoking task: name[unlock] id[59] (2 in queue)
ZL.logPacketTransmission(): class[Outbound] frameType[ClusterSpecific] clusterId[0x0101][DoorLock] commandId[0x01][UnlockDoor] sequenceNumber[0x17]
ZigBee Details: disableDefaultResponse[false] manufacturerSpecific[false] manufacturerCode[] direction[ToServer] profileId[0x0104] sourceEndpoint[1] destinationEndpoint[1] packet[01 17 01] payload[]
ExecuteCommand(LUA_ACTION)
.   ACTION:  getBasicAttributes
Task Queue Add: name[get_basic_cluster_attributes] id[96]
Task timed out.
Task Failed: name[unlock] id[59]
Re-queueing task (3 retries left).
Task Queue Insert: name[unlock] id[59]
Invoking task: name[unlock] id[59] (3 in queue)
ZL.logPacketTransmission(): class[Outbound] frameType[ClusterSpecific] clusterId[0x0101][DoorLock] commandId[0x01][UnlockDoor] sequenceNumber[0x18]
ZigBee Details: disableDefaultResponse[false] manufacturerSpecific[false] manufacturerCode[] direction[ToServer] profileId[0x0104] sourceEndpoint[1] destinationEndpoint[1] packet[01 18 01] payload[]

 

 

Thanks in advance for suggestions as I am ready I think to abandon this lock with a C4 controller and perhaps buy the optional Zwave module and use Google Home to control it.

Take care