It will be interesting on how it goes. I have never tried or have never run any tests. Let us know how you go.
I am developing something now, but I like to test it and use it before I release it.
Very interesting
1 Like
@Blacky sure will let you know how all 3 fan automations work together 
I would certainly be up for testing when you are ready for testers.
I have just configured the âToilet Exhaust Fan Automationâ. One suggestion if I may, for greater control and consistency between bathroom humidity automation and toilet automation (not configured the temp automation yet) - would it be possible in a future release of toilet automation to add âFan Switchâ option from humidity automation to toilet automation by replacing âFanâ as a single option? Thereby allowing more than 1 fan entity/device to be selected. Reason I ask, and I know I can create a script or new switch sensor, is with the Shelly, to get high speed fan working the low speed fan needs to be switched on; if low speed is not on high speed will not come on even though the state of high will be showing as on (its a pain in the butt and I havent gotten round to creating a script or sensor if I am honest but just thought it might be good for consistency between automations to have the same option control)
Humidity automation:
Toilet automation:
Also, a trigger sensor bypass in the toilet automation would help for consistency (I see that option is in humidity and temp automotions)
I will PM you with the update you would like.
1 Like
Just developing now and I will do a quick test.
Edit: Check you messages, all done
1 Like
Im using a Ducobox with a Open Air Mini including a humidity sensor. How can I use/change this blueprint so I can have the fan idle on 30%, set the speed to 100% when somebody is using the shower and after the humidity reaches the desired level set the fan speed to 30% (for example)?
I donât use Ducobox but it looks like a realy nice product. The âFan Speed - Switch Off Optionâ was developed for the Itho box and I think this is a similar product.
With your Ducobox if you have an entity in HA that set the speed to 100% then you would put this into the âFan Switchâ. Then if you have an entity that set the speed to 30% then you would put that into the âFan Speed - Switch Off Optionâ and enable this option. Because I donât use or have a Ducobox I am not sure if it has these entities in HA. If it doesnât have them then you could create them probably like a fan speed switch where ON = 100% and OFF = 30%.
PS: Just make sure if it is the one fan that you canât turn 100% ON at the same time as 30%, so it would have some type of interlock that will only allow one of the two entities to be ON at any given time.
Blacky 
I will give this a try. thank you
You will need to do something in this update. See below âClear Home Assistant Restart YAMLâ.
New Features 
- Home Assistant restart built in, no more selection required. You will need to clear the old HA restart yaml, see blow. The restart feature now has a lot of extra features built in that will check your automation for you.
- By-pass upgrade. There are more option to choose from.
- By-pass auto OFF feature. You can now set the by-pass to automatically switch off. It can also be used as a timer to turn the fan ON and then OFF if you have chosen to use âEnable the By-pass - Turn fan ONâ.
- It now can also work with my just released new blueprint
Sensor Light Add On - Media & Movie - House Alarm - Fire Alarm + More. If you have smoke detectors connected to HA, the blueprint add on can now disable this blueprint automations and turn your exhaust fan ON including lights when the smoke detector is activated. It is all done through the by-pass hence the by-pass update.
Clear Home Assistant Restart YAML 
To clear your HA restart yaml please follow these steps. This is only required if you are updating the blueprint.
1 - Update you blueprint and open your automations.
2 - Click on the 3 dots top right.
3 - We are looking for the code , âha_restartâ and âinclude_ha_restartâ as shown below. If you donât see this code then you are all good, no need to do anything further.
4 - If you see the code then delete it, click save then the 3 dots and âedit in visual editorâ.
5 - Your all done.
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 
Thank you for this awesome blueprint!
My exhaust fan runs for 10 minutes per activation / button press. Is there some way to reactivate the blueprint after 10 minutes if the humidity is still to high, so the exhaust fan starts again?
Hi Robin,
Your welcome and thanks for your kind words 
Yes in some situations. If your humidity is staying high then best to run the fan for longer, so extend your time delay. There is a âMaximum Humidityâ setting but it must cross over from a lower setting to above you setting, then the fan will turn ON automatically.
You can also manually do this with the by-pass. How to set this up;
- Select â1 - Enable the By-pass - Turn fan ONâ
- Create a by-pass, this is in the FAQ if you need it and enter it in.
- Select âWhen you turn the by-pass off - Do not run the automation and turn the fan off instantlyâ
- Select âEnable the by-pass auto off optionâ
- Set your âBy-pass Auto OFF - Time Delayâ
Now when your turn the by-pass ON it will turn the fan ON and then OFF in your set âTime Delayâ. It is a manual operation though.
Hope this helps
Blacky 
1 Like
Thank you for your help!
So if I understand correctly, there is no way to automatically reactivate the fan after 10 minutes if the humidity stays high?
The blueprint works off and Humidity Derivative Sensor. It a bit tricky to get your head around. I will explain.
Say humidity is 75% and it rises to 90% the Humidity Derivative Sensor will see this and knows you are having a shower. Fan ON. If the humidity stays High then the Humidity Derivative Sensor just stays at 0% and the fan stays ON. When the humidity drops the Humidity Derivative Sensor then knows you have finished by going to a negative value. It will then start the time delay set by you. Make sure you monitor this so you know the humidity drops before turning OFF the fan and adjust the time delay as required. So your humidity should drop. If this doesnât happen then you have a âSafe Guard - Maximum Run Timeâ that you can adjust so the fan will turn OFF and not just run forever.
So if you set it up correctly the humidity should drop before the fan turns off.
If it drops but not enough to turn the fan ON again when you are having back to back showers then the âMaximum Humidity Optionâ will turn the fan ON. Example the humidity drops to 80% enough to start the time delay but when it rises to 95% it is not enough for the Humidity Derivative Sensor % but is triggered ON because the humidity crosses over Maximum Humidity and turns the automation ON again. You dont know this because the fan never turned OFF it just stays ON until the humidity drops again. This is were your question is. So the humidity should at this point be lower than your Maximum Humidity Option and if it increases above your setting then it will turn the fan ON again and run the automation.
To answer your question it is yes but no, the automation will not turn the fan ON again if the humidity stays high for x amount of time, but this should never happen if it is set up correctly and you have a fan that is adequate for a shower exhaust.
My recommendation would be to read the settings FAQ Click Here. Monitor your showers and adjust your setting to you get it right. I have included my settings in the documentation and this should be very close to making it work but ever site is different. I does take some time to get the settings correct but once you get it, the automation should work perfectly. Sensor location is critical to making it work as well.
Hope this helps you
Blacky
1 Like
Thank you so much for your time and explanation! Itâs a bit more clear to me now. I will monitor the behaviour of the blueprint and humidity for the upcoming days and see if I can finetune it. Thanks a lot!
@Blacky first of all thanks for a great blueprint, it works well, but Visual Studio says there is Deprecationâs in your script.
Hi Andy, Thanks for the heads up I realy do appreciate it
I did see this on the latest Visual Studio pop in this update. There is no problem as I know how to fix it and it the same in all my blueprints. I didnât want to push out the fix ASAP as if you dont have the latest HA it will probably break the blueprint. HA have said that they are giving a 12 month period now before they turn OFF breaking changes. By then I will resolve this probably around the 3 to 6 month mark so everyone will have time to update HA and everyone will have time to also update this blueprint before it stops working 
.
Again, thanks for the heads up, it is realy nice to know of these things ASAP and sometimes I miss them.
Blacky
np, iâm just starting to understand blueprintâs so I can do some of my own in time.
2 Likes
Well, this is different. For the last 3 years, I have been controlling the bathroom humidity in a crude way, through node-red. I just now happened on this post and will have to read through it. I thought I was the only one interested in this. I am very happy someone else is talking about this subject. Below are my iterations in node-red (the uneducated way, lol).
https://github.com/fixx-er/Project-files
Yeah, this is one blueprint I realy love and it works well. Since using it all the mould issues in the bathroom are gone. In the past, someone in family would forget to turn the fan ON including me, now it never forgets and we use to turn the fan OFF when we would leave the bathroom, now it runs for the correct amount of time before turning OFF.
Blacky
1 Like
Bathroom Dimmer turned off triggered by automation Bathroom Humidity Exhaust Fan triggered by numeric state of Bathroom De-Humifier
Not sure why the light was turned off. I donât see where I set it to do that? Is this not configurable? Thanks.