Yale locks in scene, frequent failures

[mcisar]

Am running 5.0.16 on my iSY994i, I have two Yale zwave locks that i'm trying to control and am running into some issues.   Individually I seem to be able to control the locks with no issues, however I've added them to a scene and in that scenario there seem to be frequent failures of the 2nd of the locks in the scene to lock. 

My zwave network consists of these two locks and a thermostat, and all 3 (along with the iSY) are within 10 feet of eachother currently.   The scene is simple, 'lock front door', 'lock back door'...  so I hope I'm not exceeding the complexity of anything   

There is a     [ZWAVE-RX-ST] Send queue full       error in the midst of the all the zwave 'transactions' that show in the log when the event fires so I'm assuming this is the point where things are going horribly wrong as there seem to be no further communications with the 2nd lock after that point  (but again if I go in manually and tell isy to lock it at this point, that works fine).    

Ideas, thoughts, condolences?

Thanks,
Mike

[lilyoyo1]

That's because you don't have any devices to take the load off the isy when talking to your devices. Unless you're willing to invest in at least 1 repeating device that supports beaming, you are better off using a program to accomplish talkimg to your locks versus a scene. 

When you depend on only your controller to talk to devices such as locks, it must first wake them up, wait for them to acknowledge, send the command, etc. Since this applies to both locks 1 can easily miss it's wake-up call as the controller also has to deal with other duties.

Beaming devices can hold this message and relay it to the appropriate device while the controller is busy doing what it's best at managing your system vs playing delivery guy waiting on something to happen.

When it comes to scenes, this information simply goes out. With programs, you can add a wait to it giving your lock and system the time it needs to process commands.