Site updated at 2017-05-07 12:40:16 UTC
This commit is contained in:
parent
533fc934e2
commit
17f4e71222
27 changed files with 185 additions and 39 deletions
|
@ -112,6 +112,15 @@ The difference between a condition and a trigger can be confusing as they are ve
|
|||
</table>
|
||||
<p>State changes can be used as the source of triggers and the current state can be used in conditions.</p>
|
||||
<p>Actions are all about calling services. To explore the available services open the <img src="/images/screenshots/developer-tool-services-icon.png" class="no-shadow" height="38" /> Services developer tool. Services allow to change anything. For example turn on a light, run a script or enable a scene. Each service has a domain and a name. For example the service <code class="highlighter-rouge">light.turn_on</code> is capable of turning on any light in your system. Services can be passed parameters to for example tell which device to turn on or what color to use.</p>
|
||||
<p class="note">
|
||||
As of version 0.42 you have to set an initial state in your automations in order for Home Assistant to restore them upon restart.
|
||||
<code class="highlighter-rouge">text
|
||||
- alias: Automation Name
|
||||
initial_state: True
|
||||
trigger:
|
||||
...
|
||||
</code>
|
||||
</p>
|
||||
</article>
|
||||
</div>
|
||||
<aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue