Merci 
I’ll take a close look at that!
1 Like
I have a small issue regarding a second person taking a shower shortly after the first person, where it will turn off and then not restart even though the humidity jumps up again. Any pointers on how I can solve this would be great. Thanks.
Yes this can be resolved by using the Maximum Humidity Option in summer or winter mode. You will have to make sure you add your Bathroom Humidity Sensor in the Auto Triggers section.
I have mine set to
- Sumner: 85%
- Winter 87%
When you have back to back showers look at your humidity sensor and see what it goes to when you start a new shower. Then set it to that level and make it as high of a setting as you can to stop false triggers.
Blacky 
I’m having some issues with getting this automation to turn off the exhaust fan. The falling humidity derivative is set to -2%, and the derivative sensor definitely gets to that value after a shower.
Time delay is 10 minutes, safeguard time is 15 minutes. However the fan doesn’t turn off, even waiting for 30 minutes. After which I stop waiting for it, and I turn it off myself manually.
I created a more primitive version of this blueprint using the derivative helper and a chooser. That does correctly turn off the exhaust fan.
Something is wrong with this blueprint.
Would you care to share your blueprint/automation?
Sure. It is a simple automation I created via the GUI, but here it is in YAML form, which I guess is the easiest way to share it here.
alias: Auto Bathroom Humidity Fan
description: >-
Automatically turn on bathroom exhaust fan when humidity is rising, and turn
off when it falls
triggers:
- alias: When humidity rising
trigger: numeric_state
entity_id:
- sensor.bathroom_humidity_derivative
above: 0.8
id: humidity_rising
- trigger: numeric_state
entity_id:
- sensor.bathroom_humidity_derivative
below: -1
id: humidity_falling
alias: When humidity falling
conditions: []
actions:
- choose:
- conditions:
- condition: trigger
id:
- humidity_rising
sequence:
- action: fan.turn_on
metadata: {}
target:
entity_id: fan.bathroom_fan
data: {}
- conditions:
- condition: trigger
id:
- humidity_falling
sequence:
- delay:
hours: 0
minutes: 10
seconds: 0
milliseconds: 0
- action: fan.turn_off
metadata: {}
target:
entity_id: fan.bathroom_fan
data: {}
mode: single
1 Like
Nothing is wrong with the blueprint I use it 5 times a day for years now and it works perfect every time.
If you like me to look at it 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.
Blacky
Had been using the Blueprint for 6 months no issues. We moved to a new house with ducted air con. Now seems when house humidity is high, and I turn ON the ducted air con which drops humidity levels, the automation triggers bathroom fans ?
Is that possibly whats happening ? fast humidity rate drop triggering the automation ?
No, it should trigger on fast humidity rise using the Derivative Sensor. Then when it is running it will start the turn OFF process by fast humidity drop again with the Derivative Sensor but it must be running (not a trigger).
Make sure when you turn ON the ducted air the humidity levels don’t increase and it is being triggered by the Maximum Humidity setting if your using that option.
Have a look at what happens with your Humidity levels and the Derivative Sensor when the fans turn ON. You will then be able to find it and adjust your settings.
Blacky
1 Like
Thanks for this Blueprint! I’ve just set it up and was actually expecting the fan to turn off after the humidity fell back to within a similar range to when the shower started? Is using a time delay for off a better approach?
1 Like
Hello Blacky,
Do you maybe have some time to take a look with me to this automations? i don't get it to work!
Can we do that by discord ?
Regards Sander
Comment: Just wondering if your automation for the bathroom is using a generic global humidity value, rather than one specific to that room and sensor?
You wouldn't notice it as a logic issue until you added a second sensor without being specific as to which sensor you were testing against.
Used this blueprint for bathroom. Working well. Thank you for work.
Additionally it seems this blueprint can be used for refrigerator like info, when is time to defrost (existing sensors are room temperature, humidity and energy meter for refrigerator).
Any recommedation?
I just do everything here as it helps others to.
You just need to explain what you did and what is happeing and then just provide your settings YAML. 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.
Blacky 
1 Like
Glad the blueprint is working well for you. It sill one of my favorite blueprints that never skips a beat.
I don't have anything for defrost of a refrigerator.
Blacky
It was for that room. I setup a derivative helper based on the bathroom humidity sensor.
Regardless, I've moved on from this blueprint, to my own automation, so I can do things like change the LED bar on my Inovelli switches when the automation is running.
My custom one is much better for me now.
@Blacky I think because the automation mode in this blueprint is set to restart then there can be a race condition where the fan stays on indefinitely. This morning the automation fired twice in quick succession and then the second run failed conditions and stopped immediately even though the fan had already started. Should the mode be single for this blueprint instead?
That is okay it is still running.
No and the reason is we need it to restart. Example: Someone has a shower and finishes, the fan is running and waiting to time out but the next person enters the shower and triggers the automation again to start. If it didn't restart the fan would turn OFF and the second shower would not be taken care of.
Hope this make sense.
I very raillery update this blueprint because it has been working rock solid now for years. Theory is not broken, don't fix it. In saying that I do have an extra feature being added and will be out soon, so keep an eye out for it. It's a feature request.
Blacky
New Feature 
-
Operating Hours - Restrict the automation to only run between the start and end times on the selected days.
The operating hours only apply to automatic operation. The manual trigger, manual fan switch and bypass will still work outside the selected times, allowing you to manually run the fan when needed.
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 
2 Likes