⏱ Timer Relay - Run ON Timer

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

GitHub Link Click Here

Like this blueprint? Consider hitting the :heart: button below :+1:

Version: 1.2

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

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.

:rocket: CHANGELOG

Version: 1.2 - 7 Nov-22 - Removed days and reduce hours to 4
Version: 1.1 - 7 Nov-22 - Initial release


:bulb: Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time
:shower: Bathroom Humidity Exhaust Fan
:toilet: Toilet Exhaust Fan with time delay
:hourglass_flowing_sand: Entity - Run ON Timer
:gear: Turn Light, Switch or Scene On & Off with Trigger Conditions
:thermometer: Temperature Control Exhaust Fan
:snowflake: Temperature Control Exhaust Fan - Inverted
:nazar_amulet: Push Button Relay - Contactor
:on: Smart Relay - Contactor

Like this blueprint? Consider hitting the :heart: button below :+1:

1 Like

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).

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

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 :grinning: