Yes you can have Fahrenheit on the sensor and in HA
Edit: If you get some I would say get 5 + you will use them. I have one in my fridge, outside, kitchen, family room, bedrooms, laundry, etc. Once you get them it is nice to have. My batteryâs lasted over a year. My Atom Lite (ESP32) that runs my humidity sensor for the exhaust fan is also a Bluetooth hub thanks to HA that they connect to.
A lot that has been added to this new release. Hope you like it.
New Features 
Enjoy
Blacky 
Just found out about this blueprint, and figured someone might benefit from my two cents which solves the needing different seasonal baselines as well as potential false positives from organic large changes in humidity. Apologies if this has been covered before - I tried to read through the thread but I may have missed something skimming.
Because I have many humidity sensors (every motion sensor and every thermostat) I have a pretty good representation of the median humidity across my house. This gives me an excellent baseline to know when humidity for one bathroom differs significantly from the rest of the house. I created a helper sensor for the median humidity, and then derivative sensors for both the median humidity and bathroom humidity sensors. I then used these to create template sensors to calculate the difference between the derivative of humidity for a given bathroom vs. the median humidity overall. If this delta is positive of a certain magnitude for a certain period of time, I turn on the fan. If this delta is close enough to 0 for a certain period of time, I turn the fan off.
Hereâs an example config for the delta template sensor:
- platform: template
sensors:
master_bathroom_humidity_difference:
friendly_name: "Master Bathroom Humidity Difference"
value_template: >
{{states('sensor.change_in_master_bathroom_humidity')|float - states('sensor.change_in_household_humidity')|float}}
unique_id: sensor.master_bathroom_humidity_difference
Thanks for the info. I have been toying around to have an option to use a reference sensor. But it has never work well enough or I havenât nailed it yet for me to include it in this blueprint.
Have you tried using this blueprint as is?
Blacky 
Hey @Blacky. I have just installed this blueprint (after taking an obligatory shower to start recording derivative stat patterns). I have also seen (and imported but not yet setup) the Temp Control Exhaust Fan and Toilet Control Exhaust Fan. Do all 3 of these automations conflict with each other if you try and run them for 1 room? I currently have a NR workflow setup but it is pretty complex (and doesnât do temp control) and it would be nice to move over to automations like the amazing work you have created in all 3 of these.
My own environment setup is an ensuite bathroom, with shower, toilet and sink. The exhaust fan was a continuous running fan that was controlled by light switch (ensuite light off and the fan would run in lower power mode, turn the light on and it would run high power mode). About a year ago I added a Shelly 2.1 into the mix and an Aqara humidity sensor. I can now control each of the high and low speed fan as and when I want rather than it running all the time which means night time no fans run anymore unless someone either uses the toilet or shower and even then, once humidity/time is down to a level I want the fans turn off.
Also, would the âHumidity Derivative Sensor By-passâ be something like an automation enable/disable switch/input_boolean? The FAQ shows a question on how to set this up but no answer. I am guessing it is for overriding the automation - eg each and every automation I have in the house can be overridden with an input_boolean for the given task such as donât turn the lights on for a given room when it is dark
Hi James
I would say yes but it will just depend on what is happening.
This is on the road map ahead.
Yes.
There is a bigger roadmap ahead that I am sure you will like without say to much.
For your lights have a look at my 
Sensor Light blueprint
@Blacky thank you for the answer. I will configure the other 2 for now and see how it all interacts.
The bigger roadmap sounds very interesting though 
Thanks for the tip regarding the lights however I donât have control over those for the ensuite and they are dumb lights. The Shelly only controls the fan based on a seperate feed from the light switch which is what used to make the fan high power or low power depending on current.
EDIT: DOH! My mistake, I see what you mean about the light automation. Might be of use elsewhere around the house as long as I can work in the house modes into the automation ( I run house modes of away, night, evening, midweek, morning midweek, weekend, morning weekend)
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
@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.
Just developing now and I will do a quick test.
Edit: Check you messages, all done
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
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;
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 
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
