🚽 Toilet Exhaust Fan - Time Delay - Trigger Wait Time - Time

[cemil]

Hi @blacky,

alias: Downstairs Bathroom Exhaust Fan
description: ""
use_blueprint:
  path: Blackshome/toilet-exhaust-fan.yaml
  input:
    entity_trigger: binary_sensor.lumi_lumi_sensor_motion_aq2_motion
    fan_switch: switch.downstairs_bathroom_fan
    time_delay: 1
    include_manual_fan_switch: enable_manual_fan_switch
    manual_fan_switch: switch.downstairs_bathroom_light_fake_switch
    manual_fan_switch_time_delay: 0

YAML there. Also failure condition.

Thank you for helping debug! How can I help?

[Blacky]

@cemil

The ‘switch.downstairs_bathroom_light_fake_switch’, I can’t see if this is set up correctly. Can you copy your light entity ID and replace it with your ‘switch.downstairs_bathroom_light_fake_switch’ in the YAML. Like this.

alias: Downstairs Bathroom Exhaust Fan
description: ""
use_blueprint:
  path: Blackshome/toilet-exhaust-fan.yaml
  input:
    entity_trigger: binary_sensor.lumi_lumi_sensor_motion_aq2_motion
    fan_switch: switch.downstairs_bathroom_fan
    time_delay: 1
    include_manual_fan_switch: enable_manual_fan_switch
    manual_fan_switch: your.light_entity_id_here
    manual_fan_switch_time_delay: 0

@cemil

YAML there. Also failure condition.

Don’t be confused with this trace line as it is the inverted trigger being stopped. When you go into your traces at the top you will see the date and a back / forward arrow. Click on the back arrow to get the correct trace.

Blacky

[cemil]

Sure; will try in about an hr or so. FWIW< here’s the fake switch template:

- platform: template
  switches:
    downstairs_bathroom_light_fake_switch:
      unique_id: "downstairs_bathroom_light_fake_switch"
      value_template: "{{ is_state('light.downstairs_bathroom_light', 'on') }}"
      turn_on:
      turn_off:

[Blacky]

@cemil

You have actions in the but no actions . Try this… it will be better to just input your light as you are not using it as the trigger.

platform: template
switches:
  downstairs_bathroom_light_fake_switch:
    unique_id: "downstairs_bathroom_light_fake_switch"
    value_template: "{{ is_state('light.downstairs_bathroom_light', 'on') }}"

alias: Downstairs Bathroom Exhaust Fan
description: ""
use_blueprint:
  path: Blackshome/toilet-exhaust-fan.yaml
  input:
    entity_trigger: binary_sensor.lumi_lumi_sensor_motion_aq2_motion
    fan_switch: switch.downstairs_bathroom_fan
    time_delay: 1
    include_manual_fan_switch: enable_manual_fan_switch
    manual_fan_switch: light.downstairs_bathroom_light
    manual_fan_switch_time_delay: 0

Blacky

[cemil]

OK! Will do - I think it wouldn’t let me pick a manual_fan_switch through the UI if the domain type was == light.

I figured I didn’t need any actions in there, since we were just using it for state - is that not the case? I thought you were just monitoring for state?

[Blacky]

@cemil

It will not allow you to pick a light domain through the UI but you can edit the YAML and add your light in this blueprint… for that input it will still work. I run filters sometimes so it is easier to pick your entity and I though most people wouldn’t use a light there but it is okay to do so.

@cemil

I figured I didn’t need any actions in there, since we were just using it for state - is that not the case?

Normally when you add these turn on or off actions you have actions. What you can do when developing templates like this is to add your light and you template to the UI then turn the light ON and see what happens to the template. Then if needed you can edit them and see what happens remembering you will have to reload templates every time you edit them. To do this go into developer tools . YAML tab > then select ‘Template Entities’. A HA restart will also do the same thing.

Hope this helps you, let us know how you go.

Blacky

[cemil]

@blacky - sorry it took me a little while to get back to playing with this!

I’m still having the same issue. YAML below.

When I walk into the bathroom, sensor trips, fan comes on. If I then decide I want the light, and turn ON the light, fan stays on. If I then walk out, turn the light off, fan stays on - and never turns off again.

Ideas greatly appreciated!

description: ""
use_blueprint:
  path: Blackshome/toilet-exhaust-fan.yaml
  input:
    entity_trigger: binary_sensor.lumi_lumi_sensor_motion_aq2_motion
    fan_switch: switch.downstairs_bathroom_fan
    time_delay: 1
    include_manual_fan_switch: enable_manual_fan_switch
    manual_fan_switch: light.downstairs_bathroom_light
    manual_fan_switch_time_delay: 0

