Well you did say I could ask any further questions, so here is one.
How do I prevent the fan from turning on overnight? Iâm using this in our en-suite and I donât want the fan to come on when weâre asleep. Previously, my automation has checked a âquiet_timeâ binary sensor, but the only thing I can see in the blueprint is the derivative sensor bypass. Unfortunately, the auto-off timer for the bypass switch only seems to last a maximum of 4 hours.
Rather than having another, seperate, automation turn the bypass on and off based on the state of my âquiet_timeâ binary sensor, is there a way you could incorporate such functionality into the blueprint?
For context, because Iâm using this in an en-suite, and Iâve reached the age when I face the inevitable visit through the night, the humidity can often rise sharply when the door is opened due to the moist air in the bedroom migrating into the en-suite.
So it would be good to be able to set a start and finish time for the bypass to prevent it coming on overnight.
fyi: found the cause, deleting and recreating the derivative sensor with a different entity name sorted the issue, it seemed to have somehow inherited the original deriviative sensor setup and wasnt updating it in the backend it looks like. So now fine and reporting in %/min.
Nice one and good find . Thanks for letting us know, I will keep this in mind if anyone else has the same problem.It is good to know you are up and running.
Yep, I have updated my full set up to now show it all done in the one esp32. It shows you the esp32 I used with all the sensors and parts. I have also shared my code used in the esp32 when used with ESPHome. Click Here to go to my full set up.
PS: In the code I just added a door sensor if you need one. But in this bathroom I am not using one.
@Blacky Fantastic job! I plan on implementing this later this week. I wanted to take a moment and thank you for providing such a detailed and well documented automation blueprint. It is rare to find things like this so well documented.
Hi Janson, thanks for this type of feedback. It is always nice to receive. It is a realy nice automation, one I realy love and it is nice to be able to share it with the community. If you control your lights then check out my sensor light blueprint as they have been designed to work together. If you have any questions, just ask.
As Iâm configuring and testing this blueprint, I noticed that my fan controller (currently a Philips Hue plug in my loft) became unavailable for a short period and this automation was due to turn the fan off while it was unavailable, resulting in the fan not turning off.
Are there any retries or failsafes built in to handle device instability or occasional disconnects, either in the blueprint or in HA. I wasnât sure if HA should automatically keep trying and sync the state of the device when it reappears?
I will obviously look to prevent the device disappearing (itâs actually getting replaced anyway with a zigbee on/off switch connected directly to HAâs zigbee network) but was wondering generally.
You could do a small automation that would be if Philips Hue plug goes from unavailable to ON then turn switch off in X amount of time. Then you would have your safeguard for your fan.
Thanks. Yes I should fix the cause of the dropout but will have a think about that.
Iâm just testing the bypass between this automation and your toilet exhaust fan blueprint. In the toilet exhaust, should the enable bypass be set to turn fan on AND turn fan off? And with the same toggle helper? Or just fan on?
I want to ensure that the humidity trigger overrides the toilet exhaust fan which is triggered by a ceiling light in my en-suite bathroom so the humidity is always controlled.
I can post the config if Iâve not explained myself very well.
Enter your by-pass into âFan Switchâ. Now when the fan is ON the bypass is ON. In the toilet exhaust fan add that by-pass to option 3 of the by-pass.
Remember in the toilet one dont use the âUse The HA Restart Optionâ ⌠make sure it is disabled.
Yep correct, and that is why I have allowed for the input boolean to be added to the âFan Switchâ and the âUse The HA Restart Optionâ is an option in the toilet exhaust as the bathroom humidity has the safeguard
The bathroom humidity you donât use the by-pass option only in the toilet exhaust. The input boolean used as a by-pass (in the toilet exhaust) goes in the bathroom humidity âFan Switchâ
Hmmm, the humidity isnât triggering the fan now - would you be able to cast your eye over my config and see what Iâve got wrong? The light still turns the fan on/off, just humidity isnât triggering it. Should the boolean helper also be off when HA restarts?
Thanks.
alias: En-Suite Humidity Auto Fan
description: ""
use_blueprint:
path: Blackshome/bathroom-humidity-exhaust-fan.yaml
input:
include_lights: lights_disabled
trigger: sensor.en_suite_humidity_derivative
bathroom_humidity_sensor: sensor.ewelink_th01_humidity
include_max_humidity: maximum_humidity_enabled
max_humidity: 95
fan_switch:
entity_id:
- input_boolean.en_suite_bypass_link_en_suite_automation
time_delay: 5
automation_link_time_delay: 10
rising_humidity: 1
falling_humidity: -1
time_out: 30
alias: En-Suite Light Auto Fan
description: Automation to control the En-Suit fan
use_blueprint:
path: Blackshome/toilet-exhaust-fan.yaml
input:
entity_trigger: light.en_suite_ceiling
fan_switch: light.en_suite_fan
trigger_wait_option: fire_on_trigger
trigger_wait_time: 2
time_delay: 1
include_bypass:
- bypass_enabled_stop
bypass_fan_on: []
bypass_fan_off: []
bypass_auto_off_delay: 60
bypass_fan_stop:
- input_boolean.en_suite_bypass_link_en_suite_automation
. Thanks for letting us know, I will keep this in mind if anyone else has the same problem.It is good to know you are up and running.
