🌔 Temperature Control Fan + Ceiling Fan Mode

Hi,

Firstly, copying the entity and pasting allows me to run the actions ok!

However, waiting to get to the required temperature to trigger the automation (ie, rising) to prove it all works. I have attached the YAML as requested. What I would like to know is if there is a way to trigger the automation automatically if the temperature is already above rising temperature. Ie. If the rising is set at 50 DegC and the current temp. is 60 DegC as it currently doesn’t.

alias: Loft Fan Control
description: ""
use_blueprint:
  path: Blackshome/temperature-control-fan.yaml
  input:
    trigger_sensor: sensor.synology_nas_temperature_group
    rising_temp: 62
    falling_temp: 50
    auto_mode_entity: input_boolean.loft_fan_auto_status
    fan_switch:
      entity_id: light.hue_smart_plug_1

@stevencavanagh

Try toggling the Auto Mode Control Entity.

Blacky :grinning:

Yep, that did it!

Cheers
Steve

1 Like

This is a great automation thanks for your hard work!
I have a request to add a secondary sensor (possibly a third?) so that I can better control the fan running over quite a long shadehouse structure.

Would that be possible or even something you would consider?

Thanks!

@wellsy

Thanks for your kind words.

I really appreciate all suggestions, they’re always welcome! Before anything else though, it helps to clearly understand what the idea is. I’ve been able to add quite a few great suggestions already, and while I may not be able to include everything, I always take the time to consider it.

Sometimes there’s even a way to achieve it with the current blueprint setup.

Blacky :grinning:

Impressed with your speedy reply Blacky!
The shadehouse I am trying to moderate the temperature in is around 15m long and also has varying shade strength from end to end.
I have a number of fans within the structure and starting to automate them just now. The first fan is an evaporative cooler type which provides cool air movement up the full length on one side. Ideally I would like to be able to control on an average of 2-3 sensors placed along the 15m length. Once this fan is working well I plan to control a second fan which assists the flow of air return down the other side of the shadehouse with another 2-3 sensors also averaged. That would use a second instance of your automation.

Cheers and I hope that may help clear up what I’m looking for?
Let me know if more info required.

Regards Steve

@wellsy

Okay, so you would like the average of 2, 3 + sensors and then work with the average.

Will a sensor group work?

Go to:

  • Settings > Devices & Services > Helpers > Create Helper > Group > Sensor Group
  • Give it a name like: North Side Temp Group
  • Under Members, add all your temp sensors you would like to use.
  • For Type, choose: Arithmetic mean to give the average. (sensor 1 + sensor 2 = ? div by 2 = your average)

You then use that group.

Will that work?

Blacky :grinning:

1 Like

I had no idea that was possible in Helpers I am sad to say.
I am sure that would work and confirm once implemented.

Thanks very much

Update: Yes that works wonderfully as you would expect. Cheers!

@wellsy

In Home Assistant, there’s so much you can do, it really lets you create just about anything you can imagine, and that’s the beauty of it. Unlike many other smart home hubs, Home Assistant gives you the freedom to shape things exactly how you want, local and private, and that’s why I truly love it.

When you get a chance, take a look at all the helpers, they’re incredibly powerful and can really take your automations to the next level.

Glad it worked out the way you wanted it… enjoy!

Blacky :grinning:

1 Like

I’m not sure what I am doing wrong. Zigbee Temp/Humid sensor and a Switch Entity being my fans for my homelab.

My Rising temperature is set to 30 degrees, falling 25. (I’m aware that my ambient temp is 30 degrees at the moment) I’ve set up a boolean entity to enable to automation but it’s not turning on my fans despitre the temp. I imagine I have not set something obvious but I can’t tell what.

@TehH4rRy

Welcome to the community.

I cant see what you done but Cif you like you can 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.

For the automation to trigger it must go from below 30 to above 30. If it is just 30 then if you toggle your boolean entity from OFF to ON it will also trigger.

Blacky :grinning:

Ahh I get it now. The temperature is already at 30 or above when it’s running so that makes sense why it’s not kicking in. I appreciate the quick reply! Thanks man.

No problem, your welcome.

Blacky :grinning:

Using this blueprint, I’ve got my bedroom fan to come on when the temperature is over 22°c and after 19:00. I’d like to add a pressure sensor as a switch so the fan only comes on when all three conditions are met (temp, time, sensor)

How would I go about this?

Cheers

@stalker79

The fan works of temp. If you would like to make all these conditions then you would do that to toggle the Auto Mode Control Entity.

Blacky :grinning:

1 Like

New update 2.0

Fan-tastic Fan Control: The Ultimate Fan Control for Optimal Temperature Regulation. :wind_face::chart_with_downwards_trend:

:bug: Bug Fixes

  • Fixed a bug when turning on a Percentage Fan. Some fans would not turn on depending on your fan type.

Maintenance :toolbox:

  • From time to time, Home Assistant updates their YAML standards and coding practices. To align with their roadmap, we’ve updated the code accordingly. We will continue to apply these updates across all our blueprints as they are revised.

If you like this blueprint? Consider hitting the :heart: button in the top post :+1:

If you like my blueprints, and would like to show your support or just say thank you? Click Here :smiling_face_with_three_hearts:

Enjoy

Blacky :grinning:

Error: ZeroDivisionError: float division by zero

I have two RF remote ceiling fans controlled by the Bond Bridge. They work fine from Home Assistant. The Bond Bridge sets the speed via percentage, but the HA cards show preset buttons.

This blueprint only works for me in Three Speed Fan Mode and then, it only turns the fan on or off at the last speed (since there aren’t selectable entities for each speed). I’ve updated to 2.0 with no changes.

Enabling Fan Percentage in the automation always results in a ZeroDivisionError and it happens on the last decision step, then again in the Percentage Fan section.

What setting is causing this? (The temperatures are test values I was using and not indicative of reality.)

Thanks in advance!

alias: Temperature Control Fan - Master Bedroom
description: ""
use_blueprint:
  path: Blackshome/temperature-control-fan.yaml
  input:
    trigger_sensor: sensor.third_reality_inc_3rths24bz_temperature
    fan_mode: ceiling_fan
    fan_high_speed: []
    fan_medium_speed: []
    fan_low_speed: []
    fan_off: []
    rising_temp: 70
    falling_temp: 67.5
    medium_speed_temp: 69.5
    high_speed_temp: 76
    ceiling_fan_max_temp: 96.5
    preset_medium_speed_temp: 80
    preset_high_speed_temp: 83
    ceiling_fan_max_pct: 100
    ceiling_fan_min_pct: 33
    three_speed_dead_zone: 0.5
    three_speed_heartbeat: 1
    preset_dead_zone: 0.5
    preset_heartbeat: 1
    ceiling_fan_control_mode: fan_percentage
    ceiling_fan_heartbeat: 0.5
    ceiling_fan_step_value: 5
    ceiling_fan_dead_zone: 7
    auto_mode_entity: input_boolean.master_bedroom_ceiling_fan_control_enable
    ceiling_fan_entities:
      device_id: 6593.....2da

@jcreagerlv

Your using a device in Fan Controlled By A Percentage Value you can only use entity. This is a link to a FAQ of my sensor light blueprint but it shows you how to expand down to an entity click here

Blacky :grinning: