Rule 5.0 is a further enhancement of the Rule 4.x series. Rule 4.0 was the culmination of a journey in the transformation of the Rule Machine app. All at once, it simplified and added power, resulting in a fully generalized automation engine. The prior top-level organization of Rule Machine–familiar to Rule 3.0 users—was been replaced with an optimized interface. The changes described below, explain how prior rules were created versus how it is accomplished with Rule 4.x and Rule 5.0. The former structure of Rules, Triggers, Triggered Rules, Actions and Schedules are now replaced with the definition of what causes a rule to run, and the resulting action. Conditional logic capabilities are provided, allowing the most subtle or complex automations to be created. You simply define what causes the a rule to run, and then that you want it to do.
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" existing rules, which will continue to function and be edit-able. The change in parent app was necessary to remove the global variable feature, a feature of now-Legacy Rule Machine, and replace them with hub variables, a feature now available to all apps and accessible from Settings.
In any Rule, the rule itself can be thought of as an overarching IF-THEN-ELSE, where if the condition was True for the IF part or the rule, then Actions for True are run, and if they are False, then Actions for False are run. In Rule-5.0, this same logic can now simply be done with the Conditional Actions of IF-THEN and ELSE in the Actions section of a rule. As described in the next section, IF-THEN now has the same full logical expression capability previously available, with the addition of AND, OR, XOR, NOT logical operators, and nested parenthetical sub-expressions.
All "Rules" in Rule-5.0 are in effect Triggered Rules. They each have a Trigger Event, and then Conditional Actions. Instead of a rule with Actions for True and Actions for False, they simply use conditional logic in the actions to create an equivalent IF-THEN-ELSE structure.
Each rule can have one or more Trigger Events that when triggered, cause the rule's actions to run.
Events are created by the devices or conditions in your system. Each device creates events appropriate to the type of device. A Trigger Event listens for specific events and when a trigger receives a selected event, it causes the defined Actions to run.
Rule Machine allows the following events in a Hubitat Elevation system to be acted upon. Each event results in a single test and the supported events and states that can be tested are listed below. For each event that refers to a device, one or more devices can be selected, and then the device state required for the Condition to be met can be selected. When multiple devices are selected, the Condition/Event may apply for ANY (default) or ALL of the devices.
Acceleration: active / inactive Between two dates: starting month on this date / ending month on this date Battery: value Button: pressed / held / doubleTapped / released Certain Time: at a certain time, including sunrise / sunset with offset Cloud End Point: hitting URL fires Contact: open / closed Custom attribute: device capability Days of Week: on certain days of the week Dimmer level: value Door: open, closed, opening, closing, unknown Energy meter: value Garage door: open, closed, opening, closing, unknown HSM alert: intrusion, intrusion-delay, intrusion-home, intrusion-home-delay, intrusion-night, cancelRuleAlerts, intrusion-night-delay, smoke, water, rule, arming, armingHome, armingNight, cancel HSM status: armed away, armed home, armed night, delayed arming home, delayed arming night, delayed arming away, disarmed, all disarmed Humidity: value Illuminance: value Last Event Device select device and attribute Local End Point: hitting URL fires Lock: locked / unlocked Mode: any of your hub's modes Motion: active / inactive Music player: playing, paused, stopped Periodic: allows periodic schedules for minutes, hourly, daily, weekly, monthly or yearly Physical dimmer level: value Physical switch: on / off Power meter: value Power source: mains / battery Presence: present / not present or arrives / leaves Private Boolean: true / false Rule paused: rule Smoke detector: clear, detected, tested Switch: on / off Temperature: value 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 of day: specific time / sunrise / sunset Variable: value Water sensor: dry / wet
Note: value means compare current value to a number, to another device with an offset, or to a variable with an offset, or changed, increased, decreased
Actions are the portion of a rule that defines what the rule does when it is triggered to run.
As you define actions, you are creating a script of actions to perform when the rule runs. You may use as many actions as you want for each Action type and they can be run in whatever order you want. There is no predefined order of execution for Rule Machine actions, so you may arrange the order of actions any way you want. You can insert a new action anywhere in the list of actions, or at the end of the list.
The Rule-5.0 user interface provides the ability to Edit and Delete any action you have defined, giving you complete control over your list of actions. You may also Cut and then Paste actions if you need them to occur in a different order.
All actions can be delayed, effectively pausing the action execution for a specified amount of time. Actions may also be delayed for a period of time that is dependent on the current Mode by using Delay Actions Per Mode.
Delay per Action
Each action you define can have an optional delay. These delays can be defined with hours, minutes, and seconds. Seconds can have decimal fractions, allowing millisecond resolution. In a rule, delays can have the option to be cancelled in the event of a change of rule truth. It is important to realize that the delay assigned to an individual action affects only that action, and not subsequent actions. Any subsequent action is executed immediately after the delayed action starts its delay timer, and does not wait for that delay timer to run. When the delay timer expires, the delayed action is executed (unless the delay was cancelled). Delay all Actions
It is also possible to delay all actions (also with optional cancel). The script of actions runs sequentially when the rule runs, with each action happening in order. Actions with delays start their timer, which can vary for each action, and the next action in order runs. By using Delay Actions, the entire script can be paused by a delay.
Delay Actions per Mode
Delay Actions can also be specified on a per mode basis, so that the time the script is paused, varies according to the current mode.
In Rule Machine, IF-THEN-ELSE-ENDIF conditional blocks can be nested. The user interface utilizes textual indentation to help guide you in keeping track of which IF-THEN-ELSE-ENDIF block you are currently adding actions to. The user is responsible for completing each level of nested IF-THEN blocks.
The condition of an IF-THEN or ELSE-IF Action can be a full logical expression built-up from individual conditions, and the logical operators AND, OR, XOR, and NOT. Parenthesized sub-expressions are also possible. This is the same user interface of the former rule portion found in Rule or Triggered Rule from Rule-3.0. An individual Condition can be created on the fly while defining a logical expression. Every such Condition is kept in the list of available Conditions. This list of available conditions is present in the Define Actions page. The user interface then allows Creating, Editing and Deleting conditions. If a condition is edited, those changes will be reflected where it is used in an IF-THEN or ELSE-IF conditional action.
This combination of nested IF-THEN blocks and full logical expression for each IF-THEN and ELSE-IF, allows creativity for rules in Rule-5.0 that is limited only by your imagination. To help you with complex logic structures, new actions are available.
When Event Triggers are defined, corresponding conditions are created for most types. Some conditions, like Button, Certain Time, etc, do not have a state and so have no corresponding condition. These created conditions are available in the Define Actions page for use in Conditional Actions, are available for use in other Actions, and can be edited.
You can introduce conditional execution of actions using the following method.
IF (condition) THEN
ELSE-IF (condition) THEN
IF-THEN and ELSE-IF both accept a logical expression as described above and IF-THEN-ELSE may also be nested. If the expression on the IF portion is True, then those actions following IF and before any ELSE-IF or ELSE statements will be carried out. If the expression is False, then those actions are skipped, and the ELSE portion or ELSE-IF are carried out. In the case of ELSE-IF, its expression will be tested, and the following Actions that follow it will either run or will not run, depending on the result of the evaluation. There can be as many ELSE-IF sections as you need, and the ELSE-IF and ELSE portions are both are optional. END-IF is also optional, and if omitted means all remaining actions are part of the preceding IF-THEN, ELSE-IF or ELSE. However, for good rule structure, just a sentence should have a period at the end, it is strongly recommended that you use END-IF to complete an IF-THEN-ELSE as a regular practice.
Portions of, or all of the script of an Action can be repeated periodically, but you must specify the time interval for the repetition. Be careful not to make this interval too short, as you can consume your hub CPU resources by repeating too quickly. You can select any number of iterations if desired, but some method to stop the repetition is required. When a Repeat Actions is introduced to the script, any action before END-REP will be repeated. Only the Actions between Repeat Actions and END-REP will be repeated. Actions following END-REP will run only once the repetition has stopped. There is an optional Stop for a Repeat Action choice and if selected, then Stop Repeating Actions will stop this repetition. Using Cancel Rule Timers from either the current rule or another rule, will stop all Repeat Actions, irrespective of which Stop selection is used.
A Repeat Actions, like any action, can have a condition specified. If the condition is False, the Repeat Actions block will not be executed. If the condition becomes False during repetition, the repetition will be stopped (with the exception of when Repeat N Times is selected). This provides three features well known to computer programmers.
While loop - repeat while the condition is True:
IF (condition) Repeat Actions
For loop (repeat n times):
Repeat Actions n times
Conditional For loop (repeat n times if condition is True):
IF (condition) Repeat Actions n times
Repeat Actions with Stop selected
IF (condition) Stop Repeating Actions
Repeat Actions cannot be nested. END-REP is optional, and if omitted, all actions after Repeat Actions will be repeated.
Wait for Events and Wait for Conditions may be using with Conditional Actions and in a Simple Conditional Action. Additionally, Wait for Conditions allows for full logical expression with operators AND, OR, or XOR. If the conditions are true, no wait occurs, otherwise the rule execution is paused until the conditions are met. Both Wait for Events and Wait for Conditions have the option to select a Timeout period. Multiple events can be defined to cause the Wait to end. In effect, this introduces another trigger-like capability into the Actions. There is also an event type specifically for Wait for Events named Elapsed Time. When the Elapsed Time expires, the wait will be over, irrespective of other events it may be waiting for. Pending Wait for Events and Wait for Conditions will be cancelled each time a rule is triggered, and can be also cancelled by another rule with Stop Rule Actions, or by a Cancel Wait action (which presumably would have been part of a Delayed Action).
Wait for Conditions also has an option to use Duration instead of a Timeout period, allowing you to specify an amount of time that the Conditions must remain continuously true for the Wait to conclude. This is useful for many automations that require the passage of some time in a certain state, such as a door that has been left open for more than 5 minutes. The rule would Wait for Conditions that the door is open for a duration of 5 minutes, Following the Wait period, you could have a notification action. If the door was subsequently closed before the 5 minute duration period, the Wait wouldn't conclude. If the door opened again, the pending Wait would then be canceled, and a new one begins. Only if the door is opened and remains open for 5 minutes would the Wait conclude, and the notification be sent.
A Custom Action allows you to select a device, and send any of the commands that device supports along with parameters it may take. Custom Actions are created within your actions and they are specific to the rule where created.
Hub Variables are a setting for creating very efficient variables directly in the hub for use in other apps, not just in Rule Machine, as is the case with Local Variables. There are five types of Hub Variables available - Number, Decimal, String, Boolean and DateTime.
Each Hub Variable can have an associated Connector. A Connector is a virtual device linked to the Hub Variable. When the Hub Variable value changes, so does the Connector value, and vice versa. When the Connector device is set to a different value, the corresponding Hub Variable is set to that value. Connectors can be used in any app. The aforementioned DateTime, allows both Date and Time to be set. The use of Date has very limited applicability for now, specifically in the Certain Time trigger for Rule 5.0, where triggering on a specific date is possible; by using a DateTime connector, that can be a variable Date and Time.
Managing Hub Variables can be found in Settings, allowing for the creation of a Hub Variable, changing its value, creating a Connector for it, and removing it. If a Hub Variable is in use by an app, the name of the Hub Variable is shown in Orange, and selecting that shows the apps it is in use by. When a Connector is created, the type of Connector is shown in Blue, and selecting that connector opens a new tab with the Connector device settings page. The value of the variable can be changed by selecting the Purple text in the Value column. When a Connector exists, the variable value is shown with the selected attribute for the Connector.
Example: A Boolean variable for which a Switch Connector is created, will show On or Off as the possible values, rather than True or False.
When you first create a new rule, you are creating a child app of the parent Rule Machine app, and therefor you must select Done on the main page to install the Rule-5.0 rule. If you re-open the rule, its actions can be run by hitting Run Actions button. If you change the Trigger Events in any way, you must either select Done or the Update Rule button.
You can select which types of logging you want to see in Logs. This is a very good way to determine exactly what a rule is doing.
Conditional Actions IF (conditions) THEN ELSE-IF (conditions) THEN ELSE END-IF Simple Conditional Action Control Switches, Push Buttons Turn switches on Turn switches off Toggle switches Flash switches Set switches per mode Push a button Push a button per mode Set Dimmers and Bulbs Set dimmer level Toggle dimmer level Adjust dimmer level Set dimmer level per mode Fade dimmer level over time Stop dimmer fade Start raising dimmer level Start lowering dimmer level Stop changing dimmer level Set color and level Toggle color and level Set color and level per mode Set color temperature and level Toggle color temperature and level Set color temperature and level per mode Change color temperature over time Stop changing color temperature Activate Scenes, Adjust Shades or Fans Activate scenes Activate scenes per mode Open shades Close shades Set shade position Set fan speed Cycle fans Control HSM, Garage Doors, Locks or Valves Arm/Disarm Hubitat® Safety Monitor Open garage door Close garage door Lock locks Unlock locks Open valves Close valves Control Thermostats or Thermostat Scheduler Set thermostats Set Thermostat Scheduler Send, Speak, or Log a Message, Send HTTP Request Send or Speak a Message Log a Message Send HTTP Get Send HTTP Post Control Music Player, Volume, Sounds Control Music Player Set Volume Mute Unmute Sound Tone Sound Chime Control Siren Set Mode or Variables, Run Custom Action Set Mode Run Custom Action Write to local file Append to local file Delete local file Set Private Boolean, Run/Cancel/Pause Rules Set Private Booleans True Set Private Booleans False Run Rule Actions Cancel Rule Timers Pause Rules Resume Rules Capture/Restore, Device Refresh or Polling Capture Devices Restore Devices Refresh devices Poll devices Start Z-Wave poll on switches Stop Z-Wave poll on switches Start Z-Wave poll on dimmers Stop Z-Wave poll on dimmers Delay or Repeat Actions, Wait Delay Actions Delay Actions Per Mode Cancel Delayed Actions Repeat Actions END-REP Stop Repeating Actions Wait for Events Wait for Condition Cancel Wait Exit Rule Comment
Select this option to allow export of your Rule Machine rules for import to another hub, or to clone an existing rule as a base from which to start a new rule.
You may choose to Restore a rule instead of using the Import option. This is most appropriate for instances where you want to bring a Rule Machine rule into your hub database, but you do not want to change the name or the devices used in the rule. If you instead choose to Import, the process will pause to allow the rule to be renamed, and the devices used in the rule to be substituted with other devices installed on your hub before completing the import process.