You didn’t define a selector that handles the switch between the two schedules.
Just because I’m curious: Why do you have an extra schedule for the weekend? A schedule covers all 7 days and so each day can be specified individually. Or do you also have the weekdays assigned differently in the weekend schedule, e.g. if you are on vacation? That would then make sense.
I have a question: what are the differences between the Calibration Temperature Sensor and the Room Temperature Sensor in matter of operation/functionality? In theory they can be the same and in an essence they are both controlling the “desired” temperature.
You can add the same sensors. In the next major release there is only one room temperature sensor. 
The naming for the schedules was not clearly from my side. “wochenend” was another schedule, it is now for vacation. Refactoring is sometimes… eh… strange
Ok, thanks for your clarification and have a nice time!
Thanks - busy day - testing it now. Will keep you posted. Thanks for all your dedication and great work.
Hey,
I just decide to release the final version of AHCv5.
For everyone who’s coming from v4: Disable your old automations (for backup) and setup your new automations with the v5 blueprint from scratch.
If you encounter bugs, or you just have questions and ideas feel free to give feedback.
So, happy heating @all and many thanks to all testers and everyone who supported me! 
Best regards,
panhans
Congrats for the new release!
Just updated from the dev version but unfortunately my automations don’t work anymore. I get the following error for each automation:
Logger: homeassistant.components.automation.thermostatsteuerung_schlafzimmer
Quelle: components/automation/init.py:689
Integration: Automatisierung (Dokumentation, Probleme)
Erstmals aufgetreten: 11. November 2024 um 23:16:28 (68 Vorkommnisse)
Zuletzt protokolliert: 06:47:58
Error rendering variables: TypeError: unhashable type: ‘list’
Help would be greatly appreciated….
Hey, did you setup the new blueprint from scratch? The new blueprint is not compatible to the old setup. If you did then just share your automation configuration in yaml with me.
Hi,
Thanks for the quick reply. I had set them up for the 5.0rc2 version. To test I setup one of them from scratch but that didn’t change anything.
Here’s the current config:
Advanced Heating Control v5 alias: Thermostatsteuerung Schlafzimmer
description: ""
use_blueprint:
path: panhans/advanced_heating_control.yaml
input:
input_trvs:
- climate.thermostat_schlafzimmer
input_temperature_comfort_static: 21
input_temperature_eco_static: 17
input_mode_party: []
input_persons:
- person.person1
- person.person2
input_schedulers:
- schedule.zeitplan_schlafzimmer
input_windows:
- binary_sensor.fenster_schlafzimmer_links_window_door_is_open_21
- binary_sensor.fenster_schlafzimmer_mitte_window_door_is_open_3
- binary_sensor.fenster_schlafzimmer_rechts_window_door_is_open
- binary_sensor.balkontur_schlafzimmer_window_door_is_open
input_windows_reaction_time_open:
hours: 0
minutes: 0
seconds: 20
input_windows_reaction_time_close:
hours: 0
minutes: 0
seconds: 20
input_log_level: debug
Thank you. Issue is fixed. It came with a last change. 
Just update the blueprint, please.
Wow, you’re the best. That fixed it. Thanks so much.
Hello Panhans.
Great job.
I have wa question about aggressive calibration. If I adjust the Delta to e.g. 1, the thermostat temperature is adjusted via the calibration value so that the thermostat switches on or off. What is the behavior at 0? I don’t quite understand your description text. " if Range is 0, then Offset is Always added "
Thank you
Stefan
Let’s say the Range is 0.5 and the offset is 1 and your target temperature is 20°.
With the range parameter you define a window around your target temperature. Is the room temperature in this window the original temperature is set. If you set the range to 0° you close the window and the offset is added whenever the room temperature is not equal to the target temperature.
If the current room temperature is:
[19.5 ← 20 → 20.5] → in this range the original target temperature is set.
[… ← 19.5] → lower than the range the offset is added. In this case 21°
[20.5 → …] → higher than the range the offset is subtracted. In this case 19°
With a range of 0:
If your room temperature is below 20°, e.g. 19.9°C → offset is added to target temperature (21°)
Vice versa: room temperature is higher than 20° target, e.g. 20.1° → the offset gets subtracted (19°)
Aggressive Calibration doesn’t manipulates the target temperatures of your thermostat but the add this calculation to the calibration entities. So the displayed target temperature is always the original set temperature.
thank you for your explanation.
does the offset then have to be greater than the switch-on threshold of the thermostat? (in my case 0.5) or is the heating command started and stopped by the automation? e.g. when range > or < the set 0.2°C.
the point with the “calibration” is clear. Works so far. I always get the right temperature displayed.
The automation only sets the target temperature. If the valve gets opened is handled by your thermostat.
If your thermostat can only open and close the valve fully, the offset is as good as irrelevant. It only needs to be large enough for the thermostat to react. So to be on the safe side, make it larger.
If your thermostat opens the valve opening as a percentage, you can work with smaller values for the offset.
Ok, I got. it.
I have normal open and closed valves for underfloor heating. And to avoid overheating I wanted to use this function. The offset must then be greater than the switching control of the thermostat. Thanks for the explanation
@panhans 2 Points:
Hello @panhans Thank you very much for your Blueprint! I have a question, if I wanted to activate the thermostat with the dashboard, Automation will pause, for example when I want to warm up the office before going to work. Do you have any ideas? Thank you very much!
Hey, im currenlty playing around with the newest dev Version for all of my Heaters (Tado Theromostat) . But somehow on one unit the calibration goes crazy and pushes the value ob to -8°C. When I turn the AHC DEV Automation off and enable the regular AHC Automation everything works well. How could I assist you on the issue tracking?
thanks, Martin
