I don’t believe such reference exists at the present time. In Version 1 there were Timers which are obviously “time” based activities. Macros were device “event” based activities that could optionally be gated with a time component. Version 2 has merged Timers and Macros into a single component called Actions but the concept of a “time” based activity and a device “event” based activity still exists. Some of the options make sense for a “time” based activity such as Sunset(+/-) , Sunrise(+/-) and Absolute. Other options, such as SunsetToSunrise, SunriseToSunset and Window make sense as options to time gate a device “event”.

If you have a question(s) about how to do something specific I’ll be happy to try and work up an example. With multiple Conditions which can be Anded and Ored together along with multiple Effects on a single Action, Version 2 Actions offers capability well beyond Version 1 Timers and Macros.

I’ll try to put some examples together however some clarification is needed. In the bedroom case are looking to cause the bedroom lights to turn On and Off at certain times, or only allow them to turn On and Off at certain times. It is the difference between a “time” based event to turn lights On and Off at a specific time or a device based “event” that is allowed to happen only at certain times.

This is an example of Action Interval, starting at 21:00:00 and reoccurring every 10 minutes, an ICON Switch is turned ON, followed 20 seconds later with an Effect that turns the ICON Switch OFF.

[attachment=1:mr9ebw3p]ActionInterval.JPG[/attachment:mr9ebw3p]

[attachment=0:mr9ebw3p]ActionIntervalCondition.JPG[/attachment:mr9ebw3p]

Saving an Action at 17:00 with a Condition 1 of “Random Time =”, specifying a random interval of 15 minutes resulted in the Action being triggered at…

17:03:56
17:16:56
17:19:56
17:42:56
17:50:56
18:03:56
18:06:56
18:29:56
18:42:56

Triggering an Action with “Random Time” by itself does not make much sense from a logical view point but it demonstrates what the option does. I think it makes more sense to combine (AND) two Conditions together to form a “Random” activity within a specific time period. Defining Condition 1 with a “Window”, say from 19:00 through 21:00, ANDing the “Window” Condition with a “Random Time” Condition 2 would create a random pattern of light activity during the period from 19:00-21:00.

You can define as many Actions as you need. V2 supports up to 5 individual Conditions that can be Ored and Anded together to control when and if a particular Action is triggered and then 5 (6 if using the Beta Harmony client) Effects that occur when the Action is triggered.

The Conditions and Effects apply to a specific Action only. There are no global conditions or effects. The HTML interface may carry over the input field values into the next Action definition but those values can be altered before the next Action is saved. There is no fixed limit on the number of Actions. With multiple Effects per Action the number of Action definitions needed may be less in V2 compared to V1. The number of Conditions and Effects per Action is 5 with HTML, 6 with Harmony client.

The underlying Action logic is the same whether the Action is defined through the HTML interface, Harmony client or XML API. Screen space is the limiting factor when using the HTML interface.