Summary: my all lights on scene turns 3 lights on instantly but the 4th light is delayed by a couple seconds. Using LUUP to turn the 4th light on first and the other 3 after makes them all turn on instantly. Why?
I have 4 lights in my kitchen hooked up to 4 different ZWave switches and I’m trying to figure out why there is a delay when I create a scene to turn them all on or off. Here’s what my setup is…
I created a scene “all on” and manually clicked the on button for the 4 lights. When I run the scene, lights 1, 2, and 3 (in that order) instantly turn on at roughly the same time but light 4 turns on about 1 to 2 seconds later. This happens every time I run the scene.
Second Attempt…
Created a new scene but this time I used LUUP code to turn the lights on in the order 1, 2, 3, 4. When I run it, it’s exactly the same as my first attempt. 1,2,3 instantly turn on and the 4th light is delayed
Third and final attempt…
Created a scene using LUUP to turn the lights on but this time I changed the order to turn 4 on first followed by 1, 2, and 3. When I run the scene, all the lights turn on in that order with no delay and roughly at the same exact time.
Why is this? I have a whole house All On and Off scene and the delays are pissing me off. Do I really need to spend a day figuring out the appropriate order to turn things on and off if I want it to happen instantly??
I’d have to see the logs to know for sure what is happening, but my guess is a routing issue. I’ve seen similar behavior many times in the past where, multiple devices in a scene react immediately, but one or more devices in the same scene take seconds to respond. In my experiences, the slow devices were sent commands on bad routes, the commands timed out and then the commands were resent on different/better routes and success.
The solutions varied. In some cases it was necessary to increase the density of the Z-Wave network by adding intermediate routing nodes. In other cases, it was enough to exclude the device, include it again and the add the newly included device to the scene.
Edit: Sorry, to answer your specific question, I suspect that the acknowledgment that the command completed successfully from switch three is following the aforementioned “bad” route and is causing the delay. When you run the alternative sequence you don’t notice the delayed acknowledgment. I suspect that you would see the delay in your log though.
Thanks Z-Waver, you got me looking in the right direction.
I tried manually routing all the devices which improved everything a bit, but there was still a little lag. It wasn’t until I went through all the devices in my network and clicked “update neighbor nodes” which solved all my problems.
Now not only do all my kitchen lights turn on and off in milliseconds, but my entire house all off scene runs in under a second vs about 10 seconds!
I learned a ton by researching routing and neighbors.
Sent from my iPhone using Tapatalk
Best Home Automation shopping experience. Shop at Ezlo!