I am quite new to vera and have a few issues and questions. This is the first.
Sometimes the performance when triggering scenes is very sluggish. It can take minutes for a scene to trigger and then if I try to trigger it again since it did not run it will run two times when it decides to start.
I have three main scenes.
Turns on most light on our bottom floor ad it is triggered by different buttons and one fibaro wallplug s power consumption. The fibaro wallplug measures a plug from my alarm system that turns on/off a light when the alarm is armed. This turns on 6 z-wave lights and a few 433MHz plugs via an RFXtrx433E USB HA controller.
A scene for cosy lights when watching tv
Good night… turn most lights off
To the questions:
a) Is it possible to tell vera to turn on a specific light first without putting all the other light in a delayed action?
b) Would splitting the scene up into several scenes with the same triggers reduce the time from trigger until all lights are turned on?
c) Is there any other ways to speed up execution?
You want to put the devices that respond fastest at the beginning … and those that run slowest at the end.
Use the advanced Scene editor to see and control the order of device actions.
As @RichardTSchaefer stated, the advanced section will allow you to change the order and putting the fastest devices first will help a lot.
b) Would splitting the scene up into several scenes with the same triggers reduce the time from trigger until all lights are turned on?
No. Scenes are executed one at a time and device commands are executed one at a time. (Serially)
c) Is there any other ways to speed up execution?
Fast and slow are subjective. A scene turning on 6 lights should complete within 2 seconds at most. If your scene is taking longer than that to complete, after you click the Run button, then you probably have a poor mesh in your Z-Wave network. The solution to this is to add more mains powered nodes.
Also note that there is a difference between a scene taking seconds to complete and a trigger taking several seconds/minute to start the scene. It wasn’t entirely clear to me in your post, whether you were referring to trigger time, scene execution time or both.
If your post is referencing a delay in Vera receiving the trigger, then your issue is probably due to a lack of Instant Status in the triggering device. Without Instant Status, you will need to wait until Vera polls the triggering device and learns about a state change, which can take anywhere from seconds to over a minute. The solution to that, is to replace the trigger device with one that supports Instant Status. See Leviton Vizia RF+ and Cooper.
I actually have totally missed the advanced editor.
Is the order shown the order the actions are executed?
Do I need to delete all and add them in the order I want them to be triggered?
If all actions are handled serially what happens if I put a 10 minute delay in a scene?
Will other scenes be able to run during the delay?
I guess my delay when triggering a scene is when I press a z-wave button from NOD and it does not send the action immediately
That issue is probably true since I do have a few 433MHz nexa buttons and they are “fire and forget” and when using them the scene is triggered instantly.
Is there a way to force the z-wave buttons to send the command directly when pressed?
- Do I need to delete all and add them in the order I want them to be triggered?
Probably not all, but maybe.
- If all actions are handled serially what happens if I put a 10 minute delay in a scene?
- Will other scenes be able to run during the delay?
Yes, other scenes can run during the delay. In the scenario that you describe, the first scene runs instantly and creates a delayed action in memory that will execute after 10 minutes. But the scene is completed instantly and other scenes and actions can execute until that 10 minute delay is due. I was more referring to the serial execution of Z-Wave commands where the next Z-Wave command won't be sent until the previous is acknowledged or the timeout period has expired. This can cause a few seconds delay between each Z-Wave command, when the network is not optimal.
- Is there a way to force the z-wave buttons to send the command directly when pressed?
This is a possible on a very few devices that have a parameter to enable instant status, like Fibaro or Aeon relays. I have no idea what a NOD is.
