🌡 Temperature Control Fan + Ceiling Fan Mode

Blueprints Exchange
, , , ,
103

Here is previous configuration I was using. It seams obvious why this one is not working as I’m forcing a greater than 100% input.

alias: Bedroom Fan Auto Control
description: ""
use_blueprint:
  path: Blackshome/temperature-control-fan.yaml
  input:
    trigger_sensor: sensor.master_bedroom_temperature_temperature
    auto_mode_entity: input_boolean.bedroom_fan_auto
    fan_mode: ceiling_fan
    fan_high_speed: []
    fan_medium_speed: []
    fan_low_speed: []
    fan_off: []
    falling_temp: 67
    medium_speed_temp: 72
    high_speed_temp: 78
    ceiling_fan_control_mode: fan_percentage
    ceiling_fan_entities:
      entity_id: fan.bedroom_fan_fan
    ceiling_fan_max_temp: 72
    ceiling_fan_max_pct: 255
    ceiling_fan_min_pct: 64
    ceiling_fan_step_value: 64
    ceiling_fan_dead_zone: 1

After starting to write this, I did some clean up and ended up with this, which as far as I can tell appears to actually be working correctly. (not fully tested yet)

alias: Bedroom Fan Auto Control
description: ""
use_blueprint:
  path: Blackshome/temperature-control-fan.yaml
  input:
    trigger_sensor: sensor.master_bedroom_temperature_temperature
    auto_mode_entity: input_boolean.bedroom_fan_auto
    fan_mode: ceiling_fan
    falling_temp: 68
    medium_speed_temp: 72
    high_speed_temp: 78
    ceiling_fan_control_mode: fan_percentage
    ceiling_fan_entities:
      entity_id: fan.bedroom_fan_fan
    ceiling_fan_max_temp: 78
    ceiling_fan_max_pct: 100
    ceiling_fan_min_pct: 33
    ceiling_fan_step_value: 33
    ceiling_fan_dead_zone: 1
    rising_temp: 70

Developer tools showed the following for the fan I was controlling:

fan_dev_tools
fan_dev_tools922×130 10.4 KB

And finally the device log, which apparently was just screwing me up. The homekit commands make sense for using a percentage, but the level 128 was confusing me.

fan_logbook
fan_logbook314×462 21.1 KB

Short of it is, it may be working correctly now.

104

@Jpeg6

Looks like you found it, nice one… glad you got it working.

Blacky :grinning:

105

@Blacky
I don’t understanding the difference between the “Auto Mode Control Entity” and the “Trigger Sensor By-pass” options. Let’s assume a helper control is added for use with the “Auto Mode Control Entity”. When this helper is turned off, the fan wouldn’t automatically start. In other words the temperature sensor is disabled or bypassed.

What’s the purpose of the “Trigger Sensor By-pass” if the “Auto Mode Control Entity” is already in use?

106

@rcblackwell

Auto Mode Control Entity is basically an Auto / Manual switch. When in Auto Mode the automation can run. Or it is just enable or disable.

Trigger Sensor By-pass Option When in auto mode you can then decide to turn the fan ON / OFF / Keep the current state. You may want to force it into one of these states and maybe another automation controls it. Just gives you more advance options.

Blacky :grinning:

107

I’m still confused!

Let’s assume the fan is running and the “Auto Mode Control” is set to Auto. Now lets use the “Trigger Sensor By-pass” in an automation to turn the fan off. Won’t the fan turn on again the next time the “Heartbeat” triggers?

108

@rcblackwell

No, maybe think of it as enabled or disabled. Because it is a ceiling fan type of blueprint I wanted a toggle in the UI to turn ON auto mode. This way in summer we can choose when we would like the fans to run. If you have an A/C and you turn it ON you can use the bypass to stop the ceiling fans even if it is in auto mode. Then when you turn the A/C OFF your ceiling fans will work.

Blacky :grinning:

109

Thanks. The example helped.

1 Like
110

@Blacky Is there any provision or hacky way to use this with IR fans? My IR fan takes speed input from 1 to 5 which I can fire with broadlink IR blaster, but the blueprint can’t take this as ‘remote’ is not a fan entity in HA.
Any thoughts or clue?

111

@pranjal-joshi

You will have to get the speeds into HA. The blueprint can control 3 speeds., Once you can get HA to see the speeds then you can control them.

Blacky :grinning:

112

Thanks @Blacky

I was able to use SmartIR integration that maps IR blaster based devices as fan and now I can see this blueprint is firing IR blaster to adjust the fan speed.

113

@pranjal-joshi

Nice one, thanks for letting us know.

Enjoy

Blacky :grinning:

114

Any way to get this to trigger based on a room’s humidity?

115

@Dr.proctor

Yes, just think of temp as humidity.

Blacky :grinning:

116

I have to ceiling fans, they are almost the same. Both integrated via localtuya. The behavior tends to differ between both.

One of them is working perfect with this blueprint, but the other doesn’t switch on when only using fan.set_percentage, it needs also a fan.turn_on action.

So I added this in the sequence at “Set fan percentage when first turn ON”:

                    - service: fan.turn_on
                      target:
                        entity_id: "{{ pct_control_ceiling_fan }}"

and now all works fine. I also tested this with the other fan and this also still works. Could you be so kind to implement this you blueprint?

117

Hi,

Wanted to use this blueprint to trigger a fan (via a philips hue plug) to switch on/off depending upon temperature. However, Philips Hue plug neither appears in list of devices or entities. Is there a reason for this?

Steve

118

Hello stevencavanagh,

Because your switch is a switch, and it needs something in the fan domain to work, possibly?

This might help.

119

Cheers, I will take a look!

Steve

120

When I try to create a helper to change type I get an error as the entity is showing as a light, which sort of makes sense as it is a Philips Hue plug but it won’t allow the helper to be created unfortunately.

121

I will PM you.

Blacky :grinning:

122

@stevencavanagh

What option are you using?

First can you copy and paste your Philips Hue pug into the input and see if that works.

If not

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.

Blacky :grinning: