⏱ Timer Relay - Run ON Timer

[Blacky]

GitHub Link Click Here

If you like my blueprints, and would like to show your support or just say thank you? Click Here

Like this blueprint? Consider hitting the button below

Version: 1.3

The most common automation used for a Timer Relay (also known as a “Run on Timer”)

The Automation Process:

• When the trigger is activated, it turns the selected entity (lights, fan, motor etc.) ON and then OFF automatically in a pre-set time period. You can have as many triggers and entities as you like.
• The entity will stay ON if the trigger has been activated again before the time delay turns the entity OFF. It will then reset the time delay after the last trigger event.
• Select a trigger and its desired state.

CHANGELOG

• Version: 1.3 - 21 Sep-23 - Update deprecated code.
• Version: 1.2 - 7 Nov-22 - Removed days and reduce hours to 4
• Version: 1.1 - 7 Nov-22 - Initial release

MY OTHER BLUEPRINTS

Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time
Sensor Light Add On - Media & Movie Lights - House Alarm Lights - Smoke Alarm Lights & Exhaust Fans + More
Bathroom Humidity Exhaust Fan
Calendar Notifications & Actions
State Notifications & Actions
Toilet Exhaust Fan with time delay
Entity - Run ON Timer
Turn Light, Switch or Scene On & Off with Trigger Conditions
Temperature Control Exhaust Fan
Temperature Control Exhaust Fan - Inverted
Push Button Relay - Contactor
Smart Relay - Contactor

Like this blueprint? Consider hitting the button below

[123 (Taras)]

This blueprint attempts to use a delay to simulate the function of a timer entity. The main drawback is that, unlike a timer, a delay can’t survive a restart.

The longer the duration of the delay the more vulnerable it is to termination by a restart (or simply by reloading automations in versions prior to 2022.11.0). This blueprint supports delays of hours and days which means the user should be especially careful of when they restart Home Assistant. Automations based on this blueprint may fail to run to completion (i.e. entities that were turned on won’t be turned off).

For long delays, it’s best to avoid delay and use a timer (with restore: true).

[Blacky]

I will look into that. Thanks for the heads up but it is time for Zzzzzz

I did original have timer but having issues with it on the trigger variable

[Blacky]

Update to Version: 1.2

On @123 advice we have removed days and limited the hours to 4 to reduce the risk of the blueprint fail to run to completion. Normally this time frame is all you will need anyway. If you need more hours just let us know.

We are going to look into timer for long delays when we get more time to spend on this blueprint.

If you have already created an automation with Version: 1.1 it will still function. If you update to Version: 1.2 we recommend you delete the automation created with Version: 1.1, update the blueprint to Version: 1.2 and add back your automation.

Thanks for your understanding.

Blacky

[Herr.Vorragend]

Is it possible to extend the trigger domains to input_boolean? So it is easier the create a helper for this automation?

Another feature request:
Could it be possible to disable the boolean after the countdown is finished?

Update:
hmm, I think that my wishes (e.g. an additional action) have to be implemented in my own individual automation. A blueprint would be too specific.

[Blacky]

Could you give us an example of what you are trying to do so it helps me to understand.

[Herr.Vorragend]

It wasn’t really well thought out on my part. With a normal automation it is easier with my special requests.
I want to start a timer via an input_boolean (“activate pool pump for 30min”). After the timer has expired, the input_boolean should be turned off and a pushover message should be sent.
The plan is to start a pool pump over it.

I did it now with an own automation.

[Blacky]

New update 1.3

BLUEPRINT CODE UPDATE

Just a heads up if your still on a old HA version before you update.

From time to time Home Assistant update their code structure and the old code will become “DEPRECATED” stopping / breaking automations from working. It effected this blueprint about 4 to 6 months ago. I wanted to wait some time so everyone had a chance to update their HA version before updating the code as older HA versions can not run the new code. This blueprint has now been updated so it will still operate once HA remove the “DEPRECATED” code from their system.

If you like this blueprint? Consider hitting the button in the top post

If you like my blueprints, and would like to show your support or just say thank you? Click Here

Enjoy

Blacky