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

Site updated at 2017-11-10 09:32:54 UTC

Browse source
This commit is contained in:
Travis CI 2017-11-10 09:32:54 +00:00
parent b4ab42e7e7
commit 273c0efb01
28 changed files with 74 additions and 69 deletions
Download patch file Download diff file Expand all files Collapse all files

2
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 diffferentiate 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 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 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>