|
|
| Line 1: |
Line 1: |
| − | {{Top}}<h3><big>Introduction to Automation</big></h3>
| |
| | | | |
| − | <big>A home automation system is a collection of smart devices and a Hubitat Elevation hub. The objective of the system is to provide automatic control of various devices in the home based on events and conditions. This introduction explains the structure of the system and the way that it operates. Understanding these concepts is essential to being able to design your own home automation system.</big> | + | <big>'''We're moving!''' Please visit http://docs2.hubitat.com for the latest documentation.</big> |
| | | | |
| − | <h4><big>Events</big></h4> | + | <big> |
| − | | + | This document is available at: http://docs2.hubitat.com/en/apps/rule-machine |
| − | <big>An automation system is "event driven". The devices in your home automation system regularly generate events. An '''event''' is simply a small message that a device or the hub sends out.</big>
| + | </big> |
| − | | |
| − | *<big>'''Example''': When you turn on a smart switch, it sends out an event reporting that it was turned on. One way to think of the automation system is that there is a constant stream of '''events'''. The role of the hub is to make sense out of this stream of events and to make actions happen in the system.</big>
| |
| − | | |
| − | ====<big>Automations</big>====
| |
| − | <big>An "automation" is a very small computer program which responds to events, and results in something happening.</big>
| |
| − | | |
| − | *<big>'''Example''': An automation could respond to the event of a door contact opening by turning on a porch light. These '''automations''' (e.g. Rules), make up the brains of the home automation system, delivering the "Smart" of a Smart Home.</big>
| |
| − | | |
| − | <big>Of all of the events occurring in the system, each '''automation''' is only interested in a few specific events. To avoid having to process every single event, each automation "subscribes" to the ones it is interested in. In our previous example of the porch light, an automation subscribes to the events from the door contact sensor, and ignores all other events in the system. Its single job is to turn on a light when that contact opens. Each automation in a system has subscriptions to the events it is concerned with. The job of the hub is to send each automation, only the events that it for which it has subscribed.</big>
| |
| − | | |
| − | '''<big>Event types</big>'''
| |
| − | | |
| − | <big>There are four basic event types:</big>
| |
| − | | |
| − | #<big>Device events</big>
| |
| − | #*<big>Devices events are generated by the smart devices in the system, like the door contact sensor reporting 'open'.</big>
| |
| − | #<big>Time events</big>
| |
| − | #*<big>Time events are generated by a scheduler in the hub for things like sunrise, 5:00 PM, etc.</big>
| |
| − | #<big>Hub events</big>
| |
| − | #*<big>Hub events are special events that the hub generates</big>
| |
| − | #**<big>'''Example''': The hub generates an event when it starts up.</big>
| |
| − | #<big>Network events</big>
| |
| − | #*<big>Network events are messages that come to the hub from the LAN or internet. Some devices use the LAN to send events, some use Z-Wave or Zigbee radio signals.</big>
| |
| − | | |
| − | <big>For every device event or network event to be processed so that an automation can respond to it, there must be a "driver" in the system.</big>
| |
| − | | |
| − | *<big>'''Example''': A driver would receive a message from the Zigbee radio network sent by the door contact, and convert it into an event. Each smart device in the system has a corresponding driver installed in the hub. The hub serves as the traffic cop, forwarding device '''events''' to '''automations'''.</big>
| |
| − | | |
| − | ====<big>Components of an Automation</big>====
| |
| − | <big>As explained above, an '''automation''' is a small app that runs on the hub. Its purpose is to respond to events by causing actions.</big>
| |
| − | | |
| − | <big>Every automation has two elements:</big>
| |
| − | | |
| − | #<big>The events that provoke it to act.</big>
| |
| − | #<big>The actions it performs as a result.</big>
| |
| − | | |
| − | <big>Some automations are very simple. The one described where opening a door causes a light to turn on is very simple, but you may want or need it to be more sophisticated. Suppose you only want the porch light to turn on when the door opens at night, but not during the day. To accomplish this, the automation will need more than just the events and the actions, so it will need to evaluate '''Conditions'''. Based on this evaluation of conditions, it may or may not perform an action, or it could perform different actions depending on the conditions that are evaluated. Expanding on the porch light automation example, you could have the '''Rule''' also test what the time is, and the result from that additional evaluation of the '''Time event''' would determine if the light should turn on when the contact sensor is opened.</big>
| |
| − | | |
| − | <big>You should now have a complete picture of what an automation is all about, with the understanding that all automations have this general form.</big>
| |
| − | | |
| − | *<big>An automation responds to '''Events'''</big>
| |
| − | *<big>Evaluates '''Conditions'''</big>
| |
| − | *<big>Performs '''Actions''' based on the '''Conditions'''.</big>
| |
| − | <h3><big>Rule Machine</big></h3>
| |
| − | | |
| − | <big>Rule-5.0 is a built-in app in Hubitat Elevation that can be used to create automations. Each rule created with Rule Machine has the described form.</big>
| |
| − | | |
| − | *'''<big>Trigger Events</big>'''
| |
| − | *<big>'''Actions -''' Actions may have '''Conditions''' to be evaluated as a step in determining what the automation does.</big>
| |
| − | <h3><big>Rule Machine API</big></h3>
| |
| − | | |
| − | <big>It is possible for other apps to use '''Rules''', '''Triggers''', and '''Actions''' defined in Rule Machine. This is very similar, and uses the same mechanism, as actions in Rule Machine that affect other rules. It is also possible to use Rules, Triggers, and Actions from an HTTP request to an endpoint.</big>
| |
| − | | |
| − | <h3><big>Using Rule Machine from within other apps</big></h3>
| |
| − | | |
| − | <big>First, import the RM helper class into your app.</big>
| |
| − | | |
| − | <code><big>'import hubitat.helper.RMUtils'</big></code>
| |
| − | | |
| − | ====<big>The List of Rules</big>====
| |
| − | <big>Rule Machine maintains a list of available Rules, Triggers, Triggered Rules, and Actions. That list can be obtained with this method call.</big>
| |
| − | | |
| − | <big>def rules = RMUtils.getRuleList()</big>
| |
| − | | |
| − | <big>In this example, the resulting list of the variable '''rules''', can be used as an input to an "enum" as the options.</big>
| |
| − | | |
| − | ====<big>Supported Actions</big>====
| |
| − | <big>It is possible to set the '''Private Boolean''', evaluate a rule, run the rule actions, or stop running rule actions (either delayed or repeating). This is accomplished by sending an action request to Rule Machine, with each take the following form.</big>
| |
| − | | |
| − | <big>def RMUtils.sendAction(rules, action, appLabel)</big>
| |
| − | | |
| − | <pre> Set Private Boolean True:
| |
| − | action "setRuleBooleanTrue"
| |
| − |
| |
| − | Set Private Boolean False:
| |
| − | action "setRuleBooleanFalse"
| |
| − |
| |
| − | Evaluate Rule:
| |
| − | action "runRule"
| |
| − |
| |
| − | Run Rule Actions:
| |
| − | action "runRuleAct"
| |
| − |
| |
| − | Stop Rule Actions:
| |
| − | action "stopRuleAct"
| |
| − |
| |
| − | Pause Rule:
| |
| − | action "pauseRule"
| |
| − |
| |
| − | Resume Rule:
| |
| − | action "resumeRule"
| |
| − | </pre>
| |
| − | <big>In each case above, a list of '''Rules''' selected by input is sent. The rule options come from the variable to which they were input as described above, in the options section of the input.</big>
| |
| − | | |
| − | <big>The '''appLabel''' parameter is passed and will appear in the log entry that the rule makes when it performs the action commanded. Typically, simply pass `app.label`, for the name of the app that is causing the action. This has no function, other than logging.</big>
| |
| − | | |
| − | <big>'''Example''':</big>
| |
| − | | |
| − | def rules = RMUtils.getRuleList()
| |
| − | input "theseRules", "enum", title: "Select which rules to stop", options: rules
| |
| − | RMUtils.sendAction(theseRules, "stopRuleAct", app.label)
| |
| − | | |
| − | <h3><big>Using Rule Machine from HTTP requests</big></h3>
| |
| − | | |
| − | <big>It is also possible to cause Rule Machine to perform these same actions from an HTTP request. To accomplish this, you would create a '''Trigger''' with either a Local End Point or Cloud End Point. The endpoint URL given by Rule Machine has the following form.</big>
| |
| − | | |
| − | <big>`http://192.168.0.36/apps/api/10249/trigger?access_token=ecd95469-bbcd-4889-a694-9b05ef80f4db`</big>
| |
| − | | |
| − | <big>To run rule actions the above URL must be modified to include the list of rules and the action. The modification takes the following form.</big>
| |
| − | | |
| − | <code><big>`/action=rule1&rule2&rule3`</big></code>
| |
| − | | |
| − | <big>Where action is the action from the list above and <code>`rule1&rule2&rule3`</code> are the '''appIds''' of the rules to run, separated by ampersands.</big>
| |
| − | | |
| − | <big>This parameter is inserted in the endpoint URL just before the '''?''' that precedes the access_token as follows.</big>
| |
| − | | |
| − | <big>`http://192.168.0.36/apps/api/10249/trigger/stopRuleAct=943&956&10217?access_token=ecd95469-bbcd-4889-a694-9b05ef80f4db`</big>
| |
| − | | |
| − | <big>This example would do the same thing as the code example above, where '''943&956&10217''' are the appIds that were selected by consequence of the input for '''theseRules''', and '''stopRuleAct''' is the action to perform.</big>
| |
| − | | |
| − | <big>The '''appIds''' are the values selected by the input described above. For example, <code>`theseRules`</code>. The appIds can also be found for a rule by opening the rule and observing its appId in its URL as follows.</big>
| |
| − | | |
| − | <big>`http://192.168.0.36/installedapp/configure/10249/mainPage`</big>
| |
| − | | |
| − | <big>The '''appId''' for that rule would be '''10249.'''</big>
| |
| − | | |
| − | ====<big>Get Rule List</big>====
| |
| − | <big>To get the list of rules as returned from <code>`getRuleList()`</code> , use the following insert for the URL.</big>
| |
| − | | |
| − | <code><big>`/getRuleList`</big></code>
| |
| − | | |
| − | <big>Here's an example of how you would use a full URL.</big>
| |
| − | | |
| − | <big>`http://192.168.0.36/apps/api/10249/trigger/getRuleList?access_token=ecd95469-bbcd-4889-a694-9b05ef80f4db`</big>
| |
| − | | |
| − | <big>This returns a JSON object with appId and rule name pairs. The other requests return a JSON object with a human readable description of what was done.</big>
| |
| − | | |
| − | <h3><big>Dedication</big></h3>
| |
| − | | |
| − | <p><big>Rule Machine is dedicated to [[wikipedia:Alan_Turing|Alan Turing]]. He gave us the concept of an abstract machine that could compute, and from that we built small implementations of his vision. Today, we all use them every day of our lives.</big></p>
| |
| − | __FORCETOC__
| |
