Indigo Domotics

Is there any way to insert a delay into an action group? In my AV systems I need to turn several devices on but most of them go through a some kind of boot sequence that precludes accepting other config commands until the devices have finished booting. II'd like to be able to turn them on and then insert a delay into the action group to allow the devices to finish booting before sending more commands.

Oh for devices that will generate an event when they finish executing the last command. It would make life so simple.

The delay by checkbox at the bottom of each action is what you're looking for.

Ah, that wasn't clear to me. Thanks.

Does that delay before or after the command is executed?

Before.

Ah, got it. Thank you!

Oh, hey. Looks like delays are multi-threaded. If my action group is:

do A
do B
do C delayed by 15 seconds
do D

Thinking that I would get AB<delay>CD when the actual result is ABD<delay>C. That was a bit of a surprise. I would have expected the action group to proceed sequentially after the delay. Looks like I may need to put A and B into one action group and then C and D into another (call it Action2) and do:

do A
do B
do Action2 delayed by 15s

to get what I want. Can you confirm?

Thanks!

brianlloyd wrote:

Oh, hey. Looks like delays are multi-threaded. If my action group is:

do A
do B
do C delayed by 15 seconds
do D

Thinking that I would get AB<delay>CD when the actual result is ABD<delay>C. That was a bit of a surprise. I would have expected the action group to proceed sequentially after the delay. Looks like I may need to put A and B into one action group and then C and D into another (call it Action2) and do:

do A
do B
do Action2 delayed by 15s

to get what I want. Can you confirm?

Thanks!

Or delay D by slightly more than 15s.

Yeah, I figured that out but it gets awkward when I really want to do ABC<delay>DEFGHI.

But I appreciate the reply. Thanks.

brianlloyd wrote:

Yeah, I figured that out but it gets awkward when I really want to do ABC<delay>DEFGHI.

But I appreciate the reply. Thanks.

Yeah, that sounds like two action groups. Maybe a feature request for a "sequenced action group" is in order. Guaranteed in sequence, with delays as specified.

That request is on the list...

Figured as much. It's too obvious not to be.

This threw me off for quite a while as newbie. I just assumed actions would be executed in order otherwise why would there be a move up/down button!
Adding delays per action to get them to execute in order is a bit clunky in my opinion especially since the delay timers are all started at the same time.

kelmk wrote:

This threw me off for quite a while as newbie. I just assumed actions would be executed in order otherwise why would there be a move up/down button!
Adding delays per action to get them to execute in order is a bit clunky in my opinion especially since the delay timers are all started at the same time.

Yeah, what is the function to have a move up/down buttons if actions are multi-threaded? Could we have a checkbox to enable/disable multi-threaded action?

Thanks

Joel

Ordering the actions might make it easier to read. Agreed that it's somewhat misleading and we've got a few requests on the list along these lines.

The order is somewhat relevant, in that the order shown will be the order of execution for commands to the same interface or plugin. So if you are doing an INSTEON or Z-Wave scene then the commands will be sent to the PowerLinc or Z-Stick in that order. For example, in my nighttime "power house down" action group I have the most high-traffic lights turned off first and I don't care that the garage light is towards the bottom of the list (and will take several seconds to get to).