⏱ Trigger - Run ON Timer

What I need to control my MVHR fan boost in homeassistant, is to switch a Boost fan on when ANY bathroom light (upto 4 lights) turns on.

The Boost starts after a delay (5 min) and stays on while ANY light is on.

After ALL the lights have gone off then turn Boost off after another (20 min) delay

Also a manual boost on would be useful, as would your weekday selection!

Is there a version of one of your amazing blueprints that might achieve this?

Thanks
Fred

@Fastfreddy

Currently I don’t have a blueprint that would do this.

Blacky :smiley:

No worries, I’ve written an automation that does it :grinning:

1 Like

@Fastfreddy

Nice one

Blacky :smiley:

Hey,

is it possible, to change the timer with a slider in the dashboard?
I want to control the time, a device is turned on…
Greets

@Scratcher48

Yeah, anything is possible it Home Assistant :wink:

I will explain why I develop it like this and how I use it as it may help you or anyone reading this.

My use case is to turn on my electric blanket in my bed. Depending on how cold it is depends on how long I would like my electric blanket ON. When developing it a slider is hard to set on your mobile phone and I just wanted something quick and easy. The electric blanket is plugged into a smart switch and it is turned ON for the max time. Safe guards are in the electric blanket controller so all is good.

  1. I created 4 press button helpers and a timer helper.
  2. Select any state change, enable all triggers, entered in my smart plug, enabled timer helper and enter in the helper.
  3. Then I put each press button helper in each timer input.
  4. Then with time I have one for 30 min, one for 2 hours, one for 4 hours and one for 9 hours.
  5. Then I added each button helper into the dashboard and the timer helper (Tip: If you click on the timer helper you can stop it, pause it etc).
  6. Now when I would like to turn on my electric blanket depending on how cold it is I just press the button for the time I would like, no slider to adjust just press.

It is a blueprint as I use this on all my beds and beds have 2 sides (2 controllers)

I don’t know if that will work for you but I thought I would explain this as it just could be what your looking for.

Blacky :smiley:

Hello,
I love your blueprint. But I have a problem with it.

When I want it to control climate it will turn it on, but it won’t turn it off.

Here is my config:

alias: "FVE: Turn on boiler for a given duration"
description: ""
use_blueprint:
  path: Blackshome/trigger-run-on-timer.yaml
  input:
    timer_helper: timer.bojler_casovac
    entity_input:
      entity_id: climate.kotelna_bojler
    include_timer_helper: enable_timer_helper
    trigger_one_time:
      hours: 1
      minutes: 0
      seconds: 0
    trigger_two_time:
      hours: 2
      minutes: 0
      seconds: 0
    trigger_three_time:
      hours: 3
      minutes: 0
      seconds: 0
    trigger_four_time:
      hours: 4
      minutes: 0
      seconds: 0
    trigger_state: state
    trigger_one:
      - input_button.bojler_na_1h
    trigger_two:
      - input_button.bojler_na_2h
    trigger_three:
      - input_button.bojler_na_3h
    trigger_four:
      - input_button.bojler_na_4h
    include_extra_triggers:
      - use_trigger_two
      - use_trigger_three
      - use_trigger_four

Did I do something wrong? Or could you fix it, please?

Thank you,
Tomas

@tomasd

All your YAML looks good, just check your timer helper. Below is my one for your reference. Note the duration and the restart must be ticked so it will survive a HA restart.

Let us know how you go.

Blacky :smiley:

I have the timer set the same. This is a trace that happens when the timer stops and the climate should be turned off:

I’m not sure which parts of the trace are useful.
This is step details:

Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/0/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: false
entities: []
conditions/1
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/1/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: false
entities: []
conditions/2
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/2/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: false
entities: []
conditions/3
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/3/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: false
entities: []
conditions/4
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/4/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: true
entities: []
conditions/4/conditions/1
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/5
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/5/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: true
entities: []
conditions/5/conditions/1
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/6
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/6/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: true
entities: []
conditions/6/conditions/1
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/7
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/7/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: true
entities: []
conditions/7/conditions/1
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/8
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/8/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: true
conditions/8/conditions/1
Executed: January 21, 2024 at 12:20:49
Result:
result: true
entities: []
conditions/8/conditions/2
Executed: January 21, 2024 at 12:20:49
Result:
result: false
entities:
  - climate.kotelna_bojler
