🔥 Advanced Heating Control

[panhans]

ADVANCED HEATING CONTROL

Features

🔥 heating / ❄️ cooling based on
    👥 people presence
    🗓️ multiple schedulers
    🚶 presence sensor
    ↔️ proximity aka geo fencing
🏃 away temperature offset
🥶 frost protection
😡 adjustable aggressive mode
🌤️ activation based on weather, temperature or boolean entities
🎛️ granular schedule adjustments 
🪟 multiple window open detection
🎈 party mode
🤝 guest mode
🧭 thermostat calibration for the most common devices (Tado, Aqara, Popp / Danfoss / Hive, Tuya)
⚔️ liming protection
⚙️ several tweaks for fixing your thermostat issues
🎬 custom action
🤫 calm & 💪 reliable

Advanced Control ^V5

SourceCode | AHC Template Sensor | AHC Version Sensor

Advanced Heating Control V4 (deprecated)

_DEPRICATED

Development

Latest version: 5.0

Major Changelogs:
5.0

4.0 | 4.1 | 4.2 | 4.3

Planned Features

• calendar support
• more adjustable limits for aggressive mode
• stagged away mode
• valve positioning
• selection for thermostats for generic calibration / aggressive mode
• entities for away temperature and thresholds (on/off)

Thanks for testing, reporting and debugging to everyone especially: sben, sourdistorne, dario2 , coldspark29 , technikhaus, tirol3, stephanschleichstr13, bandit79, Mar1us, vajdum. Ziegelsandundspucke, mukrop, k-dani, allard77, hainfelder, Appox, NikB, kitus, David883, P6Dave, fir3dragon, DenisLanz, CarstenJ, tco95ttocs, Rapha0000, NoBadDays739

Hints & FAQ

FAQ

Q: Why Watchmen and Spooky warns me about the service tado.set_climate_temperature_offset

A: This service is part of an unofficial Tado integraton. The offical integration doesn’t offer calibration support. You can ignor this warning.

Q: How does the generic calibration work?

A: Example:

T_Room = 18°C
T_thermostat = 20°C
T_target = 24°C
T_{TargetCalibrated} = T_target - (T_Room - T_thermostat) = 24°C - (18°C - 20°C) = 26°C

After a while of heating:

T_Room = 20°C
T_thermostat = 22°C
T_target = 24°C
T_{TargetCalibrated} = T_target - (T_Room - T_thermostat) = 24°C - (20°C - 22°C) = 26°C

And when the room temperature is nearly reached:

T_Room = 23.5°C
T_thermostat = 24°C
T_target = 24°C
T_{TargetCalibrated} = T_target - (T_Room - T_thermostat) = 24°C - (23.5°C - 24°C) = 24.5°C

With every temperature change of target, sensor or temperature of the thermostat, the values gets renewed. So the target temperatures of your thermostats are only for that moment. In 10 minutes they can differ to the current temps.

You encounter a problem?

1. Check if you’re running the latest version.
2. If it’s the case, describe your problem.
   1. What do you want to achieve?
   2. What doesn’t work?
3. Set debug level to warning
4. Trigger you automation
5. Share your tace log for example here
6. Give me some time to check

How do I get a trace log?

1. Navigate to your automations
2. Find your automation and click on three-dots-menu
3. Click on traces
4. Select a trace with the upper arrows
5. Click on three-dots-menu again
6. Click on download trace

Also you can create issues on my github repo.

Hints

To make long entering / leaving durations for persons and open / closing durations for windows work properly I recommend to setup the uptime integration.

Helpfull Snippets

Calendar Based Scheduler Selector Sensor

Here is an example for my template based binary sensor for holidays. There are two calendars. One holds the national holidays for my region and the other one is my personal calendar. The sensor scans for national holidays and a catchphrase for my personal one.

template:
- trigger:
    - platform: time_pattern
      minutes: /10
  action:
  - service: calendar.get_events
    data:
      start_date_time: "{{ now().replace(hour=0,minute=0,second=0,microsecond=0) }}"
      end_date_time: "{{ now().replace(hour=23,minute=59,second=59,microsecond=999999) }}"
    target:
      entity_id: 
        - calendar.family # edit this for your calendar entites
        - calendar.holidays
    response_variable: calendar_events
  binary_sensor:
  - name: Holiday
    icon: mdi:palm-tree
    unique_id: holiday
    # here you can add a catch phrase as regex also if the holiday calendar has an event the state of the sensor will be on
    state: >
      {{  
        ( calendar_events['calendar.family'].events | regex_search('holiday', ignorecase=True) ) or 
        ( calendar_events['calendar.holidays'].events | count > 0 ) 
      }}

If you have questions or feature request, feel free to comment this thread.

Greets!

References

UI inspired: ☀️ Cover Control Automation (CCA) - a comprehensive and highly configurable roller blind blueprint

My blueprints

Simple scene toggle
Yet not another door/window/sensor open warning notification with auto close
Zone notification extended
Advanced Heating Control

[illiloh]

very nice. Is it possible to switch back to the previous temperature after x hours of manual intervention?

[panhans]

Maybe you can trigger the heating automation using another like this:

description: ""
mode: restart
trigger:
  - platform: state
    entity_id:
      - climate.your_trv
    attribute: temperature
condition: []
action:
  - delay:
      hours: 2
      minutes: 0
      seconds: 0
      milliseconds: 0
  - service: automation.trigger
    data: {}
    target:
      entity_id: automation.your_heating_automation

[andre217 (Andre)]

Hi panhans!

Thanks for providing this! I tried implementing it today, but I failed. First one obvious thing:
The window entity is not optional and I am not able to save the automation if I have no window sensor.
I fixed that by creating a new sensor, which extracts the window detection of my thermostat (Fritz! Thermo)

binary_sensor:
  - platform: template
    sensors:
      windowhelper:
        unique_id: d62d73da-7839-4cb4-8dd4-5a83b1f52923
        friendly_name: "Heizung-Helfer-Fenster-Proxy"
        device_class: window
        value_template: "{{ state_attr('climate.wohnbereich_linkes_fenster', 'window_open') }}"

But it didn’t help:
No matter what I try, the automation always sends an off state to the thermostat.
Do you have any idea, what I am doing wrong?

My config:

(both winter_mode and party_mode entities are helpers and set to off, at least one person is present, window state is closed, schedule is marked 9-22)

[panhans]

Hmm, I have one automation without window running atm. I’ll try to set up a new one.
If winter mode is off heating is always off. Try to set it to on.

[andre217 (Andre)]

That works, thank you! I am used to something like “Summer-Mode”, so my thinking got mixed up.

[lucidwings]

Great work! Super easy to set up and works as intended!
Nevertheless, the party mode doesn’t override my schedule. Is it a known issue or do you need further details?

[panhans]

I’d faced that issue a few days ago and fixed it this week. Maybe you try to update the blueprint.

[lucidwings]

Works like a charm! Thank you!

[scr44tch]

thx you very much, it works great,
would it be possible to make this work with a separate temperature sensor?

[panhans]

What should the external sensor do? Do you want the outside temperature to turn on/off heating?

[scr44tch]

thx for your answer,

i hoped to use a different temp sensor for the room,
my thermostats temperature is reporting way to high degrees. (i tried to offset the temperature, but its a total mess)
with an option for a different room temp sensor, one could just simply choose a sensor of choice.

hope that makes sense

[panhans]

This blueprint only controls temperature. There are other blueprints/automations for your issue. It also depends by your valves, integration and calibration attribute.

The most calibration automation can be used parallel to this blueprint. If you’re using tuya and z2m this thread could help you:

Tuya radiator valve (TS0601) calibration from external sensor (via zigbee2mqtt)

TuYa radiator valves measure temperate on themself, which gives inaccurate results. [TS0601_thermostat] This blueprint allow to calibrate them to have same (± ~0.5C) temperature, as external temperature sensor using MQTT message blueprint: name: Temperature Calibration description: Temperature calibration for Zigbee valve TS0601, according to external temperature sensor domain: automation input: valve: name: Smart Valve selector: entity: domain: clima…

[coldspark29]

@panhans: I am just trying your blueprint as well. Why don’t you have multiple window entities? Like this you have to create a template and combine all window contacts if your room has more than one. I just made a new one and changed it to multiple. I would also like to add thermometers to the blueprint, that are used as current temperature, because the ones at the valves are not a good choice in some cases. Will see how I can do that

[panhans]

1. Home assistant blueprints cant handle multiple optional entities used as trigger entities. There is an issue opend for that and also some threads here in the community but for most people not a big thing. Dont know if its ever be possible. So I must decide if I go with one optional window entity or multiple window support. Since some people use the build in window open mechanism I decide to chose the first option. Other blueprints are using time based periodical checks but I am not a friend of this kind of polling.

2. For using an external temperatur entity for calibration I wrote something one post above. Since this is much wanted I will dive into to see what I can do for this blueprint.

[coldspark29]

Ah yes, just setting the windows to multiple breaks the automation. Pity that this isn’t supported.

Haven’t read your post above. Will have a look into it. Thx

[panhans]

And you dont need a template. Simply create a helper and group your windows and select this group as your window entity.

[coldspark29]

Yes, thank you. Works like a charm

The blueprint is great apart from that. I could get rid of my complicated automations. I had one automation for turning the heaters on and one for turning them off. Horrible…

When the external temperature sensors are implemented, the blueprint will be perfect!

[diegot (Diego)]

Hey!

Thanks for this amazing blueprint, I got one question.
My EvoHome Systems requires the preset mode to Permanent otherwise it will follow a strange inside build schedule…

How can I add the preset mode to the Blueprint?
For Example, HVAC Mode Heat + Preset Mode: Permanent

Second question is, I can’t set the temperature to 19.5 in the Blueprint, am I doing something wrong?

Hope you can help me out with this!

[diegot (Diego)]

I found something like this that works for me but I am not sure where I can leave this code in the blueprint:

service: climate.set_preset_mode
data:
preset_mode: permanent
target:
entity_id: climate.living_room