Scheduler section → Scheduler Selector (see the description)
You can set an input boolean as a party mode entity for example.
Atm, yes with winter mode or a fake window (input boolean), but I will add an overwrite modifier to the adjustments.
Not, atm. I will add this to the valve positioning section.
Have a look into the AHC template sensor. (Link in the first post)
Hi all,
i use this blueprint and it works so far very good. But i have one problem:
my window open time and close time is set to 30 sec. If the window is opened more than these 30 sec, everything is ok as the temperature is correctly restored after the Window gets closed.
But if the Window is opened only a very short time (<30sec), then, after the window is closed, the temperature is set to the eco temperature.
For me, it looks, the problem is, that when the window is opened shorter then the “window open time” no scene is generated.
I have eight TRVs (BRT-100-TRV) / Automations which all behave the same.
2025-01-24 14:48:32.329 INFO (MainThread) [blueprints.panhans.heatingcontrol] AHC - TRV-Wohnzimmer
automation delayed: False
2025-01-24 14:48:32.361 INFO (MainThread) [blueprints.panhans.heatingcontrol] AHC - Change - TRV-Wohnzimmer
Trigger ID: temperature_change_window_on Thermostat: climate.trv0008
Mode: heat
New Target Temp: 0.0
Current Target Temp: 21.0
2025-01-24 14:49:28.896 INFO (MainThread) [blueprints.panhans.heatingcontrol] AHC - TRV-Wohnzimmer
automation delayed: False
2025-01-24 14:49:28.929 INFO (MainThread) [blueprints.panhans.heatingcontrol] AHC - Calibration - TRV-Wohnzimmer
apply scene: scene.trv_wohnzimmer_window state: <template TemplateState(<state scene.trv_wohnzimmer_window=2025-01-24T13:38:27.314714+00:00; entity_id=[‘climate.trv0008’], friendly_name=trv_wohnzimmer_window @ 2025-01-24T14:48:32.351028+01:00>)>
2025-01-24 14:50:52.707 INFO (MainThread) [blueprints.panhans.heatingcontrol] AHC - TRV-Wohnzimmer
automation delayed: False
2025-01-24 14:50:52.740 INFO (MainThread) [blueprints.panhans.heatingcontrol] AHC - Change - TRV-Wohnzimmer
Trigger ID: temperature_change_window_off Thermostat: climate.trv0008
Mode: heat
New Target Temp: 14.5
Current Target Temp: 21.0
Greetings, Manfred
Hi, thanks for reporting. I can not confirm this behavior. Could you share a trace log? Have a look into the troubleshooting section. (first post of this thread)
Currently there seem to be problems with Aqara thermostats external temperature input: Is external_temperature_input of Aqara SRTS-A01 device still working? · Issue #24780 · Koenkk/zigbee2mqtt · GitHub
Ok, i will check. But it will be earliest late tomorrow.
I am running Version : 5.2.6
now you can set the max valve opening
Sure.
I have separate helpers for the temperatures (I replaced her name with “child” below). This automation checks for the beginning or end of a calendar event, and if that calendar event is titled “Child bei Mama”, it switches the target temperature around. At the beginning of the calendar event, it sets both comfort as well as eco temp to 16° (child is with mom). When that calendar event ends (child will return to me), the comfort is set to 21° and eco to 19°.
Separately, it also switches the bathroom schedule between two schedules via a Scheduler Selector that goes straight into the blueprint automation and switches between two separate schedules (input_select.select_last versus input_select.select_first) as we get up an hour earlier when the child stays with me because of the school run, hence I heat up the bathroom one hour earlier in those weeks.
This is how I both change target temperatures as well as schedules with one single automation.
Advanced Heating Control5.3 alias: Child Mama-Papa Calendar
triggers:
- trigger: calendar
event: start
entity_id: calendar.child
offset: "-0:0:0"
- trigger: calendar
event: end
entity_id: calendar.child
offset: "-0:0:0"
conditions:
- condition: template
value_template: "{{ 'Child bei Mama' in trigger.calendar_event.summary }}"
actions:
- if:
- condition: template
value_template: "{{ trigger.event == 'start' }}"
then:
- action: input_number.set_value
data:
value: 16
target:
entity_id: input_number.child_comfort
- action: input_number.set_value
metadata: {}
data:
value: 16
target:
entity_id: input_number.child_eco
- action: input_select.select_last
target:
entity_id:
- input_select.bad_scheduler_selector
data: {}
else:
- action: input_number.set_value
data:
value: 21
target:
entity_id: input_number.child_comfort
- action: input_number.set_value
metadata: {}
data:
value: 19
target:
entity_id: input_number.child_eco
- action: input_select.select_first
target:
entity_id:
- input_select.bad_scheduler_selector
data: {}
thank you for clearing that up for me!
The thermostat in my office does not have a calibration entity so it set it togeneric.
The thermostat in my livingroom does (at least i think its that). SO it looks like that:
What do i need to use as a keyword here?
Thanks for the help!
After update to newest Version i have this error in log:
expected HVACMode or one of ‘off’, ‘heat’, ‘cool’, ‘heat_cool’, ‘auto’, ‘dry’, ‘fan_only’ for dictionary value @ data[‘hvac_mode’]
Thanks for reporting. Update to the latest version, please.
hi
whatever you changed in this version to the latest 5.2.16, all my automations with an external temp sensor and generic calibration didn’t set neither eco nor comfort temp via a sheduler!
Or is it fixed with the 5.3.1?
Updated to 5.3.1 and it looks like its working again 
How can I switch the full automation off via the GUI?
I have open/close sensor on some of my windows, which stopped the heating.
Can I manually do this in any way?
I already tested with a binary helper sensor, but I can’t change the status of this.
Any ideas?
You can set the state of the sensor in the developer tools / state section. Filter for it, click on it, manipulate the state and click set state. Or you set an input boolean as a fake window.
Hi everyone,
thanks for providing this exceptional blueprint. I migrated away from better thermostat, since the temperatur was unreliable. But I currently am missing a nice way of controlling the room temperature. I was used to set up heating plans in Scheduler card and they also got this nice component better-thermostat-ui-card
Is there anyway to achive something similar, for the widget or the scheduling?
Thanks in advance!
Hi there, for a few days now I have a problem with AHC. Whenever there is a change in the state of a scheduler, the respective thermostat will be set to off. It used to work properly for quite some time.
I am not sure if this is some kind of bug? I updated to 5.3.1, but that didn’t solve the problem.
It would be nice if somebody can point me in the right direction to solve that issue. - Thanks.
Hi, could you share a trace log? (First post, troubleshooting section)
Thank you for your great blueprint.
I have several questions.
For the Proximity option, I would like to be able to set the temperature separately with an input_number entity, which is controlled when I am outside the range. Is this possible?
With the window open option, I would also like to be able to control the temperature using an input_number entity, is there a way to do that?
At night I would like to lower the temperature, I use the window option with a time of day sensor, would it be possible to implement this as a single option?
There is a holiday integration in HA, I would like to automatically treat the holidays like weekends. Is there a way to set that?
Thank you in advance for the help and thank you for the great blueprint.
Edit:
I also have to explain that I need another temperature in addition to the Comfort temperature when I’m at home. I use the Eco temperature for this.
Could you check the state of your outside temperature sensor if it is below you threshold temperature? Also try to remove it temporarily from your ahc configuration.
This really did the trick. I just realized that my outside temp sensor is unavailable.
Now I have another issue: For one of my AHC rules, the window sensor has an issue. The thermostat will be set to off when the window will be opened. However, the temperature won’t be set back to its previous value when the window has been closed.
I checked all the settings but couldn’t find any obvious error. Here’s the respective trace back: https://controlc.com/7b9e3032
