This is awesome! It would be great if this worked with ceiling fans as well.
Is your ceiling fan a switch?
Blacky 
It looks like the entity is of type “fan”.
On a separate note, I am testing your blueprint on a light. It works fine except when I disconnected the occupancy sensor from the network. When I manually turn the light on, it immediately shuts off. I will add that for testing I had set the timer to 1s.
Okay, maybe I should update it so a switch can be anything (any domain other than a light).
Your best to use the bypass for manual control.
Blacky
Can this be time based so from 5pm to 10 pm lights stay on for 10 min and 10:01 pm until next day 4:59 PM lights stay on for 5 min.
Since I only have a door binary sensor that is Open or closed I changed these settings to accommodate resting the helper timer when the door is re-opened. I have Kasa motion sensors and they dont allow for HA to see motion status.
420 - alias: Ceck if the timer is idle
conditions:
- condition: state
entity_id: !input timer_helper
state: Closed
449 - alias: Ceck if the timer is idle
conditions:
- condition: state
entity_id: !input timer_helper
state: Closed
Thanks. Im a bit confused by the response to the second item since the point of your blueprint is to allow for manual control with auto off. What I’m seeing is that when the proximity sensor is offline, the blueprint shuts the light off. I would hope that it would do the opposite and not shut the light off and only return to normal operation when the sensor is back online.
Currently there is only one time delay. You may be asking that when you open and close the door you would like it ON for 10 min or 5 min depending on time. If this is the case then have a look at my sensor light blueprint and you can use night lights with a different time delay.
Blacky
Just a quick note. If you don’t use the timer then delay will be used and in the top post it gives you examples on how it handles a HA restart.
Day/time is not to be confused with delay or timer. It is not the same. Day/time is exactly that… set day/time. Delay or timer is not exact day/time. This blueprint can be triggered at any point and when it turns OFF is not a exact day/time.
FYI: Below are 2 examples for day/time v timer. There are many ways to handle this in your automation code it just depends on what option you choose. No way is wright or wrong.
Day/time = If you have X running for 3 hours and 20 sec before it is about to turn OFF you restart HA. At that point you are using a day/time trigger to turn it OFF. HA takes 30 sec to restart and your time/day trigger has been missed. It will not turn X OFF.
Timer = If you have X running for 3 hours and 20 sec before it is about to turn OFF you restart HA. HA takes 30 sec to restart and your timer resumes after the 30 sec and start the 20 sec left on the timer and turns X OFF. Yes it ran for an extra 30 sec but it is OFF.
Again you can make anything work it just depends on your code and what you would like to do. You could make day/time work in the above scenario but you will need the code to handle that. This blueprint needs delay or timer as it is not a fixed day/time. It triggered from the time you turn the light or switch ON.
Hope this gives you a better understanding.
Blacky
Another pretty cool BP 
Thank you!
1 Like
Hi - thank you for this BP…
I have three separate bathroom fans that I’d like to turn off after 35 minutes. Does each fan need it’s own BP and Timer helper? At least from my initial testing, it seems the timer restarts when another device gets turned on.
Short answer is , Yes but it is optional to use a timer.
Have you looked at my other 2 blueprints.
Toilet Exhaust Fan with time delay
Bathroom Humidity Exhaust Fan
Blacky
Thanks @Blacky - just looked at that…
I might still need this one. Basically, in my bathroom, I have a power switch for the bidet. If the switch is turned on, I want the fan turned on. Ideally, the bidet would turn off after 25 minutes, and the fan would turn off after 35 minutes.
I have a basic automation working right now (without a blueprint), it just doesn’t survive a reboot.
You can do this with the toilet exhaust BP. You would use the power switch for the trigger, use normal mode, enter in your fan and the time delay. The bidet turning off after 25 min I am keen to know more about this as it makes total sense to have it work with a bidet. If you would like to PM me and give me what happens and how it all works we can go through it together.
Blacky
Hi @Blacky Thank you for your work and reply on this.
It’s actually very simple. My bidet is a power bidet with heated seat and heated water. While it as a “sleep” mode - it’s not perfect.
So basically - someone comes into the bathroom to handle their toilet business, and pushes the button that turns on the bidet’s outlet. But oops, forgot to turn on the fan.
Right now, my very basic automation sees that, and says, here comes smelly stuff, so fan ON. Then the bidet outlet turns off in 25 minutes, and the fan turns off in 35 minutes.
Of course this doesn’t survive a reboot so, the fan or bidet stays on.
Thanks for the info… I am going to look into this more but what I would do is use the Toilet Exhaust Fan with time delay BP. Use the push button as the trigger (may need to do something here but you need an ON state), use normal mode, don’t use the wait time, enter in your fan and set the delay time to 5 min.
What I do it have a Shelly on my light in the toilet so I can see if it is ON or OFF (that is all the Shelly does, we still use manual control) and then I use the light as the trigger, normal mode, use the wait time and set it to 2 min, enter in the fan and time delay of 4 min, Use time from 8am till 10 pm every day. Everyone loves it.
Blacky
Hi Blacky,i like your work. Are you interested in taking up part-time job of setting up my smart home using HAOS. Please reply to me on email [email protected].
Thank you.
Vikram
Thanks for your consideration but sorry I will have to pass. It is quite easy to do and there is a lot of help on this forum with many people will to help.
Thanks again.
Blacky
Noted
1 Like