[Blacky]

@cemil

I have tested it here again trying every option and the fan always turns OFF. Can you check to make sure nothing else it keeping it ON (anther automation).

Blacky

[cemil]

Hi @Blacky ; again, finally got back to testing this, and not seeing ‘expected’ behaviour. I’ve got my master fan down the bottom.

For clarity, there are 2 Shelly relays - a 1pm and a dimmer in there; 1pm runs the fan, dimmer runs the lights. They’re on separate switches. It may be important to note that the presence sensor and switch are both inside the bathroom, so it’s hard to press the light switch without triggering the presence sensor.

Based on the config below, I am definitely seeing unexpected behaviour:

1. If I trip the sensor, fan works - every time. If I don’t touch the light, the fan will go off with the time delay. So far, so good.
2. If I trip the sensor, then turn the light on manually, the fan will eventually go off when the presence sensor stops detecting motion, but so will the light. Example log entry - I’m not sure how the automation is turning off the light, given that I haven’t selected any option.

Master Bathroom Light turned off triggered by automation Master Bathroom Exhaust Fan triggered by state of Master Bathroom Motion Sensor Presence
19:28:09 - 19 hours ago

3. Lastly, if I trip the sensor, then turn the light on manually, then turn the light off manually, the fan will not turn off by itself - requires manual intervention.

What other information can I provide to help troubleshoot?

alias: Master Bathroom Exhaust Fan
description: ""
use_blueprint:
  path: Blackshome/toilet-exhaust-fan.yaml
  input:
    entity_trigger: binary_sensor.master_bathroom_motion_presence
    fan_switch: switch.master_bathroom_fan
    time_delay: 2
    include_manual_fan_switch: enable_manual_fan_switch
    manual_fan_switch: light.master_bathroom_light

[Blacky]

@cemil

Thanks for providing this detail of what is happening including your YAML. It really helps me.

@cemil

If I trip the sensor, fan works - every time. If I don’t touch the light, the fan will go off with the time delay. So far, so good.

Correct

@cemil

If I trip the sensor, then turn the light on manually, the fan will eventually go off when the presence sensor stops detecting motion, but so will the light. Example log entry - I’m not sure how the automation is turning off the light, given that I haven’t selected any option.

Correct

@cemil

Lastly, if I trip the sensor, then turn the light on manually, then turn the light off manually, the fan will not turn off by itself - requires manual intervention.

Not correct

@cemil

What other information can I provide to help troubleshoot?

All is good in the design of the blueprint but it look like you would like a different option / way in how it should work. Please look at removing / disabling the manual light control and use option 1 in the bypass. Then in ‘By-pass Switch - Turn Fan ON’ enter in your ‘light.master_bathroom_light’. The only thing that may happen is when you turn your light OFF the fan may turn OFF instantly if the presence sensor is not detecting motion. I could add a extra input to fix this but let us know if this works for you. Note you could also use the ‘Enable the by-pass auto off - Turn fan ON option’ and set a ‘By-pass Auto OFF - Time Delay’ if the light was left ON accidentally.

Please let us know how you go as I do value feedback.

Blacky

[cemil]

Hi @Blacky ; Thanks for the rapid response mate. What you’ve written makes sense, let me try it.

I may come back with some small wording modifications to documentation / tooltips in that case. Thanks a lot for the help!

[Gartenfreund]

Hi,
I would really like to use the inverted mode in combination with the “trigger wait option”, which is exclusive for the “normal Mode”.
Means that the fan should only be switched on if the trigger wait time has passed and the light is switched off (after leaving).
I haven’t found a solution for this. Does anyone have an idea?

Thanks a lot.

[Blacky]

@Gartenfreund

Firstly welcome to the community

I can see your point. I have updated the blueprint, just doing the final checks and I will release the update. Stay tuned.

Blacky

[Blacky]

New update 2.5

New Features

• Invert Mode - Trigger wait option can now be used in inverted mode.

Maintenance

• Changed to my new layout.

Bugs Fixes

• Fixed bugs in inverted trigger by-pass.

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

[ralph.ralph]

Thank you for a nice set of Blueprints.

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.

[Blacky]

@ralph.ralph

Currently there is no way to turn the fan back ON if the switch is turned OFF.

Blacky

[ralph.ralph]

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?

[Blacky]

New update 2.6

New Feature

• 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

Enjoy

Blacky

[extreme4u]

I am missing a time limit when the light is on. For example, if the light is on and I forget to turn off the light, the fan will never turn off.

[Blacky]

@extreme4u

Thanks for your suggestion… I will put it on the list.

Blacky