Now you need to check the state of the lights after the delay, which requires you to know the original brightness. The grace period as you described works fine, but if you want to stop your lights for going out completely as soon as you notice the 50% brightness “warning”, things get a lot more complicated. Time is an integral part of our lives, so it makes sense to have good time-building blocks. I also believe that having better timers would greatly reduce complexity in some automations. I agree that we need easy to use building blocks. Remaining and elapsed would support the same values as for in the state platform, so a time-string, a number of seconds or a hours/minutes/seconds object. This would trigger when the timer has been running for 10 minutes. This would trigger when the timer has 10 minutes remaining: trigger: State: started | paused | finished | cancelled | restartedĪnd this would add the new functionality: Make the timer into a proper trigger platform in stead of having to use the event platform: trigger: Add a timer condition, like the numeric_state conditions.Ĭondition passes if there is atleast 5 minutes remaining: condition:Ĭondition passes if there is atmost 5 minutes remaining: condition:Ītleast and atmost would support the same values as for in the state platform, so a time-string, a number of seconds or a hours/minutes/seconds object.įor consistency we may want to shadow the state condition to the timer condition too: condition: Would set the timer to atleast or at most the specified duration. Alternatively only add the timer.add service and have it support negative values. Would add or subtract 5 minutes to/from the timer. Press a button: light goes on for 5 minutes, wait a minute (4 minutes to go), press the button again, light stays on for 9 minutes.Įdit: Proposal Add new services for timers: timer.add / timer.subtract action: Open a door while the 5 minute timer is running: light shouldn’t go out after just 1 minute. Open a door: light turns on for 1 minute, press a button light turns on for 5 minutes. Ensure there are atleast/atmost X minutes remaining on the timer. User presses a button: thing happens, unless the timer is almost up, then we want another thing to happen.
Have a condition that checks whether there are atleast/atmost X minutes to go for a timer.
Now I have to start a timer which runs for 60 minutes, and another that runs for 65 and another that runs for 70 minutes or have a timer for 60 minutes and two for 5 minutes, either way you need 3 timers for a single timed event. Turn 3 lights off after an hour, but not all at the same time, so we’re not in the dark suddenly. Trigger an automation X minutes before a timer ends. Ensure there are atleast/atmost X minutes remaining on the timer.Have a condition that checks whether there are atleast/atmost X minutes to go for a timer.Trigger an automation X minutes before a timer ends.
0 kommentar(er)
