[Blueprint] Auto Resolve "Heat/Cool" Mode by Season - for A/C Units Without Remote Control

Blueprints Exchange
1

[Blueprint] Auto Resolve “Heat/Cool” Mode by Season – for A/C Units Without Remote Control

When an A/C unit (or any climate entity) switches itself into "heat_cool" mode, this blueprint automatically sets it to heat in colder months and cool in warmer months - and applies your preferred target temperatures.
Tested on Daikin A/C with Faikin controller, but it should work with any climate device that exposes the climate.* entity and supports the heat_cool mode.

Why I Created This

We currently don’t have remotes for our A/C units, so we’re turning them on using the physical buttons on the indoor units.
When pressed, the unit always starts in "heat_cool" mode with a fixed 25 °C setpoint, which isn’t ideal - I prefer different setpoint.

To automate this, I created this blueprint to automatically:

  • Detect when the unit switches to "heat_cool",
  • Resolve it into heat or cool depending on the season (Central Europe),
  • And apply my preferred temperature for each mode.

Now, the A/C starts correctly every time, even when controlled manually by the button on the unit itself.

What It Does

  • Watches selected climate.* entities
  • When any changes to "heat_cool", automatically:
    • Determines the season (Central European months)
    • Switches the mode to:
      • HEAT from September → April
      • COOL from May → August
    • Sets the target temperature according to your per-entity settings or defaults
  • Optional: only trigger when the setpoint is near 25 °C (so it won’t react to other mode changes)
  • Fully configurable per A/C unit

Inputs

Input Description Default
Climate Entities Climate entities to monitor —
Only React When Setpoint Matches Optional check for ~25 °C trigger Off
Setpoint Match Value Target temperature to match (±0.6 °C) 25
Per-Entity Setpoints Optional map of each entity with heat/cool temps heat = 21, cool = 25

Seasonal Behavior

  • Cold months (Sep–Apr) → switches to heat
  • Warm months (May–Aug) → switches to cool

You can easily adjust the month lists inside the YAML if you live in a different region.

Import the Blueprint

Open in Home Assistant

Example Use Case

  • Daikin A/C (Faikin integration) - tested and working perfectly
  • Other brands - should also work as long as the integration uses standard HA climate.* attributes
  • Useful for any climate device that defaults to heat_cool when powered on and doesn’t let you change the default setpoint

Notes

  • Works with multiple A/C units at once
  • If you don’t define per-entity setpoints, defaults of 21 °C (heat) and 25 °C (cool) are used
  • Designed around Central European seasons, but logic is easily editable

If you try it on another brand or climate integration, please share your results or improvements.