The "Wait" action inserts a pause in action processing. When a Wait action is placed between two Actions in an Event, the Event is suspended at the Wait action for the designated period of time. No further processing of the remaining Actions is done until the Wait period has elapsed. Wait actions are sequential. If there are two Wait actions back to back, each will pause the event in succession, making the Wait the sum of the two times. Here is an Example Event with 2 wait actions.
When the above Event is run, it will turn Device1 On, then the entire Event will pause for 10 seconds and execute the second action and turn Device2 On. After another 10 second pause the third action will be run turning Device 3 On. As you can see below, the three devices were turned on in succession with 10 seconds between each Action
.
The Event actually looks like this in terms of processing:
PAUSE 10 seconds
PAUSE 10 seconds
The Wait action also serves another purpose. When an Event is in a Wait state, it can be cancelled by the "Cancel Another Running Event" Action. This Action will ONLY work on an Event utilizing a Wait Action. An Event without Wait Actions is completed within milliseconds and therefore cannot be cancelled.
A Wait can be inserted between any Action or group of Actions. Here a Wait is at the top of the Event, with three Actions following. All three Devices will be turned on at once after a 10 second delay.
For short delays of a few seconds a Wait is generally more reliable and efficient than Delayed Events or Delayed Device actions. Those will be covered in another thread.
When the above Event is run, it will turn Device1 On, then the entire Event will pause for 10 seconds and execute the second action and turn Device2 On. After another 10 second pause the third action will be run turning Device 3 On. As you can see below, the three devices were turned on in succession with 10 seconds between each Action
.
The Event actually looks like this in terms of processing:
PAUSE 10 seconds
PAUSE 10 seconds
The Wait action also serves another purpose. When an Event is in a Wait state, it can be cancelled by the "Cancel Another Running Event" Action. This Action will ONLY work on an Event utilizing a Wait Action. An Event without Wait Actions is completed within milliseconds and therefore cannot be cancelled.
A Wait can be inserted between any Action or group of Actions. Here a Wait is at the top of the Event, with three Actions following. All three Devices will be turned on at once after a 10 second delay.
For short delays of a few seconds a Wait is generally more reliable and efficient than Delayed Events or Delayed Device actions. Those will be covered in another thread.
Comment