conditions/9
Executed: January 21, 2024 at 12:20:49
Result:
result: false
conditions/9/conditions/0
Executed: January 21, 2024 at 12:20:49
Result:
result: false

For the sake of testing, I’ve set the run time for 10s.

It does not work just for the climate. When I change the boiler climate with a switch it works great.

Should I send you anything else?

I see, I will PM you.

Blacky :smiley:

Hello !
Many thanks Blacky for this really nice blueprint.
I wanted to develop one but yours is so advanced I gave up mine :wink:

I would like also to add a condition (SUN condition).
How I could achieve this in your opinion please ?

My use case:

  • 3 triggers (1 helper “button”, 1 switch, 1 motion sensor)
  • the entity to turn on is a light
  • I would like to switch on the light when a trigger is activated AND during night only

Another request:

  • could you add a notification system before and after the action ?
    For instance, a notification is sent via Telegram or other solution before the light is switched on and another notification after it is back to off.

  • last question: how do you display remaining time of a timer please ? I can display the duration of the timer in a card but not the remaining time.

Thank you again !

Hi again,

I’m still testing your blueprint. I’m facing an issue when I use a timer helper:
Everything goes well until the timer is over:

When I click on the trigger-button, the timer looks good:
image

At the end of the timer, the light doesn’t switch off and in the log:

homeassistant  | 2024-02-23 08:45:04.024 WARNING (MainThread) [homeassistant.components.automation] Error evaluating condition in 'Test timer bureau':
homeassistant  | In 'condition':
homeassistant  |   In 'or' (item 9 of 10):
homeassistant  |     In 'and' (item 3 of 3):
homeassistant  |       In 'template' condition: UndefinedError: 'dict object' has no attribute 'entity_id'

I don’t understand my issue… :thinking:

Thank you in advance !

It is probably because you are using a device and not an entity. But have a look at this blueprint :magic_wand: Manual light control with auto OFF it may be more inline with what you are trying to do.

Blacky :smiley:

Hi,

Many thanks !!! I changed to an entity and now it works perfectly !! :sparkler:

The blueprint you mentioned is not totally what I’m looking for, but I keep it :+1:

Thanks ! :pray:

1 Like

FAQ

Q: How do I create a timer helper?

A: Follow these steps click here

FAQ - How do I create a timer helper?

To create a Timer Helper, follow these steps:

  1. Navigate to Settings > Device & Services > Helpers tab at the top.
  2. Click the Create helper button.
  3. Select Timer.
  4. Provide a Name and Icon of your choice. Leave the duration set to 00:00:00 and tick the Restore box.
  5. Click Create.

5

Your done :tada:

Enjoy

Blacky :grinning:

Back to FAQ: Click Here

New update 1.7

:new: New Feature - Collapsible Sections

  • Collapsible Sections - Added collapsible sections to the blueprint. This enhancement improves the blueprint user interface by making it cleaner and more organized, allowing sections to be collapsed.

    :warning: This feature was introduced in Home Assistant 2024.6, so you must have this version or later for the blueprint to work.

:toolbox: Maintenance

  • Set blueprint to my new layout.
  • Update input descriptions for better understanding.

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

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

Enjoy

Blacky :grinning:

3 Likes

My end durations were never triggering the ‘off’ state. I finally recognized I had changed “Use The Timer Helper Options” to ‘Use a timer helper’. I expected that since I hadn’t selected a Timer Helper in the next form item, that it would fall back to the default delay duration triggering the ‘off’ state but this is currently not the case. Basically, if you say you’ll use a timer helper but don’t specify one, your timer will never fire.

I suggest removing the 'Use a Timer Helper Options question altogether. You can infer from the ‘Timer Helper’ question. Use one if one is specified, otherwise don’t.

@hubdedub

Welcome to the comunity

If you select to use the Timer Helper then yeah you have to input your timer helper into the Timer Helper input. In the description of Timer Helper input is states that you need to select your timer helper if you opted to use a Timer Helper. I will update it so that if you select to use a Timer Helper and you don’t select one it will not work.

Thanks for your feedback.

Blacky :smiley:

New update 1.8

Maintenance :toolbox:

  • From time to time, Home Assistant updates their YAML standards and coding practices. To align with their roadmap, we’ve updated the code accordingly. We will continue to apply these updates across all our blueprints as they are revised.
  • If you opted to use a Timer Helper and you don’t input your timer, the automation will not run.

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

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

Enjoy

Blacky :grinning: