Site updated at 2016-10-14 20:56:39 UTC
This commit is contained in:
parent
103bbd44c5
commit
6e3982d5ff
23 changed files with 36 additions and 43 deletions
|
@ -91,13 +91,6 @@
|
|||
|
||||
<p>Conditions are an optional part of an automation rule and be used to prevent an action from happening when triggered. Conditions look very similar to triggers but are very different. A trigger will look at events happening in the system while a condition only looks at how the system looks right now. A trigger can observe that a switch is being turned on. A condition can only see if a switch is currently on or off.</p>
|
||||
|
||||
<p>If your triggers and conditions are exactly the same, you can use a shortcut to specify conditions. In this case, triggers that are not valid conditions will be ignored.</p>
|
||||
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">automation</span><span class="pi">:</span>
|
||||
<span class="s">condition</span><span class="pi">:</span> <span class="s">use_trigger_values</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<p>The available conditions for an automation are the same as for the script syntax. So see that page for a <a href="/getting-started/scripts-conditions/">full list of available conditions</a>.</p>
|
||||
|
||||
<p>Example of using condition:</p>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue