🔥 Advanced Heating Control

[Ohana_Means_family]

I wish that if I have a presence detector and integrate it into AHC, I could also set an extra temperature for the rider.

[Korbelix]

Could you please share the code for this card? Was looking to build something similiar and would love to use this as a starting point

[mauritsivs]

this card is awesome! would be great if you could share the code/process

[ajb538 (Alex)]

on v4.1, will try v5 and report back if it still doesnt work…thanks

[ajb538 (Alex)]

Just tried v5, not sure the schedule / plan adjustments are working in v5 yet…

With the selector defined, and the ‘Shoulder Schedule’ selected, its still only applying the adjustment associated with the ‘Winter Schedule’, not the ‘Shoulder Schedule’ as expected. It’s 3:47pm so should have applied the ‘Shoulder Schedule’ adjustment and set temp to 21c, but is setting it to 19c as per the Winter Schedule adjustment thats defined.

[tasomaniac (Taso Dane)]

Thanks a lot for this automation @panhans

I was planning to report bunch of issue because I couldn’t make the combination of some settings work before. I just upgraded to v5 and then it works flawlessly.

Here is my set-up: I have 2 rooms only. Living Room and Bedroom. I have a Aqara FP2 presence sensor in the living room.

• Living Room: only based on presence. 5 min after the room is empty, lower to eco, immediately after entering the room increase to comfort.
• Bedroom: Based on schedule, during the day comfort, during the night eco.

I do have a question about the “away mode” though. When I set away mode to -4 degrees and when the living room was empty, the automation still put the eco temperature and did not apply -4. But anyways, I also struggle to understand the concept of “away” with presence. When the room is empty, AHC anyways set to eco temp which is lower. And this by default already works like the “away” feature. What is the use case of setting up both away and presence?

[P6Dave (Dave Forrester)]

CALIBRATION - TADO

Has anyone using this blueprint with Tado devices been able to successfully set up the calibration element without experiencing huge changes to the target temperatures?

All of my rooms have a separate thermometer measuring the temperature in a central location away from any external influence. However, every time I try to configure calibration using one of those, I get offsets that vary from +15°C to -10°C. I thought I was going mad until I figured out that it was the calibration setting these offsets so large. The temperature difference between that measured by the radiator valve is usually no more than 2 or 3°C away from the separate thermometer I have in the same room. So why would it apply such a large offset?

I read through the documentation again. Here is one of my tado climate entities, I’ve set the offset value manually in the Tado app:

The offset is an attribute so doesn’t have an entity_id

This states that tado is supported, but that the tado integration doesn’t generate a separate calibration entity. If that’s the case, how does this blueprint apply the offset as shown here?

Also, what calibration timeout should I set if I only want to calibrate the radiator valve twice a day? Do I need to set a timeout value at all, or is that just a fallback (I note it says the minimum value should be 2s)?

Finally, how critical to the process are settings such as calibration delta and generic calibration offset?

Thanks.

[victoroos (Victor Roos)]

Hello,

I seem to be unable to get the presence detection working.
I used a motion group but the automation doesn’t respond even when it is in de intended schedule.
Any tips?

Cheers
Vic

[P6Dave (Dave Forrester)]

I think I’ve figured out my calibration issues now. I’ve had two rooms calibrating with the following settings for 24 hours now and it is working

My next question is in relation to turning that calibration on and off based on the state of a door contact.

We generally leave all our downstairs room doors open and the main temperature sensor is in our hallway. I’d like to calibrate the downstairs temperature using a temperature sensor in our main sitting room, the door of which is closed at night.

So is it possible to turn on and off calibration of a room based on the state of a door contact sensor? I suspect not, because the adjustments require a timestamp entry.

In which case, is it possible to capture the last_changed time of a door contact and use that to change the time of a heating adjustment on the fly?

For example:

• close door - turn calibration off
• open door - turn calibration on

[panhans]

@NoI3ody

But when i open a window, the temperature drops from for example 20°C to 5°C, but when i close the window it stays at 5°C. I think the problem is that my Comfort Temperature Entity, gets read by the “experimental feature” and reads the trv temperature and drops to 5°C, but after closing it doesn´t get up to it´s last value. Is there a way arround this?

Thanks for reporting. I will check this.

@ajb538

With the selector defined, and the ‘Shoulder Schedule’ selected, its still only applying the adjustment associated with the ‘Winter Schedule’, not the ‘Shoulder Schedule’ as expected. It’s 3:47pm so should have applied the ‘Shoulder Schedule’ adjustment and set temp to 21c, but is setting it to 19c as per the Winter Schedule adjustment thats defined.

Hmm… I have definitely tested this. Could you share me your adjustments as yaml code?

@tasomaniac

I do have a question about the “away mode” though. When I set away mode to -4 degrees and when the living room was empty, the automation still put the eco temperature and did not apply -4. But anyways, I also struggle to understand the concept of “away” with presence. When the room is empty, AHC anyways set to eco temp which is lower. And this by default already works like the “away” feature. What is the use case of setting up both away and presence?

For away mode and presence you have to two options:

Setup people and presence sensor:

• if somebody is at home and presence is off → away mode kicks in

Setup presence and presence schedule + enable ignore people

• if presence is off but presence schedule is on → away mode kicks in

@victoroos
Could you share your automation configuration in yaml?

@P6Dave

My next question is in relation to turning that calibration on and off based on the state of a door contact.

Not possible atm, but I could easily implement a custom condition for the calibration action branch if you like. So you’re able to define your own custom condtion to allow / block calibration.

[P6Dave (Dave Forrester)]

@panhans

I could easily implement a custom condition for the calibration action branch if you like. So you’re able to define your own custom condtion to allow / block calibration

That would be amazing, as long as it’s not too much work for you. It’s a quite a niche request I would imagine.

[tasomaniac (Taso Dane)]

@panhans

Setup presence and presence schedule + enable ignore people

• if presence is off but presence schedule is on → away mode kicks in

But in this case if you don’t use away feature, the temperature will be dropped to eco anyways right? What’s the difference?

[panhans]

Presence schedule on + presence on → comfort
Presence schedule on + presence off → away temp (comfort - away offset)
Presence schedule off → eco

[mattbruman (Bruman)]

Hello, thank you for this BP. It really solves the headaches of the Mr Cool products.

So the Mr Cool mini splits have this issue where they don’t turn off their fans once its to temp so this BP allows me to turn off the device once it hits the temp. My question is, is there a setting for a run delay that will ensure the HVAC device runs for a minimum amount of time to prevent bouncing on and off too quickly? I am trying to ensure my mini split runs at least 10min once it is triggered to turn back on. After the 10min it allows the automation to return to the previous instructions. Would also need a similar option to ensure it stays off long enough to finish any shutdown routines.

Again thank you for all the work put into this BP.

[Bernhard76]

So, I have purchased a few external temperature sensors there is some action now, but I still don’t fully understand the logic.

As for the burner - sure, here is the info of my burner climate:

climate.vscotho1_200_11_heizung
hvac_modes: off, auto, heat
min_temp: 3
max_temp: 37
target_temp_step: 1
preset_modes: comfort, eco, home, sleep
current_temperature: 58.5
temperature: 28
hvac_action: heating
preset_mode: home
vicare_programs: comfort, eco, external, holiday, normal, reduced, standby
active_vicare_program: normal
active_vicare_mode: forcedNormal
heating_curve_slope: 1.2
heating_curve_shift: 0
vicare_modes: dhw, dhwAndHeating, forcedNormal, forcedReduced, standby
friendly_name: VScotHO1_200_11 Heizung
supported_features: 401

