jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2018-01-25 17:33:45 UTC

Browse source
This commit is contained in:
Travis CI 2018-01-25 17:33:45 +00:00
parent 2a429df2b2
commit 94552b64db
144 changed files with 304 additions and 301 deletions
Download patch file Download diff file Expand all files Collapse all files

6
components/timer/index.html
View file

@ -75,7 +75,7 @@
</header>
<hr class="divider">
<p>The <code class="highlighter-rouge">timer</code> component aims to simplify automations based on (dynamic) durations.</p>
<p>When a timer finishes or gets cancelled the corresponding events are fired. This allows you to differentiate if a timer has switched from <code class="highlighter-rouge">active</code> to <code class="highlighter-rouge">idle</code> because the given duration has elapsed or it has been cancelled. To control timers in your automations you can use the services mentioned below. When calling the <code class="highlighter-rouge">start</code> service on a timer that is already running, it resets the duration it will need to finish and restart the timer without triggering any events. This for example makes it easy to create timed lights that get triggered by motion.</p>
<p>When a timer finishes or gets canceled the corresponding events are fired. This allows you to differentiate if a timer has switched from <code class="highlighter-rouge">active</code> to <code class="highlighter-rouge">idle</code> because the given duration has elapsed or it has been canceled. To control timers in your automations you can use the services mentioned below. When calling the <code class="highlighter-rouge">start</code> service on a timer that is already running, it resets the duration it will need to finish and restart the timer without triggering any events. This for example makes it easy to create timed lights that get triggered by motion.</p>
<p class="note warning">
With the current implementation timers don’t persist over restarts. After a restart they will be idle again, together with their initial configuration.
</p>
@ -108,7 +108,7 @@ With the current implementation timers don’t persist over restarts. After a re
<tbody>
<tr>
<td>timer.cancelled</td>
<td>Fired when a timer has been cancelled</td>
<td>Fired when a timer has been canceled</td>
</tr>
<tr>
<td>timer.finished</td>
@ -160,7 +160,7 @@ If no <code class="highlighter-rouge">entity_id</code> is given all active timer
</tbody>
</table>
<h4><a class="title-link" name="service-timercancel" href="#service-timercancel"></a> Service <code class="highlighter-rouge">timer.cancel</code></h4>
<p>Cancel an active timer. This resets the duration to the last known initial value without firing the <code class="highlighter-rouge">timer.finished</code> event. If no <code class="highlighter-rouge">entity_id</code> is given all active timers will be cancelled.</p>
<p>Cancel an active timer. This resets the duration to the last known initial value without firing the <code class="highlighter-rouge">timer.finished</code> event. If no <code class="highlighter-rouge">entity_id</code> is given all active timers will be canceled.</p>
<table>
<thead>
<tr>