jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-26 18:57:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update timer.markdown (#3943)

Browse Source 
Quick spelling correction.
This commit is contained in:
NeLLyMerC 2017-11-10 03:58:44 -05:00 committed by Fabian Affolter
parent 14eccf7f32
commit cf33748e16
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_components/timer.markdown
View File

@ -14,7 +14,7 @@ ha_release: 0.57
The `timer` component aims to simplify automations based on (dynamic) durations. The `timer` component aims to simplify automations based on (dynamic) durations.
When a timer finishes or gets cancelled the corresponding events are fired. This allows you to diffferentiate if a timer has switched from `active` to `idle` 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 `start` 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. When a timer finishes or gets cancelled the corresponding events are fired. This allows you to differentiate if a timer has switched from `active` to `idle` 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 `start` 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 class='note warning'> <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. With the current implementation timers don't persist over restarts. After a restart they will be idle again, together with their initial configuration.