i use rules for switchtching on my christmas lights for example.
having a common homeduino RF switch. now create a rule like
"when it is 18:00 THEN switch on xmas1 and after 2 seconds switch on xmas2 and after 4 seconds switch on xmas3 and so on …"
the time span between the switches do not summarize. you are counting the time always from the first switch (seen as zero time). then device 1 will switch on when rule is triggered, device 2 will be switched on 2 seconds after device 1, the third device will switch 4 seconds after the 1st device has been triggered.
this one here is not a good solution!
THEN switch on xmas1 and after 2 seconds switch on xmas2 and after 2 seconds switch on xmas3 …"
this might lead to collisions since device 2 and 3 will be triggered at the same time after device 1 has been switched.
hope i could make it a little bit understandable ^^
so you now could use a buttons device or maybe a dummy switch and use it with the rule from above.
“WHEN dummyswitch is switched on THEN switch on shellswitch1 and after 2 seconds switch on shellswitch2 etc…”
if using the dummy switch, you maybe can get rid of the shellswitches at all.
you could try to use rules then like “WHEN dummyswitch is switched on THEN execute `send send XXX X 1” but you also need an off command then. o, i see, maybe the shellswitch is a good option here.
if anybody else has a clue, go ahead