Rule Machine is the most powerful built-in tool for creating custom automations in Hubitat Elevation.
Tip: Rule Machine is very powerful but can be somewhat complex for new users. Before using Rule Machine, you may wish to consider if another built-in app (e.g., Notifications, Room Lighting, or Basic Rule for simpler custom automations) meets your needs.
NOTE: Rule 4.1 and prior versions are found under the Rule Machine Legacy app, which is what the previous Rule Machine "parent" app has been renamed to. Rule 5.0 and newer versions are found in the "new" Rule Machine app. There is no need to change or "upgrade" (re-create) existing rules, whether Rule Machine Legacy or Rule 5.0; they will continue to function. New rules can be created only in Rule 5.1.
Rules consist of up to three parts:
Each rule can have one or more trigger events specified. Events are generated by devices or by your hub itself. Examples of trigger events include "Motion sensor X is active" or "Time is 8:00 PM". Rules will listen for trigger events and run the "Actions to Run" when any trigger event happens (except in some cases when a required expression is used, as described below).
Rules can also be created without any trigger events. However, such rules' actions will run only when called by another rule or when run manually when viewing/editing the rule (with the Run Rule Actions button).
To specify a trigger event, open the Select Trigger Events page by selecting the Select Trigger Events box. Then, choose the "capability" that matches the kind of trigger event you want to add. For example, to trigger on "motion active," choose the "Motion" capability. To trigger on a switch (including a bulb or dimmer) turning on or off, choose "Switch." See the List of Trigger Event Capabilities section below for a complete list of capabilities and the attributes or events they correspond to.
The And stays? option, also called a "sticky trigger," is option available for many types of trigger events. (If this option does not appear, that particular kind of trigger event does not support this option, generally events that do not relate to state changes.) For example, a trigger of Front door opens and stays that way for 0:05:00 will trigger only if the front door opens and remains in an opened state for 5 minutes. If the door is closed before that time, the rule will not trigger.
NOTE: multiple triggers for the same attribute on a given device are not supported. For example, two triggers in the same rule for "level < 25" and "level > 75" on the same device will not work, as Rule Machine is not designed with a mechanism to track different possibilities for the same attribute on the same device separately. Different attributes — for example, "motion active" and "temperature > 60" on the same device, like a motion sensor – are not affected by this.
Enabling the Use required expression option allows you to define an expression (a single condition or any combination of conditions) that must evaluate to true in order for the rule to trigger. If the required expression evaluates to false at the moment when a trigger event happens, the rule will not actually trigger — and, in turn, the specified actions will not run.
One possible use for required expressions is to trigger only on specific state changes. For example, if you want a rule to trigger only on a specific mode change — e.g., Away mode to Home mode — then a required expression is an easy way to make that happen:
Trigger events: Mode becomes Home
Required expression: Mode is Away
Without the required expression, this rule would trigger any time mode becomes Home, regardless of the previous mode.
Another possible use for a required expression is to restrict the execution of actions under certain conditions (though this can generally also be done with conditional actions in "Actions to Run"; see below for more).
NOTE: Almost any condition can be used to create a required expression. However, local variables should not be used in conditions used to create required expressions (they do not generate events and thus the required expression will not be re-evaluated when it changes). Hub variables and Private Boolean will work without caveats.
Rule Machine offers two additional options, both disabled by default, for required expressions:
This is where you define what happens when the rule is is run. To add an action, first select the "+" button at the bottom of the (now empty) actions table to create a new action. Then, choose the appropriate category for the action under Select Action Type to add. Finally, choose the specific action under Select Which Action. Many actions will present additional options to configure the action after this point, but options will vary by action. Most actions run a command on a device. For example, Set Dimmers and Bulbs > Set dimmer can be used to set the level (brightness) on a dimmer or bulb. Rule Machine will ask you for a level (required) and, optionally, a transition time. Under the hood, this calls the "Set Level" command on the device, but you do not need to know this; Rule Machine handles running commands on devices as needed based on your selections here.
See the List of Actions section below for a complete list of where to find any particular action in the action menu structure.
Actions to run are essentially an ordered script. You can add as many actions as you need in whatever order you want. Note that some "special" action lines like
IF (expression) THEN and
Repeat have specific formats that must be followed; see below for more details on these.
On the Select Actions to Run page, the actions you've added to the rule are shown in a table format. Actions can easily be moved by using the up or down arrows in the cells next to the action. To insert an action before an existing action, select the "+" icon next to that action. To insert an action at the end of the list, select the "+" button at the bottom of the table (like you did to create your very first action).
To delete an action, select the trash can icon next to the action. To disable an action, check the box in the "X" (disable) column for that action. Disabled actions will be shown in an red, italic typeface. They will be skipped when the rule actions are run.
Actions can be cut/copied and pasted with in the same rule or between different rules.
To copy an action, select the checkbox to the left of the action in the table, then select the copy icon at the bottom left of the table (to the left of the "⬅ Copy Selected Actions To Clipboard" text). You may copy more than one action at a time — just check any number of boxes. To cut an action, select the scissors (cut) icon in the same row as that action. A cut action will be removed from the actions list and added to the clipboard; a copied action will remain in the list and be added to the clipboard.
To paste an action into the same rule, either select the paste icon at the bottom of the table to paste the copied action(s) at the end, or select the paste icon in the row next to any action to paste the copied action(s) before that action. Actions remain on the clipboard after cutting or copying and can be pasted again and again anywhere in the rule as desired. Use Clear Clipboard to remove all actions from the clipboard if needed.
To cut or copy actions from one rule to another:
TIP: To delete, enable/disable, cut, or copy multiple rule actions at the same time, the fastest method is to select the corresponding icon in the top/header row of the actions table (e.g., the trash, "X," cut, or copy icon in the top row). A drop-down list of actions will appear, with checkboxes next to each action. Check the desired actions, then click/tap anywhere outside the dropdown. Your changes will be saved immediately (e.g., actions will be deleted, copied, enabled/disabled, etc. as soon as you close the drop-down).
This may be faster for you than performing these tasks on individual actions.
Each rule has options for Logging:
All log entries will appear in "Logs," accessible from the sidebar. These options can be useful for troubleshooting.
Display current values: if enabled, the current value for any selected device attributes, variables, etc. will be displayed next to the device the list of trigger events and actions to run. These values will also be displayed with the actions in "Logs" if action logging is enabled.
Run Actions button: will run the Actions to Run section (effectively a way to manually trigger a rule)
Update Rule button: re-initializes rule like Done but without leaving the rule editor page
Remove button: removes this rule. Note that the Remove button inside a rule removes only that rule; the Remove Rule Machine button inside the "parent" Rule Machine app will remove Rule Machine and all rules.
Done button: re-initializes rule (updates trigger event subscriptions; cancels any timers/scheduled jobs), then returns to the Apps list page. (Note that changes inside the "Select Actions to Run" page are saved as they are made and do not require use of this button.)
Rule Machine rules also offer two features (at the top of the main rule page) to pause/resume or start/stop a rule:
Most Rule Machine actions run commands on devices. For example, Control Switches, Push Buttons > Turn switches on/off will send an "On" or "Off" command to the selected device(s), depending on the options chosen. Toggle switches will turn the switch (or dimmer, bulb, etc.) off it it is on or on of it is off. However, Rule Machine also contains various types of special actions, like delays and repeats.
Rule Machine offers two types of conditional actions:
The most powerful option is the "full" conditional action you can get by selecting IF (expression) THEN. Any action between this action and END-IF, which must be used to indicate the end of your block of conditional actions, will be executed only if the provided expression is true when the IF (expression) THEN line is reached. For example:
IF (Living Room Dimmer is on) THEN Dim: Living Room Dimmer: 50% END-IF
The "Dim..." action will be reached only if the Living Room Dimmer device is on when the
IF...THEN line is reached. If not, the rule will proceed to the next action after the
END-IF. You can put multiple lines of actions between the
END-IF. You can also use
ELSE-IF to create more complicated flows. These work similarly to conditional logic in most programming languages. Here is a more complicated example:
IF (Living Room Dimmer is on) THEN IF (Mode is Day) THEN Dim: Living Room Dimmer: 75% On: Kitchen Lights ELSE-IF (Mode is Night) THEN Dim: Living Room Dimmer: 25% Off: Kitchen Lights ELSE Dim: Living Room Dimmer: 50% END-IF
(Note that these are only examples of how to create rule actions and may appear somewhat contrived to demonstrate possible structure; we are not considering what might trigger this rule.)
A simple conditional action is an expression that can be "attached" to a single action, and that action will only run if the condition is true. Our first example above could have been re-written using the Simple Conditoinal Action option as:
IF (Living Room Dimmer is on) Dim: Living Room Dimmer: 50%
Unlike "full" conditional actions, a simple conditional action allows only a single action to run when the condition is true. It also does not provide a way to specify alternate flows if false.
The Select Actions to Run page includes a Create Conditions or Manage Conditions section at the bottom, with the note You can create and manage conditions to be used in Conditional Actions and Expressions below above:
This allows you to edit (or pre-build) conditions used in conditional actions, wait for expression actions, and other places where conditions can be used — without needing to edit or re-create that action.
NOTE: Creating or adding conditions under Create Conditions or Manage Conditions does not do anything on its own. These conditions are available to use (and perhaps are being used) in conditional actions, wait for expression actions, and other rule actions where expression can be used — but they do not do anything unless they are used somewhere.
A similar option appears in the Define Required Expression page, and the same applies (although these two "banks" of conditions are separate and only available in required expressions or actions, respectively).
NOT operators are available for use when building expressions.
XOR are evaluated from left to right with equal precedence.
NOT applies to the item immediately to the right. Parentheses,
), can be inserted using the editor to create sub-expressions. Sub-expressions are evaluated first (with the innermost sub-expression being evaluated first if nested sub-expressions are used). The meaning of these operators is the similar to the logical operators in most programming languages:
AND: returns true if both operands are true
OR: returns true if either operand is true (or if both are true)
XOR: returns true if exactly one operand is true
NOT: returns true if the operand is false, or false if the operand is true
If Display current values is enabled, the editor (and logs) will show the evaluation for individual conditions as
F in parentheses immediately following the condition and the final evaluation for the entire expression as
FALSE in parentheses after the expression.
As an example, an expression that reduces to
T AND F will evaluate to
T OR F will evaluate to
Rule Machine has two types of delays. A delay can be added as a special type of action under Delay, Wait, Exit or Comment > Delay Actions (or Delay Actions Per Mode to specify a different delay for each mode). This causes the actions to effectively pause at the delay, wait for the specified amount of time, then resume with the next action when the time is up.
Alternatively, with most actions, a delay option can be specified on the action itself. To do this, select an option from the Delay? drop-down when creating or editing the action. Choose hrs:min:sec to specify a specific amount of time, or choose variable to use a local or hub variable (must be of type number or decimal).
For any delay, the Cancelable? option may be selected. By default, a rule being re-triggered (or the rule actions running again for any reason) does not cancel previously scheduled delays. Choosing the Cancelable option allows the delay to be cancelled with the Cancel Delayed Actions action elsewhere in the same rule, but this must be done explicitly.
The Cancel Rule Timers actions will also cancel delayed actions (and can be called on the rule from any rule, not just the same rule), but it affects all rule timers, not just delays. It will also cancel delays with or without the Cancelable? option selected.
Care must be taken when using delays embedded inside conditionals. If the rule re-triggers while the delay is pending and the conditional action is reached again, you may see a "Multiple simultaneous rule execution error" in Logs (and the rule actions will not run as intended). Solutions include restricting execution of the rule while the delay is pending (e.g., with a required expression), cancelling the delay earlier in the rule, or using a "Wait for events: elapsed time" action instead if you want the timer to be cancelled on re-trigger of the rule.
Rule Machine offers two types of waits under Delay, Wait, Exit or Comment: the Wait for Events action and the Wait for Expression action.
Wait for Events allows you to specify one or more events. The rule will effectively pause at this point and wait for one of the specified event(s) to happen. When any of the specified events happen, the rule will proceed with the next action. (Note that this action looks specifically for events and does not evaluate any device states when it is reached; compare with "Wait for Expression," below.)
To add more than one event to wait for, select Add another Wait Event after adding the first (or any subsequent) event. When you are finished with everything, press Done with Wait Events to return to the previous page to add or edit other actions.
The Timeout? option allows you to specify an amount of time after which the rule will proceed with the next action in case none of the specified event(s) happen.
The And stays? option requires the condition resulting from the event to remain true for the specified amount of time before continuing. If the event happens but the resulting state does not remain true for the specified time, the rule will continue to wait.
Wait for Expression allows you to specify a condition or combination of conditions (i.e., an expression). If the expression is true when this wait is reached, the rule will immediately proceed with the next action (unless a duration is required; see below). If it is false, the rule will effectively pause at this point and wait for the expression to become true.
The Timeout? option allows you to specify an amount of time after which the rule will proceed with the next action in case the specified expression does not become true before that amount of time passes. The Use Duration? option allows you to specify a Duration, an amount of time for which the expression must remain true in order for rule to proceed to the next action. (Note that the duration begins at the time when the action is reached, so in the case of expressions that are already true, the time of any preceding events is not relevant.) If a duration is specified and the expression becomes (or is) true for some amount of time less than the duration and then becomes false again, the wait will start over.
Any type of "Wait" action is cancelled upon re-triggering of a rule. (The Cancel Rule Timers action will also cancel waits but is rarely necessary, and it affects all rule timers, as described elsewhere.) Note that this behavior differs from delays, which must be explicitly cancelled.
TIP: Using Wait for Events with Elapsed Time chosen as the capability is a particularly handy method of delaying actions. Unlike the Delay action (or the Delay? option on an action), waits are cancelled when the rule is re-triggered without any additional configuration required. This can save a couple clicks compared to a "delay" if this is the desired outcome. (Note: the Elapsed time option is not available if other events have already been selected. But in this case, it is effectively equivalent to setting a timeout on that wait.)
Exit Rule stops the execution of rule actions past the Exit Rule action itself. Note that it does not cancel any repeats, delays, waits, or other scheduled actions that may have already been set in place.
This action is generally most useful if used as part of a conditional action. For example:
IF (Mode is Night) THEN Exit Rule END-IF // remaining actions to run only in modes besides Night...
This action has no effect and is ignored during action execution; it simply allows you to write a "comment" at that location in your rule actions. This comment will display in the actions list wherever it is inserted. A typical use is to document for yourself why you are using certain actions at that point in the rule.
Rule Machine offers two types of repeats: Repeat Actions and Repeat While Expression. The block of actions to be repeated must be terminated with an END-REP or Until, thus enclosing the set of action(s) to be repeated. See below for some examples.
You must specify the time interval for the repetition, presented as the Repeat every... option when creating the repeat. Be careful not to make this interval too short, as you can consume your hub CPU resources by repeating too quickly.
Some method to stop the repetition is required. One option is the Repeat n times option, which will stop the repeat after n repetitions. Additionally, there is an optional Stoppable? option for a Repeat..., and, if selected, then a Stop Repeating Actions action elsewhere (often in the other half of an
ELSE inside the repeat) will stop this repetition when called from elsewhere in the rule. Additionally, Cancel Rule Timers from either the current rule or another rule will stop all repeats (and other rule timers), regardless of whether this option is selected.
NOTE: These examples demonstrate the general format of a repeat but not any options described above that you must (e.g., "repeat every...") or may (e.g., "repeat n times") choose when creating a repeat.
With Repeat Actions:
Repeat Actions some actions... END-REP
With Repeat While (Expression):
Repeat While (Expression) some actions... END-REP
The above is equivalent to a simple conditional on a Repeat Actions, which was the only option to create such a repeat in Rule 5.0 and prior (and still works):
IF (expression) Repeat Actions some actions... END-REP
The following can also be logically equivalent:
Repeat Actions (stoppable) some actions IF (expression) Stop Repeating Actions END-REP
Repeat Actions (stoppable) IF (expression) THEN Stop Repeating Actions ELSE some actions... END-IF END-REP
Repeat n times (like a "for loop"):
Repeat Actions n times some actions... END-REP
A repeat can also be terminated with a Repeat Until Expression (which displays as Until... in the actions list):
Repeat Actions some actions... Until (expression)
Repeat While (Expression) ... END-REP, this repeat will always happen at least once and will stop repeating if the expression is true when the end of the repeat is reached.
Rule Machine includes an action that can ping an IP address (under Send, Speak, or Log a Message, Send HTTP Request). This sets the built-in
text variable to the response results of three ping attempts and the built-in
value variable to the packet loss or 100 if no response. (See above on how to use built-in rule variables.) A possible example of its use:
Ping 126.96.36.199 Set myVariable to %value% IF (myVariable = '100') THEN Log: "No response from ping" END-IF
Most Rule Machine actions run specific commands on a device. For example, the Set Dimmers and Bulbs > Set Dimmer action runs the
Set Level command on a device (and passes the level and optional fade time as parameters).
If you want a Rule Machine action to run a command on a device that is not available via built-in Rule Machine actions, the Set Variable, Mode or File, Run Custom Action > Run Custom Action action can do that. Select this action, then choose the device (by either choosing a capability the desired device supports and then finding it in the list or using "Last Event Device," which will apply to the last device that matched a trigger event), and finally, choose the command to run. Optionally, specify one or more parameters. The Device Detail page for the device displays all commands at the top of the page and will show you what, if any, parameters are optional or required.
Rule Machine is arbitrarily powerful, and there will always be things it can do that you won't find an example of. For questions, the Hubitat Community is a great resource!
Rule Machine allows you to create local variables in each rule. These function similar to hub variables, except they are only available for use inside the specific rule where they are created. (Users of older Rule versions may recall global variables, which have effectively been replaced by hub variables and are also usable inside Rule Machine.)
Use the Create Local Variables or Create, Set, or Delete Local Variables option at the bottom of the main page of any rule to create or edit local variables for that rule. Data types, naming restrictions, and in-rule usage possibilities are generally similar to those for hub variables.
Rule Machine allows the use of local variables (and hub) variables in certain UI actions. For example, if you have a local variable named
MyVariable, you can can use the string
%MyVariable% in many string inputs to substitute the value of the variable. This works with any action under Send, Speak, or Log a Message, Send HTTP Request, including Send/Speak a Message, as well as when setting the value of String variables. Many actions will also offer the option to use a variable for a specific value, e.g., Set Dimmer has a Variable level? option that can be enabled to specify a variable to use for the level.
Rule Machine also has a few "built-in" variables local to each rule that refer to the last device event, usually the most recent trigger event (except as below, or if the trigger was not a device — a schedule, a hub/location event, manually running rule actions or running from another rule, etc., in which case these variables are not guaranteed to have a specific value). These can be referred to in string inputs using:
%device%: name of the device that generated the event (or
"timeout"after a "Wait..." action if a timeout is specified on a wait and the next action is reached because the timeout expires)
%value%: the value of the event (e.g., could be "off" for a switch)
descriptionTextproperty for the event (as provided by the driver, often in a format resembling "Living Room switch is off")
%date%:the date the event was generated
%time%: the time the event was generated
%now%: the current time (this value is always available and not related to any specific trigger or event)
Private Boolean is a built-in boolean variable available to each rule. A boolean variable is one that has two values, here
false. It functions similarly to a local boolean variable, except:
Private Boolean does not do anything on its own; it is used only if and how you use it in your rule(s).
Try enabling logging as described in the Rule Options section. Then, use "Logs" in the sidebar to see what, if anything, your rule did and when. (Note that you'll need to use the "Past Logs" option on this page unless you had "Current Logs" open at the time the log entry was generated.) Sometimes, you will find that your rule, in fact, did execute as expected, but a device may not have responded as intended. This will help you begin troubleshooting. The "Display current values" may also be helpful to have enabled if you have conditional actions or may otherwise care about the value of conditions/expressions, variables, and other states during execution. See How to Troubleshoot Apps or Devices for more troubleshooting tips.
Additionally, ensure your rule was created correctly. For example, without trigger events, rule actions will never execute unless run from another rule or app (or run manually from the rule page itself).
Triggers represent events, which are an instant in time — for example, motion becoming active, a switch turning on, or the time becoming 8:30 PM. An event cannot be true or false; it just something that happens. If you want to check a state rather than respond to a specific event, you can do so in the actions (using a conditional actions), or you can use a required expression to restrict triggering when a certain condition or combination of conditions (expression) is not true.
A rule will trigger any time an event matching any trigger event occurs.
The Hubitat Community is a great place to ask questions and share ideas with fellow users.
Below is a complete list of trigger event capabilities (on the "Select Trigger Events" page) and available actions (on the "Actions to Run") page, which can be useful to consult if you are not sure where to find something or what capability to choose for a specific event.
The following is a list of capabilities found on the "Select Trigger Events" page and the attribute or event that the trigger can listen for. Most of these capabilities can also be used to create conditions for expressions. Some (denoted "conditions only") are only available for use in conditions and not triggers, while some (denoted "triggers only") are only available for use in triggers.
|Capability||Description (attribute, event, etc.)|
|Acceleration:||active / inactive|
|Between two dates:||starting month/day or variable / ending on month/day or variable (conditions only)|
|Between two times:||starting at time of day or variable / ending at time of day or variable (conditions only)|
|Button:||pressed / held / doubleTapped / released (triggers only)|
|Carbon dioxide sensor:||value|
|Carbon monoxide sensor:||detected / clear / tested|
|Certain Time:||at a certain time, including sunrise / sunset with offset, with optional date (triggers only)|
|Cloud End Point:||trigger with HTTP GET on generated cloud URL (triggers only)|
|Contact:||open / closed|
|Custom attribute:||device capability|
|Days of Week:||on certain days of the week (day[s] as condition or day[s]/time as trigger)|
|Digital switch:||on / off (triggers only); switch events with
|Door:||open / closed|
|Fan speed:||supported fan speed values|
|Garage door:||open, closed, opening, closing, unknown|
|Gas detector:||clear / detected / tested|
|HSM alert:||intrusion, intrusion-delay, intrusion-home, intrusion-home-delay, intrusion-night, cancelRuleAlerts, intrusion-night-delay, smoke, water, rule, arming, armingHome, armingNight, cancel (triggers only)|
|HSM status:||armed away, armed home, armed night, delayed arming home, delayed arming night, delayed arming away, disarmed, all disarmed|
|Keypad codes:||code name|
|Last Event Device||select device and attribute (triggers only)|
|Local End Point:||trigger with HTTP GET on generated local URL (triggers only)|
|Location event:||mode / sunrise / sunset / sunriseTime / sunsetTime / systemStart / severeLoad / zigbeeOff / zigbeeOn / zwaveCrashed|
|Lock:||locked / unlocked|
|Lock codes:||code names|
|Mode:||any of your hub's modes|
|Motion:||active / inactive|
|Music player:||playing / paused / stopped|
|On a day:||specific date or variable|
|Music player:||playing, paused, stopped|
|Periodic schedule:||allows periodic schedules for minutes, hourly, daily, weekly, monthly or yearly (triggers only)|
|Physical dimmer level:||value (triggers only);
|Physical switch:||on / off (triggers only);
|Power source:||mains / battery|
|Presence:||present / not present or arrives / leaves|
|Private Boolean:||true / false|
|Security keypads:||armed away / armed home / armed night / disarmed / changed (triggers only)|
|Shock sensor:||clear / detected|
|Smoke detector:||clear, detected, tested|
|Sound:||detected / not detected|
|Switch:||on / off|
|Tamper alert:||detected / clear|
|Thermostat cool setpoint:||value|
|Thermostat fan mode:||value|
|Thermostat heat setpoint:||value|
|Thermostat mode:||heat / cool / auto / off / emergency heat|
|Thermostat state:||heating / cooling / fan only / idle / pending heat / pending cool|
|Time since event:||attribute (or any), plus minimum time since event|
|Time of day:||specific time / sunrise / sunset|
|Valve:||open / closed|
|Water sensor:||dry / wet|
|Window shade:||closed / open / opening / closing / partially open / unknown|
The following is a list of the actions available on the "Select Actions to Run" page. This can be helpful to consult if you are unsure where to find a specific action in the menus.
|Select Action Type to Add||Select Which Action|
|Conditional Actions||IF (expression) THEN
ELSE-IF (expression) THEN
Simple Conditional Action
|Control Switches, Push Buttons||Turn switches on/off
Set switches per mode
Choose switches per mode
Push button per mode
Choose button per mode
|Set Dimmers and Bulbs||Set dimmer
Set dimmer per mode
Fade dimmer over time
Stop dimmer fade
Start raising/lowering dimmer
Stop changing dimmer
Set color per mode
Set color temperature
Toggle color temperature
Set color temperature per mode
Change color temperature over time
Stop changing color temperature
|Adjust Shades/Blinds or Fans||Open/Close shades/blinds
Set shade/blind position
Set fan speed
Activate Scenes per Mode
|Control HSM, Garage Doors, Locks, or Valves||Arm/Disarm Hubitat® Safety Monitor
Open/Close garage door
|Control Thermostats or Thermostat Scheduler||Set thermostats
Set Thermostat Scheduler
|Send, Speak, or Log a Message, Send HTTP Request||Send/Speak a Message
Log a Message
Send HTTP Get
Send HTTP Post
Ping IP address
|Control Music Player, Volume, Sounds||Control Music Player
|Set Variable, Mode or File, Run Custom Action||Set Variable
Run Custom Action
Write to local file
Append to local file
Delete local file
|Set Private Boolean, Run/Cancel/Pause Rules||Set Private Booleans
Run Rule Actions
Cancel Rule Timers
Activate Room Lights for Mode/Period
Turn Off Room Lights
|Capture/Restore, Device Refresh or Polling||Capture Devices
Start/Stop Z-Wave Polling
|Repeat actions||Repeat Actions
Repeat While Expression
Repeat Until Expression
Stop Repeating Actions
|Delay, Wait, Exit or Comment||Delay Actions
Delay Actions Per Mode
Cancel Delayed Actions
Wait for Events
Wait for Expression