Advanced Ventilation/AC Management Blueprint

[Lyntoo]

Advanced Ventilation/AC Management Blueprint

Click here to import directly into Home Assistant:

Celcius

Fahrenheit

Overview

This Home Assistant blueprint provides intelligent control of fans and air conditioners based on indoor temperature, outdoor conditions, forecasted heatwaves, and window/door sensor status. The system automatically adjusts cooling devices to maintain optimal comfort while being energy-efficient and responsive to environmental conditions.

Key Features

Multi-Device Support

Controls various types of fans and AC units with graduated response levels

Weather Integration

Proactive cooling based on heatwave predictions from weather forecasts

Smart Energy Saving

Window/door awareness prevents energy waste when openings are detected

Intelligent Thresholds

Different cooling levels based on temperature with hysteresis control

Supported Devices

Fan Types (All Optional)

• On/Off Fan: Simple switch-controlled fans (exhaust fans, basic fans)
• Ceiling Fan: Variable speed control with percentage-based speeds (25%, 50%, 75%, 100%)

AC Types (All Optional)

• Portable AC 1 (Advanced): Full fan mode options (silent, low, medium, high, full, Auto)
• Portable AC 2 (Basic): Limited fan modes (auto, low, medium, high)

Configuration Parameters

Parameter	Default	Description
Fan Start Threshold	24.0°C	Indoor temperature to start fans
Fan Stop Threshold	22.0°C	Indoor temperature to stop fans
AC High Temperature	26.0°C	Temperature for AC high cooling mode
AC Heatwave Threshold	22.0°C	AC activation temp during heatwave
Max Outdoor Temp for Ventilation	25.0°C	Maximum outdoor temp to allow ventilation
Heatwave Forecast Threshold	30.0°C	Forecasted temp triggering heatwave mode

Decision Tree Logic

TRIGGER EVENT
├── Indoor temperature change
├── Outdoor temperature change
├── Weather forecast update
└── Window/door sensor state change
▼
INITIAL VALIDATION
├── Check if automation entity is available
├── Verify sensor states are not ‘unavailable’ or ‘unknown’
└── Continue if all checks pass
▼
VARIABLE CALCULATION
├── current_room_temp = Indoor temperature sensor value
├── current_outdoor_temp = Outdoor temperature sensor value (or default)
├── is_heatwave = Check if forecasted temp ≥ heatwave threshold
└── is_window_open = Window/door sensor state
▼
ON/OFF FAN CONTROL (if configured)
├── IF current_room_temp ≥ fan_start_threshold (24°C)
│ AND current_outdoor_temp ≤ max_outdoor_temp (25°C)
│ └── ACTION: Turn ON fan
└── IF current_room_temp < fan_stop_threshold (22°C)
│ └── ACTION: Turn OFF fan
▼
CEILING FAN CONTROL (if configured)
├── IF current_room_temp > (ac_high_threshold + 2°C) [>28°C]
│ └── ACTION: Set speed to 100% (Maximum cooling)
├── IF current_room_temp > ac_high_threshold [>26°C]
│ └── ACTION: Set speed to 75% (High cooling)
├── IF current_room_temp > (ac_high_threshold - 2°C) [>24°C]
│ └── ACTION: Set speed to 50% (Medium cooling)
├── IF current_room_temp > (ac_high_threshold - 4°C) [>22°C]
│ └── ACTION: Set speed to 25% (Low cooling)
└── IF current_room_temp < fan_stop_threshold [<22°C]
│ └── ACTION: Turn OFF ceiling fan
▼
PORTABLE AC CONTROL (AC1 & AC2 - if configured)
│
├── WINDOW/DOOR CHECK
│ ├── IF is_window_open = TRUE AND turn_off_ac_on_window_open = TRUE
│ │ └── ACTION: Turn OFF AC immediately
│ │ └── REASON: Prevent energy waste with open window
│ │
│ └── IF is_window_open = FALSE
│ └── PROCEED TO TEMPERATURE CONTROL
│
└── TEMPERATURE-BASED AC CONTROL
│
├── HEATWAVE MODE (Priority)
│ ├── IF is_heatwave = TRUE AND current_room_temp heatwave_threshold (22°C)
│ │ └── ACTION: Set HVAC mode = ‘cool’, Fan mode = ‘medium’
│ │ └── REASON: Proactive cooling during forecasted heatwave
│
├── EXTREME HEAT MODE
│ ├── IF current_room_temp > (ac_high_threshold + 2°C) [>28°C]
│ │ └── ACTION: Set HVAC mode = ‘cool’, Fan mode = ‘Full’ (AC1) / ‘high’ (AC2)
│ │ └── REASON: Maximum cooling power for extreme temperatures
│
├── HIGH HEAT MODE
│ ├── IF current_room_temp > ac_high_threshold [>26°C]
│ │ └── ACTION: Set HVAC mode = ‘cool’, Fan mode = ‘high’
│ │ └── REASON: Strong cooling for high temperatures
│
├── MODERATE HEAT MODE
│ ├── IF current_room_temp > (ac_high_threshold - 1°C) [>25°C]
│ │ └── ACTION: Set HVAC mode = ‘cool’, Fan mode = ‘medium’
│ │ └── REASON: Moderate cooling for warm temperatures
│
├── MILD HEAT MODE
│ ├── IF current_room_temp > (ac_high_threshold - 2°C) [>24°C]
│ │ └── ACTION: Set HVAC mode = ‘cool’, Fan mode = ‘low’
│ │ └── REASON: Gentle cooling for mildly warm temperatures
│
├── FAN-ONLY MODE
│ ├── IF current_room_temp ≤ (ac_high_threshold - 3°C) [≤23°C]
│ │ AND current_room_temp > fan_stop_threshold [>22°C]
│ │ └── ACTION: Set HVAC mode = ‘fan_only’, Fan mode = ‘Auto’
│ │ └── REASON: Air circulation without cooling
│
└── OFF MODE
└── IF current_room_temp < fan_stop_threshold [<22°C]
└── ACTION: Turn OFF AC
└── REASON: Comfortable temperature reached

