This is quite a big update . I am slowly going through my blueprint so they all look and feel the same
Please read this before upgrading. If you use âFan Speed - Switch Off Optionâ in you automations, once you upgrade you will need to select âEnable the fan speed - switch off optionâ as shown below and click save.
Added enable / disable option to the âFan Speed â Switch OFF Optionâ.
Added Fan domain to âFan Speed â Switch OFF Optionâ.
Upgraded by-pass to have 3 options. You can now choose what you would like the fan to do when you turn the by-pass ON.
Turn fan ON.
Turn fan OFF.
Keep the current fan state.
Added the ability to use a âBy-pass Auto OFF Optionâ. This is used when you turn the by-pass ON and you would like the by-pass to automatically turn OFF in a set time delay. It can also be used as a timer to turn the fan ON and then OFF if you have chosen to use âEnable the By-pass - Turn fan ONâ.
Added end of time trigger. The fan will turn OFF when end time crosses over and your âRising Valueâ is over itâs setting.
Added some safe guards for HA restart.
Cleaned up some code.
Bugs Fixes
Start of time trigger.
Some other bugs.
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
Currently the blueprint doesnât have "zoneâ as a condition. I will put this on the list.
If you would like to do this you could set up a template sensor that is OFF when you are âHomeâ. You would then put that sensor in the bypass and select âEnable the By-pass - Turn fan OFFâ. So what would happen is when your are âNot Homeâ or âAwayâ the template sensor would get automaticity turned ON thus turning your bypass ON and the fan OFF when you leave. When you get home the bypass would go OFF allowing the automation to run.
If you need help creating this template sensor then let us know and I will provide you the code.
Below are 2 sensors. One for a individual person and one for the zone. You will need to decide what suits you. If you would like to track multiple persons then you could create all your person sensors and then group them with a helper. The zone one is for any device in a zone you are tracking. You then would enter this code into your âconfiguration.yamlâ file and restart home assistant. You will then have the new sensor you can enter into the by-pass.
Things you can change to your liking are;
ceiling_fan_zone_person_blacky_sensor - (The name must be unique and be in lower case and if you would like a space then it must be â_â. This is the entity ID of your sensor)
Ceiling Fan Zone - Blacky Home Sensor
presence
mdi:map-marker-account-outline
ceiling_fan_zone_sensor - (The name must be unique and be in lower case and if you would like a space then it must be â_â. This is the entity ID of your sensor)
Ceiling Fan Zone - Home Sensor
Things you must change (entity name) or check the zone you have
device_tracker.blacky_iphone
âhomeâ - you may have a different zone name other than âhomeâ
zone.home
This is for a person.
binary_sensor:
- platform: template
sensors:
ceiling_fan_zone_person_blacky_sensor:
friendly_name: "Ceiling Fan Zone - Blacky Home Sensor"
device_class: presence
icon_template: mdi:map-marker-account-outline
value_template: >-
{% if states('device_tracker.blacky_iphone', 'home') %}
off
{% else %}
on
{% endif %}
This is for a zone.
binary_sensor:
- platform: template
sensors:
ceiling_fan_zone_sensor:
friendly_name: "Ceiling Fan Zone - Home Sensor"
device_class: presence
icon_template: mdi:map-marker-account-outline
value_template: >-
{% if states('zone.home')|float > 0 %}
off
{% else %}
on
{% endif %}
You could have both, so if a bedroom for âblackyâ has a ceiling fan and when blacky is home the fan will work. You could have another bedroom that is for a different person so you would add another sensor in for that person. But you could have ceiling fans in kitchen then you could use zone or a group helper with all your person sensors selected. You would then use the correct sensor for the automation.
This is using both sensors together. NOTE: We only need one âbinary_sensor:â header.
binary_sensor:
- platform: template
sensors:
ceiling_fan_zone_person_blacky_sensor:
friendly_name: "Ceiling Fan Zone - Blacky Home Sensor"
device_class: presence
icon_template: mdi:map-marker-account-outline
value_template: >-
{% if states('device_tracker.blacky_iphone', 'home') %}
off
{% else %}
on
{% endif %}
- platform: template
sensors:
ceiling_fan_zone_sensor:
friendly_name: "Ceiling Fan Zone - Home Sensor"
device_class: presence
icon_template: mdi:map-marker-account-outline
value_template: >-
{% if states('zone.home')|float > 0 %}
off
{% else %}
on
{% endif %}
Just a heads up if your still on a old HA version before you update.
From time to time Home Assistant update their code structure and the old code will become âDEPRECATEDâ stopping / breaking automations from working. It effected this blueprint about 4 to 6 months ago. I wanted to wait some time so everyone had a chance to update their HA version before updating the code as older HA versions can not run the new code. This blueprint has now been updated so it will still operate once HA remove the âDEPRECATEDâ code from their system.
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
How do I set it that when the FAN goes on when passing a value⌠then normally it should go off when below a value. Sometimes it takes too long and would like it to turn off after 45min if it didnât get below that value.
Could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on â</>â and paste code in there.
Hi - this seems to be exactly what iâve been after and as similar posts have suggested I am using it to trigger heating on/off. Thankyou!!
I do seem to be having issue after my initial testing. If I manually run the blueprint it works as expected.
How frequently does it run, or pull data before a decision is made? Or do I need to something else with this? As it does not yet seem to be âautomatedâ For info I have enabled time options and during testing they are within the range.
Could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on â</>â and paste code in there.
I have the same problem - I would like to run a script rather than operate a switch but only switch entities show up. HA version up to date.
Iâve tried editing the input code under domain to add â-scriptâ but that doesnât seem to work - and I have to admit I have no idea what I an doing.
Any help?
. I am slowly going through my blueprint so they all look and feel the same 
Please read this before upgrading. If you use âFan Speed - Switch Off Optionâ in you automations, once you upgrade you will need to select âEnable the fan speed - switch off optionâ as shown below and click save.
button in the top post 
