🔥 Advanced Heating Control

@drawtrip

Could you double check if you have another instance of AHC in your automations? These error shouldn’t appear with your configuration.

Yes, try to use set_comfort.

If you use a schedule and a person, comfort is set when the schedule is active and you’re home. If this is not the case just share a trace log. (have a look into the initial post) Make sure you setup the uptime integration.

@klmmc @onrust The automation is stateless. When it is reloaded, it does not know whether someone has just come home or whether the person was already at home. The uptime integration ensures that the automation recognizes that Home Assistant has been running for a while and thus skips the waiting times. Otherwise, this behavior may occur… :wink:

Yes it’s a known tado bug. thats why some people want that timeouts for calibration or the ability tu toggle calibration completely off over night with help of the adjustments.

@LotF I will have look. :wink:

@powpow These warnings do not come from AHC. The attribute presets, for example, is not queried.

@Esmax555 Did you define a room temperature sensor? I think this TRVs should work. But we could digging a little deeper if you like.

@corx @LotF The trace logs are gone. I was a little late. :smiley:

@panhans Oh OK… sorry for the confusion!

1 Like

I didn t tried because this model wasn t on compatibility list, i will try it later

Hi what do you recommand for the “EUROTRONIC Spirit Z-WavePlus”
Can i use the “:old_key: Calibration Entity Key Word” also if not listed on the compatibility list ?

I saw if the zwave wave value the “Temperature Offset” and activated it

But i have a Problem je logic seams dont to work

I dont know why i never iut never trigged
image

Its time to turn the heat back on for the year but I keep getting this error

variables:
  is_delayed: >-
    {{ not (not is_uptime_defined or (now() | as_datetime -
    states(up_time_sensor) | as_datetime) > timedelta(**input_startup_delay)) }}

Hi, my automation trigger never, can somebody tell me what is wrong ?

The Confort TEmperature is set with

Here i have the on/OFF signal for heating, and it s ON

What is my Problem ?

No Problem, i reuploaded the logs:
06:04 is manual triggered automation via “Run actions”
06:05 is time scheduled run via “Heating Schedule Adjustments”

trace automation.flur_eg_heizung 2025-10-06T06_04_16.195770+00_00.json
trace automation.flur_eg_heizung 2025-10-06T06_05_00.246218+00_00.json

Just tried to set this up and, well, we’re using Fahrenheit here. My regular temp is 68F but as soon as the automation triggered it dropped my thermostat down the 45F. That’s… bad.

Somebody has an Idee what should i check ? why the logic never triged ?

Somebody has an Idee what should i check ? why the logic never triged ?

not sure, what might cause your problem.

One thing i can see, that you seem to use a Thermostatic Valve for Room Temperature Sensor - this makes no sense. As its stated in the description. This is supposed to be an external Sensor for Calibration.

Also you might install the AHC state sensor as found in the opening post.

Maybe also check if AHC is running fine without your temp scheduler “TempParents” - for debug just use Static Comfort Temperature.

yes that was a mistake i deleted from the automation now thx :slight_smile:

How can i do that exacly ?

Can you tell me if in this Automation how new “Confort Temp” is a trigger ?

i guess in this automation a trigger is missing to say that Automation have to check Confort value and then send the order Setppoint

Or how work this automation if we dont have presence sensor and no schedule ?

Uploading: image.png…

i added a schedule to see if he will trigger

its called “AHC template sensor” in the first post of this thread.
Add it to your configuration.yaml add it to a dashboard and then you can see all the states of AHC - very helpful for debugging (in may subjective experience)

I made a copy and paste and received

und here are the 3 Traces, perhaps u know how it works ?

Or i hope that @panhans can check it later
here the Traces:

Hi, I have used the latest version of AHC and try to use it with presence detection. But somehow the presence sensor is completely ignored.
I expected, that with the added presence sensor, the heating will stay in Eco mode till presence is detected via the sensor - even if the scheduler is switching to an active phase. Once the presence sensor gets triggered during an active phase of the scheduler, the heating switchs to comfort heating and returns to Eco after presence is not detected any more (+ presence delay).
In my case, the automation behaves as if there is no presence sensor set. Heating switches to comfort when scheduler switches to active phase and returns to Eco when scheduler is going back to non-active phase.

My configuration yaml looks as follows:

  alias: Heating Office
  description: ''
  use_blueprint:
    path: advanced_heating_control.yaml
    input:
      input_trvs:
      - climate.buero
      input_temperature_sensor: sensor.office_env_temperature
      input_temperature_eco_static: 10
      input_temperature_comfort: input_number.temp_office
      input_persons:
      - person.person1
      - person.person2
      input_mode_guest: input_boolean.heat_guest
      input_schedulers:
      - schedule.office
      input_presence_sensor: binary_sensor.office_motion_occupancy
      input_presence_reaction_on_time:
        hours: 0
        minutes: 0
        seconds: 15
      input_presence_reaction_off_time:
        hours: 0
        minutes: 5
        seconds: 0
      input_scheduler_presence: schedule.office
      input_windows:
      - binary_sensor.office_window_left_contact
      - binary_sensor.office_window_mid_contact
      - binary_sensor.office_window_right_contact
      input_calibration_generic: true
      input_mode_winter: input_boolean.heat_general_switch

Anything obvious that I missed in my config?

Hello,

I don’t understand the schedule.
I’ve created four schedule helpers: one for 5:30 AM (morning), one for 8:00 AM (daytime), one for 4:00 PM (evening), and one for 9:00 PM (night).
I’ve also added an input boolean for presence control.

How can I integrate these schedule helpers so that the heating is adjusted to the desired temperatures based on presence?

Why have multiple schedule helpers? You can have multiple active phases in one schedule helper and link this to your heating automation.
Regarding presence detection I‘m at the moment also struggling…

What error? You just posted some code. But I think some more get issues with this here.

@corx Thanks! I will check this.

Yes, it is. Could you share a trace log, please?

@Esmax555 I will check your trace log, too. Thanks. //EDIT: your link seems to be broken

@NotesTaker
With your configuration comfort kicks in when your office schedule is active. And the same schedle white lists the presence sensor. If you just want to use your presence sensor remove your schedules. If you want the presence senosor be recognized when you schedule is active set it as the presence schedule and leave the regular heating schedules blank.

@emmi89
You just need one schedule helper with your time slots. If you just want comfort heating when presence is detected, definde your schedule as presence schedule not heating schedule and set you presence entity.

Good morning,

Thank you very much for the quick replies. However, in addition to setting different times, I would also like to set different temperatures for different times of the day, which are not always the comfort temperature. For example, the heating should only heat to 20°C in the morning and to 23°C in the evening. The eco temperature should be 17°C when no one is present.

Did you check the documentation and the heating adjustments?