I have added an external temp sensor, but it also just sets the temp +max. Re-reading the part about generic calibration, I fear that it will not work for the burner (because current_temperature for the burner is of course…hot :-D) and I have to handle that myself.

Here is the info of my custom average temp:

state_class: measurement
unit_of_measurement: °C
device_class: temperature
friendly_name: AverageTemp

This is how a generic calibration looks like for me in a room.

[victoroos (Victor Roos)]

hi @panhans

I seem to be unable still to get the presence detection to work. I tried even manually switching with input bolean for full testing but nope.
This is my automation config with the motion group
VB automation config presence - Pastebin.com

I also noticed that sometimes when usingthe number boleans helper option the temperature just goes down to the lowest possible of that bolean, especially when using the away offset.

[e-p-s]

Does this help?

weekdays:
  - daily
timeslots:
  - 00:00:00 - 04:40:00
  - 04:40:00 - 07:20:00
  - 07:20:00 - 16:00:00
  - 16:00:00 - 20:00:00
  - 20:00:00 - 00:00:00
entities:
  - climate.thermostat_badezimmer
actions:
  - service: climate.set_hvac_mode
    data:
      hvac_mode: "off"
  - service: climate.set_temperature
    data:
      hvac_mode: heat
      temperature: 22
  - service: climate.set_hvac_mode
    data:
      hvac_mode: "off"
  - service: climate.set_temperature
    data:
      hvac_mode: heat
      temperature: 22
  - service: climate.set_hvac_mode
    data:
      hvac_mode: "off"
current_slot: 2
next_slot: 3
next_trigger: "2024-11-27T16:00:00+01:00"
tags: []
icon: mdi:calendar-clock
friendly_name: Badezimmer-Täglich

[tennents (Marcello)]

hi @panhans, and thanks for your awesome work!
i got a request… in my use scenario, i do not need a “Away offset” but only an “Away temp”.

the ideal configuration is

• someone is home → apply the schedule, setting comfort/eco temps based on time
• noone is home → set the away temp, always the same temp regardless of the schedule
  -someone in going home (proximity integration) → apply the schedule

is there a way to achieve this configuration using the tools already present? would you mind adding the option to choose between away offset and fixed away temp?

[panhans]

@mattbruman

I think you need a timer for your timeout. Then set a custom action in the blueprint settings that checks the timer state (not running) and if the target temperature is less or equal the room temperature.

If it’s the case just start the timer.

Then you need to check the timer in the custom condition, too. The state of the timer must be unequal to run.

@Bernhard76 @victoroos
I will have a look into this later.

@e-p-s
Yes, thanks. I will check this. Would be fine if you edit your post and put your yaml into a code block. There is a button for this that looks like this: </>

@tennents
Couldn’t you solve your problem with the frost protection feature?

[ajb538 (Alex)]

• time: “6:30”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
    scheduler: Winter Schedule
    comfort: “20”
• time: “11:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Winter Schedule
    comfort: “23”
• time: “14:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Winter Schedule
    comfort: “19”
• time: “18:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Winter Schedule
    comfort: “22”
• time: “21:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Winter Schedule
    comfort: “21”
• time: “6:30”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
    comfort: “21”
    scheduler: Shoulder Schedule
• time: “11:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Shoulder Schedule
    comfort: “22”
• time: “14:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Shoulder Schedule
    comfort: “21”
• time: “18:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Shoulder Schedule
    comfort: “21”
• time: “21:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Shoulder Schedule
    comfort: “20”
• time: “6:30”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
    scheduler: Summer Schedule
    comfort: “24”
• time: “11:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Summer Schedule
    comfort: “21”
• time: “14:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Summer Schedule
    comfort: “23”
• time: “18:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Summer Schedule
    comfort: “23”
• time: “21:00”
  days:
  • Mon
  • Tue
  • Wed
  • Thu
  • Fri
  • Sat
  • Sun
    scheduler: Summer Schedule
    comfort: “23”