šŸŒ” 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