Example Scenarios

Scenario 1: Normal Day
Indoor: 25°C, Outdoor: 23°C, No heatwave
Result: Ceiling fan at 50%, AC in cool mode with medium fan

Scenario 2: Heatwave Predicted
Indoor: 23°C, Outdoor: 35°C forecast, Heatwave detected
Result: AC activates proactively in cool mode with medium fan

Scenario 3: Window Open
Indoor: 27°C, Window sensor: Open
Result: AC turns off immediately (if configured), fans continue

Scenario 4: Cool Evening
Indoor: 21°C, Outdoor: 18°C
Result: All devices turn off, comfortable temperature achieved

Setup Recommendations

Basic Setup (Minimal Configuration)

1. Configure room temperature sensor
2. Set fan start/stop thresholds based on comfort
3. Add one cooling device (fan or AC)

Advanced Setup (Full Features)

1. Configure all relevant devices
2. Set up outdoor temperature sensor
3. Configure weather forecast integration
4. Add window/door sensors for energy efficiency
5. Fine-tune all temperature thresholds

Configuration Tips:
• Fan thresholds: Start 1-2°C above your comfort temperature
• AC thresholds: Set 2-4°C above fan start threshold
• Heatwave threshold: Set 2-4°C below normal AC threshold
• Ensure stop thresholds are lower than start thresholds to prevent cycling

Troubleshooting

Common Issues

• Devices not responding: Verify entity IDs are correct and devices are available
• Rapid cycling: Ensure stop thresholds are lower than start thresholds
• AC not starting: Check window sensor status and outdoor temperature limits
• Weather integration not working: Verify weather entity provides forecast data

Testing Tips

• Use Home Assistant’s automation trace feature to debug logic
• Monitor entity states during temperature changes
• Test window sensor integration by manually opening/closing windows

Smart Features

Heatwave Detection

Uses weather forecast entity to predict high temperatures and proactively activates AC at lower indoor temperature (22°C vs 26°C) to maintain comfort before extreme heat arrives.

Window/Door Integration

Monitors window/door sensors to prevent energy waste with configurable behavior: immediate AC shutdown or prevent startup only.

Hysteresis Control

Different thresholds for starting (24°C) and stopping (22°C) devices prevents rapid on/off cycling and ensures stable operation.

Multi-Zone Logic

Considers both indoor and outdoor temperatures to prevent inefficient ventilation when outdoor air is too hot, optimizing energy usage based on conditions.

Compatibility

Supported Integrations

• Climate entities: Any Home Assistant climate integration
• Fan entities: Standard fan platforms with percentage control
• Weather entities: Most weather integrations with forecast data
• Binary sensors: Standard door/window sensors

Device Requirements

• Temperature sensors: Must report in Celsius with numeric values
• Climate devices: Must support hvac_mode and fan_mode services
• Fan devices: Must support percentage control or dimmer functionality

Ready to install? Click here:

Celcius

Fahrenheit

This blueprint ensures optimal comfort while maximizing energy efficiency through intelligent automation. Perfect for those who want a comprehensive climate control solution that adapts to both current conditions and weather predictions!

[PeL4]

I will try it out.
I suppose it works for cold weather too right? It’s winter where I live

[Lyntoo]

@PeL4

I suppose it works for cold weather too right? It’s winter where I live

The blueprint is based on heat control with climate entities, designed to cool the living space, but I might adapt it to activate the heating in the opposite situation or perhaps create another blueprint. You can download it and modify it as you wish, such as submitting it to artificial intelligence to make changes. In the current blueprint, all temperatures are adjustable.

[Lyntoo]

Note to myself for next release:
add Fahrenheit Celsius selection
add multiple selector for door/windows sensor
fine tune hysteresis and add settings threshold

[stephanschleichstr13]

Time Plans via helper are missing

z.b. 13-20 o’clock

[Lyntoo]

@stephanschleichstr13

Time Plans via helper are missing

