alias: Badkamer FAN automatie
description: ""
use_blueprint:
path: Blackshome/temperature-control-exhaust-fan.yaml
input:
trigger_sensor: sensor.shelly_temp_sensor_humidity
entity_turn_on:
entity_id: switch.badkamer_ventilator_switch_0
rising_value: 75
falling_value: 68
maximum_run_time:
hours: 0
minutes: 45
seconds: 0
after_time: "07:00:00"
before_time: "23:00:00"
include_maximum_run_time: enabled_maximum_run_time
include_time: time_enabled
Thanks Kim, found a bug, it is fixed and updating now. Let us know if it is working.
Blacky 
Bugs Fixes 
- Fix a bug if no global condition was set the automation would not run.
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 
1 Like
Hi - this seems to be exactly what iāve been after and as similar posts have suggested I am using it to trigger heating on/off. Thankyou!! 
I do seem to be having issue after my initial testing. If I manually run the blueprint it works as expected.
How frequently does it run, or pull data before a decision is made? Or do I need to something else with this? As it does not yet seem to be āautomatedā For info I have enabled time options and during testing they are within the range.
Firstly welcome to the community.
Could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on ā</>ā and paste code in there.
Many thanks for the welcome and reply. It is appreciated. As requested please see YAML code below. Hopefully I have just missed something silly(?)
alias: Office Heating
description: ""
use_blueprint:
path: Blackshome/temperature-control-exhaust-fan-inverted.yaml
input:
trigger_sensor: sensor.office_thermostat_temperature
entity_turn_on:
device_id: 5c05ea8bbcf9faad96a4a4ab52e2e136
falling_value: 17
rising_value: 22
include_time: time_enabled
after_time: "08:00:00"
before_time: "17:00:00"
weekday_options:
- mon
- tue
- wed
- thu
- fri
Edit: I should mention that I am using v1.2 āInvertedā
No problem, good to know.
I will move this to the inverted blueprint to stop confusion for others reading this.
I have the same problem - I would like to run a script rather than operate a switch but only switch entities show up. HA version up to date.
Iāve tried editing the input code under domain to add ā-scriptā but that doesnāt seem to work - and I have to admit I have no idea what I an doing.
Any help?
I will PM you.
Blacky 
Hi Blacky.
I was wondering if you would consider adding the option that if a fan entity is selected, allow setting the fan speed and oscillation.
And thanks, I love your automations.
Thanks for you idea, I will add it to the list.
Your welcome.
A really nice option would be to add a time delay to the Trigger Sensor. The Temperature would have to be above Rising Value for X seconds. The same could be added to the Falling value. Also the ability to add scripts to the ran. I would like to send a notification when the fan turns on.
Thanks,
Have a look at this blueprint 
State Notifications & Actions it is what you are looking for. Have a look at it and if you have any questions just ask in that post.
Blacky
That would work but it would be nice to add Notification capabilities to some of these other blueprints. They donāt have to be as elaborate with the actions and buttons.
You dont have to use the action buttons. It will give you your Rising Value for X seconds and your Falling Value for X seconds. You can also run scripts in your actions. Just donāt enable the action buttons and enable the auto actions. Then enter your script and you are done.
Blacky
This blueprint has been great and Iām using it for a couple different things. One thing Iām trying to do is have it turn back off after another sensor rises above a certain temp but I canāt seem to find a way to do that.
The exact use case is: I have a temp sensor in my attic that is driving the main trigger. Once it rises above 95F it turns on a fan that pushes warm air into my workshop below. It then shuts off if the attic temp drops below 70F. Works great but what I would like is a secondary temp trigger for when my workshop is above 72F it shuts off.
Any ideas?
1 Like
Hi Blacky. Thanks for sharing your wisdom with the community. Iām new with HA. The temperature control automation turned the fan on when the sensor reached the rising-value temperature and turned it off after the max_run_time. However, it has not turned it on again even when the temp is still above the threshold. Since the temp in the garage is above 80F during summer, my idea is turning the fan on for 30 min periods, if possible wait x minutes, then turn it back on while the temp is above limit otherwise the fan will stay on forever.
Firstly welcome to the community 
Currently it does not have that feature but I can see what you are trying to do. Remember I am just reading this in 1 min and replying so I am trying to get my head around it. I value your feedback.
If you turn the fan ON because it is above 80F and then turn it OFF and it is still above 80F to then wait and turn it ON again like a cycle what are you gaining as apposed to just not turning it ON in the first place. Are you just trying to save power so that when it can bring the temp down, it can (due to night fall or a change in the weather conditions) because it just keeps trying? It could also reduce annoying fan noise and ware and tare on your fan I am one for saving power not only for the cost saving but it is just a good thing to do. The more I type it is not a bad idea. I will put it on the list to do.
Let me know your thoughts and thanks for your kind words.
Blacky
Would it be possible to add the same bypass logic here as in the sensor light blueprint?
I am trying to use this blueprint for my ceiling fans and would like to have multiple bypass on and off situations.