@Kervanoglu … I will PM you.
Blacky
how do i import this blueprint?
i’m getting
Invalid blueprint: extra keys not allowed @ data['blueprint']['input']['timer_helper']['selector']['filter']. Got None
Not very helpful error message to me
Hi Patric, Firstly welcome to the community… nice beard
They can be a bit tricky. Looks like you are on an older version of HA. Please update your Home Assistant and you should be good to go.
Blacky
Thank you!
Updating HA was the solution
Hi Blacky
Love your Blueprints, I am using Sensor Light in the Whole house
I want to ask you if you might be interestet in helping me, by maybe updating this blueprint (Run ON Timer), or maybe you have a much better idea on how to do it…
My usecase is:
I have some heattracing, on some piping, on the attic.
I also have an outdoor temp. sensor.
The idea is if the temp. fals to below 0 degress celsius, I need the timer to go on for maybe 5 minutes(adjustable), and then off, for maybe 1 hour(adjustable), turn on 5 min, and then off (you get the picture)…
This behavior should continue until the temp is above 0 degress celsius again.
I have made 2 timer helpers, an ON and a OFF timer
The trigger I could do with an automation on the side maybe, so your blueprint remain being a timer base. (I think I could make that with my limited skills, with a below or above trigger something )
In short words, can you make this blueprint an option to go, on and off, as long as the trigger is high? With the use of timer helpers(would be bad if the heating never turned off due to reboot).
Would/could you in anyway help me, and maybe ad this posibility to the blueprint?
Best regardz Shorty
This is the blueprint that you would use.
Temperature Control Exhaust Fan - Inverted
If you would like more help then just PM me.
Blacky
@Blacky - how difficult would it be to add the bypasses you have in some of your other blueprints?
My scenario is I have a light and exhaust fan. I don’t always want the exhaust fan to turn on when the light is turned on. But if the exhaust fan is turned on, I want the timer to start when the light is turned off instead of right away.
Thanks!
Have a look at my Toilet Exhaust Fan with time delay blueprint. This is all possible an more.
Let me know if this works for you.
Blacky
hey @Blacky - I gave that a try but it doesn’t work quite the way I want it to. I don’t want to tie the trigger of turning the fan on with the light switch at all. Really what I’m looking to do is
I don’t think I can achieve that with the other blueprint since it’s designed around using the light (or motion) as a trigger
You can do this but not with my blueprints as it is realy a custom automation. If you are not sure how to do this then PM me with your entity ID’s for
Blacky
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
No worries, I’ve written an automation that does it
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
Yeah, anything is possible it Home Assistant
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.
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
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
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
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