Nice one thanks for letting us know⌠glad it helped you
Blacky
Thanks for this nice blueprint Sir, it is working very well.
First of all, what a wonderful blueprint! Thanks for your great work.
I would like to know if itâs possible to chain three blueprints together of which one will be duplicated.
My situation is as follows:
All fans are connected to the same central exhaust system. I would love to combine/link these three fans. In the kitchen and bathroom I have humidity sensors, in the bathroom I have a fysical button I can use.
I am not sure what your trying to do other than some type of linking but still unsure.
Blacky
Hi - I find this my most useful aspect of home assistant, after setting it up it just works! Great.
I need to replace my Mi sensor in the bathroom which is quite reactive, works great from a timing perspective with this blueprint. Would a Tapo T310 sensor, which is a bit less âchattyâ still work OK with this blueprint? Are there recommended sensors that work better than others?
Thank you for any assistance you can provide.
Thanks for your kind words and I glad it working for you. This is one blueprint I do love.
This is one of my set ups click here. It shows you the sensors I use.
If you use the Tapo T310 sensor test it out and let us know how it goes.
Blacky
Just starting using this blueprint. Itâs great. One thing I havenât figured out how to deal with yet is if someone turns on the fan manually before starting the shower, it will turn off after the manual timer even though the automation kicked in shortly after the manual trigger. I have my manual timer set to 15 minutes but the way the kids take swampy shower the automation needs to run the fan for almost an hour after it kicks off for the - derivative. Can you look at having the automation cancel the manual timer if it kicks in?
Thanks
Hi Steve, if you turn ON the manual trigger then the automation gets triggered by your Trigger - Humidity Derivative Sensor it will takeover your manual trigger.
Blacky
An âif entity on by automationâ condition prevents overriding manual operation.
To do this, my âturn onâ automation uses an input_boolean âonâ action. The âturn offâ automation checks if the input_boolean is âonâ before proceeding to turn off.
This prevents manual override.
Hello,
Any thought to putting active window adjustments into the blueprint so it cannot trip during certain hours. Bath fan and light came on at 3 AM due to glitch in humidity sensor.
Thanks,
Roger
You just use a schedule helper and then use the bypass.
Example:
Your done.
TIP: If you put your phone on do not disturb when you sleeping then you can use that rather than a schedule helper.
Blacky
Thanks for the great blueprint! Iâve set it up (including a schedule bypass), weâll see how well itâs tuned in coming days.
One thing thatâs not clear is how the blueprint reacts to the use of the physical (smart) switch itself. My fan is linked to a physical rocker switch, and that switch to a smart relay inside the switchbox (think Shelly or Sonoff). Pressing the switch tells the relay to toggle, and the relay is the entity seen by HA. What will happen if I toggle the wall switch either to turn on or off? Will the blueprint override the wall switch? The documentation says the âmanual switchâ cannot be the entity itself.
Thanks!
It should still work but if you would like to get some additional control out of it then maybe use Manual Control Status Tracker blueprint. Then use the Manual Control Status - Toggle Helper in either the Manual Trigger or Manual Fan Switch then you can use the auto OFF option.
Blacky
Hi, for some reason the automation isnât being kept alive while the humidity is above the set âMax humidityâ
For example, 2 people shower within 60 minutes of one another, but the fan turns off after 90 minutes since the 1st shower regardless. Even though the humidity is still above the Max Humidity threshold?
Ps. I have set the âSafeguard - Maximum Run Timeâ option, but I think there should be another option to override this of humidity is still high?
Thanks in advance
Youâll notice that after the first shower finished, the humidity dropped slightly, causing the Derivative sensor to start turning things OFF. However, the humidity never dropped below your Maximum Humidity set-point and remained above it.
To resolve this, review the history graph of your humidity sensor. Look at what happened when the first shower ended, and again when the second shower began. Your Maximum Humidity set-point should be set low enough (but not too low) so that when the first shower finishes, the humidity drops below this set-point (quickly)⌠and when the second shower starts, it rises above it again.
Itâs a bit tricky, but this input/setting exists for exactly this reason (back to back showers with high humidity readings): when humidity stays high, small changes arenât picked up properly by the Derivative sensor.
In your case, the humidity never dropped below your Maximum Humidity set-point after the first shower, which is why the issue occurred.
Let us know how you go.
Blacky
Aha! Makes total sense!
So my setting was too low and it never dropped below that %
Iâll set it higher (like 90%)
Just a thought, wouldnât it be easier if you could set the blueprint to not turn off the fan as long as the humidity is too high?
So even if derivative dropped low enough to stop the fan, when the time comes to turn the fan off, if the humidity is still higher than the set max, to keep going until itâs below that level and then it can be switched off?
It looks like your humidity sensor might be getting wet. As the humidity rises, the derivative sensor shows a spike upward, but the humidity doesnât really drop afterward, and you also donât see a spike downward from the derivative sensor.
I recommend checking your humidity sensor. On mine, I drilled holes in the back and set up a fan to pull air through it. Iâm not saying you need to do exactly that, but if your sensor is getting wet, itâs worth addressing the issue.
Blacky
Hey @Blacky thanks for another amazing blueprint! Question: is there any easy way for me to add a condition to the automation? I donât want the automation to fire whenever a certain binary sensor is âtrue.â
I guess I could write another automation that activates and disables this automation based on the state of that sensor, but I feel it would be less kludgey if I could just add a âconditionâ to this one, no?
Your welcome!
Just use the bypass and then choose what action you would like. I would assume you will be after bypass option 2. Then use your binary sensor in Bypass Switch.
Blacky