Iām using the Toilet Exhause Fan blueprint. The complication is my ON/OFF switch actually has the power control for the fan built-in. So if someone turns OFF the switch then the fan stays OFF.
Question: If someone turns OFF the fan switch while itās running, How do I make the fan turn back on, if the timer is still counting down?
Edit : Iām using v2. 0
Not clear to me whether v.2.x updates have a way to override the human who turns OFF the switch, but I want it to run for the full timer amount of time.
Thanks, Iām curious though ā¦ The āswitchā is a wireless smart switch that reports itās power state to HA, its power can be turned ON/OFF thru HA, and ALSO the bathroom user can push the switch buttons ON/OFF (the entity state change reported to HA). The switch = Lutron PD-8ANS-XX
What we want is for the fan to always remain on during the delay time. If the switch entity state changes to OFF during delay time for any reason, then the Blueprint should turn it back ON.
Maybe you could point me to where in your Blueprint code I could look to see about altering it to force ON always during delay time?
Edit: thinking about it, maybe it would require re-entrance of the code, or else some nested looping. Maybe not yet possible with Blueprint YAML?
Collapsible Sections - Added collapsible sections to the blueprint. This enhancement improves the blueprint user interface by making it cleaner and more organized, allowing sections to be collapsed.
This feature was introduced in Home Assistant 2024.6, so you must have this version or later for the blueprint to work.
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
Safeguard - If your trigger is a light and it remains ON (keeping the fan ON), you can set a maximum run time to automatically turn both the light and fan OFF. No more getting cross at the children for leaving the light ONā¦ Family peace is restored . The new feature is found in the Triggers section.
Maintenance
From time to time HA updates their YAML and the way they would like to wright codeā¦ so we updated the code to follow their road map. We will be doing this through all of our blueprint as we update them.
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
Question : Why can the blueprint only switch on one entity? My ventilation connected to KNX has lo-mid-hi, now it switches on only the low. I would like to use it in the shower and sync it to the bathroom light and then switch multiple entities to on.
Feature request to make it perfect : enable for example one entity in the first X minutes the light is on but when the light remains on, switch on more, additional entities. Thanks!!
First, thanks for all your great blueprints. For my bathroom fan, I now have a quite complex setup in combination of your bathroom humidity exhaust fan in combination with this toilet exhaust fan (linked as described). This all works well. Now i use your bee in the hive blueprint as a trigger for the toiled exhaust fan. This also works fine.
Now I added a manual switch with auto off to the toiled exhaust fan (to be able to manually start the fan when needed). This also works.
Now the problem. I today started the manual switch when leaving the bathroom (fan went correctly on). The door was closed while motion/bee in the hive was already active but didnāt pass the trigger wait time of the toiled exhaust fan. After the trigger wait time delay, the automation was stopped as the bee in the hive trigger went from on to off.
But now the fan was still on and didnāt stop automatically.
Thanks for the prompt reply. As I want to keep the trigger wait time from the toilet exhaust fan (after being triggered from the bee in the hive sensor), I think I have to keep all of your blueprints.
Initially, I put the manual fan switch to the toiled exhaust fan automation. I now moved that to the manual fan switch of the humidity exhaust automation and everything seems to work after some quick tests; I will observe that in the coming days.
So now (maybe it helps someone):
The bee in the hive automation sets a bee in the hive sensor
The sensor light automation only controls the lights and is triggered by a group of the motion sensor and the bee in the hive sensor. Additionally, it can be triggered by a manual switch over the bypass options (1 - Enable the bypass - Tun lights on)
The bathroom humidity exhaust fan automation is triggered by humidity or a manual fan switch (2 - Enable manual fan switch + auto off option) and enables the fan entity and the automation link over the fan switch option
The toilet exhaust fan is triggered only by the bee in the hive sensor and enables the fan entity. Additionally, the automation link keeps the fan current state (3 - Enable the By-pass - Keep the fan current state) over the automation link
@Blacky
Thank you very much for your work, it suits my needs exactly.
I would be happy to make a small improvement.
Background: I added a physical switch to the fan that is not connected to the smart home (due to various constraints).
I want it so that if the fan was turned on via the physical switch before the automation trigger started, it will maintain the fan state for X minutes.
What I did now is define a binary sensor to the fan state and set it under option 3 in the bypass.
Or maybe thatās what you meant in the first place?
You have to determine if the fan was turned on manually or by an automation. Use this blueprint to do that by adding your fan and a toggle helper Manual Control Status Tracker .
Fan in Target Entities To Track
Toggle helper in Manual Control Status - Toggle Helper
Then when you turn the fan on manually you can use the toggle helper in the bypass
Option 3 with auto OFF = Toggle helper.
The when you turn the fan ON manually the bypass option 3 will be active and the auto OFF in X will turn the fan OFF.
If the automation turns the fan ON it will run normally.
@Blacky much appreciate all the blueprints, they are awesome!
I do have a slightly different use case. Do you think itās possible to keep the fanās duration based on how long the trigger sensor stayed active?
I want the fan to turn on immediately when the trigger is ON, then turn off when the trigger is OFF for quick business (stepping in to wash hands or going number 1). But also have the option to keep the fan on for letās say 30 minutes after the trigger is OFF (did a number 2).
Example:
Scenario 1: Washing hands or going number 1, motion/light sensor only stayed active for 2 minutes, so turn the fan off right away.
Scenario 2: Going number 2, motion/light sensor stayed active for 10 minutes, so keep the fan on for 30 minutes longer.
I donāt think these 2 scenarios can be set up in the same blueprint atm.
Currently the blueprint can turn the fan ON if the trigger is ON for X (wait time) but it will not turn it ON instantly when the trigger is ON. The idea is to keep the heat or cold in and only exhaust if needed to save $$. It also stops drafts when you donāt need it and I have found the girls like this option.
Your suggestion not a bad idea ā¦ I put it on the list.
Turn ON but use the wait time ā The fan turns ON, but if the trigger turns OFF before the full wait time, the fan will turn OFF after a brief delay. Great for both short visits (with a short fan delay) and longer stays (with a longer delay if needed).
Maintenance
Cleaned up some conditions.
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
New Feature
This feature was introduced in Home Assistant 2024.6, so you must have this version or later for the blueprint to work.
button in the top post 
. The new feature is found in the Triggers section.
ā¦ I put it on the list.