Devices In Scenes Triggering Very Slowly

  • 106 Views
  • Last Post 03 December 2015
brett.e.baldin@gmail.com posted this 02 December 2015

I have been putting together a few scenes where I use a light switch device as a trigger that will then control another Z-Wave switch or two and turn them on or off. The scenes run, but it can be over a minute between the time that I press the switch and the targeted devices turn on and off.

I have many other scenes set up using motion sensors, timers, and time triggers and these all execute almost instantly. It is only when I use one switch to trigger another that this long delay occurs. This happens with both Jasco and Enerwave hard wired switches. Note that if I use ICHA or the phone app to trigger these same devices individually they turn on and off immediately.

I have set up the scenes to try both 'when device is turned on or off' or setting the levels to '255 or 0' but neither makes any difference.

Any ideas on how to improve performance? Thanks.

Order By: Standard | Newest | Votes
rscott posted this 02 December 2015

I have been putting together a few scenes where I use a light switch device as a trigger that will then control another Z-Wave switch or two and turn them on or off. The scenes run, but it can be over a minute between the time that I press the switch and the targeted devices turn on and off.

I have many other scenes set up using motion sensors, timers, and time triggers and these all execute almost instantly. It is only when I use one switch to trigger another that this long delay occurs. This happens with both Jasco and Enerwave hard wired switches. Note that if I use ICHA or the phone app to trigger these same devices individually they turn on and off immediately.

I have set up the scenes to try both 'when device is turned on or off' or setting the levels to '255 or 0' but neither makes any difference.

Any ideas on how to improve performance? Thanks.


I suspect that InControl doesn't know instantly when the light is turned on or off. It would have to rely on polling the switch (which by default happens every 30 seconds if the network isn't being congested by other radio comms)... so the delay you are likely seeing is because of that. As soon as InControl discovers that the switch was used, it runs the scene.

You could probably confirm this by adding a notification or an email to the top of the scene list and watching when it happens; my guess is that you'll get the notification and then see all the lights turn on and that it'll be about the same time InControl polls the switch and discovers it's been turned on.

If the switch supports associations (Jasco does not, I'm not sure about Enerwave), then you could add the USB stick as an association and it should notify InControl immediately.

brett.e.baldin@gmail.com posted this 03 December 2015

Gave this a try but no success. I do have some additional information that I hope helps:

I checked the associations for the Enerwave switches (they can be associated with the Z-Stick successfully) by using Zensys. They were set correctly, but I went ahead and redid them again with return routes checked just to make sure.

When I trigger the lights from the ICHA client, or the Windows phone app, the second set of lights turns on and off instantly. If I trigger the light switch physically, I see a delay of between 30 seconds and 2 minutes. Traffic does not appear to be continuous or heavy in the network monitor. I could replicate this consistently. I set up the e-mail on the target device (after the device in the string and I got the e-mail as soon as the target device lit.

One other oddity is that the target device will appear in the e-mails to turn on, then off, then back on rapidly. This does not actually happen. The lights come on and stay on despite the extra e-mails.

Close