The blueprint automation is designed to be as universal as possible and focus on intelligent heat management in the home to have a certain consistency. Schedule management is not considered since there are several easy ways to manage automation according to calendars, timers, presence, etc. enable disable automation. You can freely modify the blueprint if you want to add options, a wonderful function which is “take control” of the bluerpint thus having it as a normal automation easy to adapt to what you are looking for. I saw this option too customizable and different from one taste to another.

[FrankTub (Frank Tubbing)]

Thank you for an awesome blueprint. I will definitely take a look at the blueprint and try it out.

I’m still a bit unsure how I would like to make my AC’s smart and one of my considerations are that I perhaps only want an automation to turn on automatically the AC’s when I have excessive solar power. But I don’t want such an automation to turn off my AC when I manually (HA Lovelace or remote) turn on my AC. Any thoughts on this?

[Lyntoo]

You could create a toggle helper (device create helper) choose toggle, then create a simple automation If the toggle creates example (auto-manual) enable or disable the automation depending on what you want to do.

[FrankTub (Frank Tubbing)]

@Lyntoo, I was trying to figure out how to configure one of my devices using this blueprint and was looking at the blueprint code what it was doing. One of the things I noted was the way you handle the fan mode which I think is really relevant depending on the differences between the outside temperature and the room temperature. In the code you set fan modes like low or high. When I look at my device I guess that is not going to work.

Looking at the docs I guess it really depends on the implementation of the manufacturer of your AC what these fan modes look like (Melcloud in my case). That makes it probably a bit more challenging to create a blueprint that fits all needs.

The other thing I was not really sure on filling out the blueprint is in what is really needed if you for example only want to make sure that the AC start’s cooling when it is too hot for your liking. I was looking at this part:

But I guess the naming of these enitities remain a bit unclear to me. I guess it should be one of the last two, but I’m not sure yet.

And one of the other things I was thinking about is what temperature should the climate be changed to? Does it depend on difference between outside temp and indoor temp or something else?

[Lyntoo]

Hello, thanks for the feedback, when I get back from vacation I will try to add the ventilation level of your air conditioner as another option, the outside temperature is used to anticipate the heat wave and start the air conditioning in advance.

[CommanderROR]

This is a pretty cool Blueprint! I already have my AC automations set to my preferences, so I probably won’t use it, but it’s a pretty neat Template for those just getting started on Automating their Hvac and Ventilation!

[JosepXavier]

Good job, it does what it says. I have this problem. My AC is “Auto,” not “auto.” Can I fix it somehow? Sorry for my writing, it’s translated by Google.

Error while executing automation automation.ventilacion_avanzada: Fan mode Auto is not valid. Valid fan modes are: auto, low, medium low, medium, medium high, high

I support the option of adding a start and end time. I’m not always home.

[Lyntoo]

Thanks for the feedback, the Auto for auto can be easily fixed in the yaml, I will fix it soon in a new release (add multiple attribute name situation) and let you know in a comment on the main publication, I will validate that the attribute name change does not affect other users. In the meantime you can manually edit the yaml and modify them if you wish.

[Lyntoo]

Add Climate entity for an AC with numbered fan modes (auto, 1, 2, 3, 4, 5)
Fixed fan_mode attribute name error: “Auto” to “auto”
Same download link, top and bottom page overwrite blueprint,

For those who would like to add timers, schedules, and device tracker for enable and disable, the links below are considered beta. If you want to give me feedback, and if desired, I will replace it with the official link. the following link does not overwrite the main page blueprint, it creates a new one

Celcius

Fahrenheit

[JosepXavier]

Good morning, thank you for these new options. I’m willing to try them out. When installing, I get the following error:

Message malformed: Entity is neither a valid entity ID nor a valid UUID for dictionary value @ data[‘entity_id’].

Sorry if it’s my mistake, I’m new to HomeAssistant.

[JosepXavier]

Positions to create new options, it would also be interesting to add days of the week

[Lyntoo]

This is a programming error, the automation expects to have a valid or non-null entity value. I will look into this as soon as I have some free time at home and make more simulation before posting.

[Lyntoo]

Same beta link direct download with fix, no entity ID error from my side, don’t enable option with nothing select in the box or the error will apear.

[JosepXavier]

Good morning, I’ve installed the new version and am testing it.
Currently, if we start the blueprint after the start time has passed, it works correctly, but if the time rule is after the start time of the blueprint, it won’t start. It also does not stop at the indicated time.

Good afternoon, if “Outdoor Temperature Sensor (Optional)” is left blank, it gives an error. I’ll keep trying.

[JosepXavier]

Good morning,
I have already seen, because it does not start at the scheduled time. Although there are shots through the sensors, the scheduled time does not start until the time, the problem is that there is a new shot by the sensors, today for example has spent 45 minutes until it has shot again, despite the fact that the temperatures exceeded and with much those established for the shot. I guess the same thing happens with the final time option, since I have to manually deactivate the rule. If there is something that does not express me correctly, tell me, thanks