🔥 Advanced Heating Control

[Schaffis]

Hi
I get warning (from spook tool) that the automation references an action that HA doesn’t recognize.
I am not using Tado TVR. Is this a bug or can it be ignored or rectified?

(automation.advanced_heating_control_l1)

• tado.set_climate_temperature_offset

[panhans]

@say1897

What is an uptime entity needed for?

The uptime integration provides a sensor with the timestamp of the last start of home assistant.
Home Assistant updates every entity with every restart so the last_changed attribute is at least the ha start timestamp.
Without knowing the actual ha uptime timestamp the automation waits after every restart until the durations ran out.
Let’s say you set the duration for presence activation to 5 min. Before restarting ha the presence detection is already on. After a restart the automation waits again for 5 min until the target temp will be set to comfort temp. With the uptime sensor the automation checks wether home assistant just started at kicks in heating without waiting the additional minutes.

There is no need to setup this integration. It’s just a recommendation.

@jonathanarcher

Hi,
could you please explain the “physical temperature change” feature? I can see that the temperature is changed according to input from the thermostat, but how/when is it supposed to reset? When using the feature while ECO is set I notice that the thermostat is set back to ECO after a short while.

Thanks

In case of physical change feature I would recommend to disable reset temperature and set a reset of the temperatures by setting up an entry of the heating adjustments at night or so.
I will add this to the warnings if it’s configured like this.

@Schaffis

Is this a bug or can it be ignored or rectified?

It’s mentioned in the initial post under FAQ. You can ignore this warning.

[CarstenJ (Carsten Jung)]

@CarstenJ

I will try your solution in the mean time.

Unfortunately, still doesn’t work. I have renamed my Ally’s entity to “number.thermostat_bad_external_temperatursensor_2”.

• I should see a time stamp in the “last_calibration” section in my AHC sensor, right? That’s still empty.
• The current temperature that’s measured by the external sensor should be written onto that entity “number.thermostat_bad_external_tempertursensor_2”, right? That just doesn’t change.

[Ohana_Means_family]

@ panhans

Advanced Heating Control

I have written the Suppoer from Aqara. See picture what the ! says. In addition, AHC sets the wrong temperatures. I have written the Suppoer from Aqara. See picture what the ! says. In addition, AHC sets the wrong temperatures. This error occurs again and again. I have to take the batteries out to reset the TRV, that with 10 TRV’s. [grafik] Yesterday I noticed that it should switch from 20 °C to 22 °C in the kitchen, for example, when someone comes home. But it was set to 21.5 °C. Accordi…

[panhans]

@CarstenJ
Could you lower the temperature delta and heat up the sensor a little bit, e.g. by holding it in your hands in order to trigger the calibration?

@Ohana_Means_family
Could you upload and share the trace log where you get the warning/error?

[panhans]

Hello everyone,

I have reworked the complete code base the last few days, adjusted the selectors and added some minor functions and improvements such as

• aggressive mode over calibration
• automatic setting for Aqara/Xiaomi thermostats for external calibration

The new code base should serve for further features and make maintenance and troubleshooting much easier.

I have also changed the file name and recommend that you setup the automation from scratch as a few selectors have changed.

If you want, you are welcome to test it and give feedback.
Thanks to all!

Links:
Advanced Heating Control v5 RC
AHC Template Sensor v5

Fixes

• rc1_a: fix aggressive mode calibration & update template sensor
• rc1_b: fix setting target temp when adjustments are defined

[jonathanarcher]

@panhans

In case of physical change feature I would recommend to disable reset temperature and set a reset of the temperatures by setting up an entry of the heating adjustments at night or so.
I will add this to the warnings if it’s configured like this.

Thanks for the reply. I didn’t set “reset termperature” however. I would really appreciate if you could comment on the way the “physical termperature change” feature is designed to work.

Thanks so much.

[stephanschleichstr13]

can you put it please into the dev version?

[panhans]

@jonathanarcher

You need to setup entities for comfort or eco temperature. When changing the temperature over the thermostat card or the device the corresponding temperature entity gets set to the new target temperature. If comfort mode is currently active the entity for comfort temperature will be taken if not the eco temperature.
This triggers the automation again to change alle other thermostats to the new target temperature. This feature should be more robust in the current test version than in v4.

@stephanschleichstr13
Done!

[stephanschleichstr13]

Im not 100% sure with the “Calibration Entity Key Word” feature.
What is the right “Calibration Entity”? my thermostat or my external sensor?
the external sensor is already the “Room Temperature Sensor” so i need to add again this one?

Edit: aah the “Room Temperature Sensor” is for “Enable Room Temperature Threshold”

[hainfelder]

as far as I understand it:
Calibration Entity is the entity of the thermostat, where calibration can be changed.

AHC looks for an entitiy that includes the keyword.
(Seems to be a clever workaround to adapt to many different thermostats)

In one case the calibration entity was named “externer” (external in german) … by setting the “Calibration Entity Key Word” we can tell AHC what to look for.

(this was the logic before already - only now we can change the keyword in the UI.)

[stephanschleichstr13]

alright thanks.

[tco95ttocs (Mario)]

so normaly there is no need to change the given keyword?

[panhans]

Yes, not needed. There are some users who localize the IDs. Thats why the default entity_ids doesn’t match the algorithm anymore. In this case the key word must be changed to make calibration work again.

[say1897]

@panhans

The uptime integration provides a sensor with the timestamp of the last start of home assistant.
Home Assistant updates every entity with every restart so the last_changed attribute is at least the ha start timestamp.
Without knowing the actual ha uptime timestamp the automation waits after every restart until the durations ran out.
Let’s say you set the duration for presence activation to 5 min. Before restarting ha the presence detection is already on. After a restart the automation waits again for 5 min until the target temp will be set to comfort temp. With the uptime sensor the automation checks wether home assistant just started at kicks in heating without waiting the additional minutes.

There is no need to setup this integration. It’s just a recommendation.

Thank you for your detailed response. With this explanation, I can work well. It seems like this is generally a very useful thing! THANK YOU!

[Ohana_Means_family]

@panhans

Könnten Sie das Trace-Protokoll hochladen und teilen, in dem Sie die Warnung/den Fehler erhalten?

Which protocol? Where is it?

[miguelpineiroo]

Great blueprint!! Congrats. I have set it up last week and I am very happy. I am using the proximity integration to track my Home zone. The only issue I am having is when I go out from home for a short period of time, let’s say 1 h, and the heater turns off. I prefer to maintain it on. To try to fix it, I have created another zone that is centered in my home but with a larger radius, let’s call it “home wide” zone. The idea is that if I am both at “home” or at “home wide” zones, the heater is on. If I set in the blueprint proximity filed the “wide zone”, it is not working when I am at home, as I am detected at home, but not at home wide. Maybe it is an issue with two overlapping zones, that selects the smaller. To make it work, it would require that the proximity section of the blueprint allows to track two zones, not only home. Is it possible to do that, or do you see an alternative? Thanks in advance.

[panhans]

If you only go with proximity you can keep your larger zone and add person entities.

[tco95ttocs (Mario)]

hi guys, i have a quaestion about the sheduling. At the moment i have several schedules, for example “normal” and “holiday”. At the moment i have to change them with the schedule selector. Would it be possible to integrate the workday integration to this blueprint, so that it will automaticaly switch between “normal” and “holiday” or weekend?

[panhans]

If I am right the workday sensor is just a binary sensor, correct? On holiday it is off and on a regular workday on.

Add your schedules in the correct order:

1. Holiday Schedule
2. Workday Schedule

Then just set your workday sensor as your scheduler selector.