Ah, ok get it. Simply get rid of the away temperature setup. What you are looking for ist frost protection. Perhaps I should extend the away temperature to the eco temperature or at least offer this as an option.
@mi-hol
Thanks for your feedback. The best way for debugging your issue is if you let run the automation to the state you don’t want and share a trace log of this moment. It’s everything described in the initial post of this thread. Thanks!
But I want to have them when nobody is at home.
Thanks, I found troubleshooting instructions in FAQ now.
On first read I didn’t see them because the topic needs to be expanded manually.
Maybe you want to give “Troubleshooting” its own section or rename this section to “Troubleshooting & FAQ” ?
1 Like
I tried to use this blueprint for my pellet stove I just bought this year.
Maybe I have some mistakes in my configuration:
alias: Ofensteuerung
description: ""
use_blueprint:
path: panhans/heating_control.yaml
input:
input_trvs:
- climate.ofen
input_temperature_minimum: input_number.absenktemperatur
input_temperature_comfort: input_number.komforttemperatur
input_windows:
- binary_sensor.fenster_wohnzimmer_contact
input_mode_winter: input_boolean.heizung_winter_modus
input_mode_outside_temperature: sensor.temperatur_aussen_temperature
input_persons: []
input_presence_sensor: binary_sensor.presence_wohnzimmer_both
input_schedulers:
- schedule.heizplan
input_temperature_minimum_static: 17
input_temperature_comfort_static: 21
input_away_options: []
input_mode_room_temperature: sensor.temperatur_wohnzimmer_temperature
The first problem is that the comfort temperature of 21°C is not reached. Temperatures are always between 17 and 19°C.
The second problem is that the heating process also runs at night. The presence detector is set to “Off” and the scheduler is also inactive at night. I have already removed the configuration from the user, as I am still in the house at night. But that didn’t help.
@Thomas71
Could you first check if you’re running the latest verision? This looks like a really old version.
Then also check / post the graph of your climate entity, especially have an eye on the local temperature.
@Ohana_Means_family
Yep, you can also disable the scheduler away mode.
Dint think of making 2 different automations for heat and another for cool. thanks for the help.
Thanks for staying so active and helping out.
1 Like
Yes, but you need to check the state of your on/off/winter mode entity in the custom condition to prevent the automation set the climates to off. If you don’t the automations will fight against each other. 
@panhans i found a small issue within your blueprint. if you open a window after your scheduling plan (e.g. scheduling is daily from 6am to 8pm) the scheduling plan is ignored and heating is started again after i close the window
e.g.: open at 9pm and close it a few minutes aftwerwards → heating starts again but should not start
Hi @panhans!
long time user returning now. I happily used your automation when version 3 was out but fell off the wagon for multiple reasons. Just installed today the latest blueprint and configured all the relevant sections, to the best of my Knowledge. I’m blown away with the many options we currently have now and by the documentation (btw, the link to the documentation site is broken but I managed to find a way around to it). Hats off.
For the life of me I can’t seem to get the automation to work as I understand it should. I have a AHC based system now. When I used v3 my heating system at home was Tado based but gas prices have skyrocketed and I’m now giving AHC a try because electricity is, at least today, a bit less expensive.
As of now, Party mode works, which confirms the automation talks to my AHC system, which in turn helps me verify that HA talks to the AHC too, and it does that very quickly and it does so locally without going out onto the cloud. This is good.
Once the basics are in place, I added the personas (me and my wife), proximity configuration and schedules. To start with, I picked a dummy schedule schedule.schedule_heating_holidays_or_guest which holds a 24x7 ON pattern, just to keep iterating things one by one.
With all these settings in place, I made sure input_boolean.global_heating was set to on, and then I switched on input_boolean.guests, which should, in my understanding, pretend a person is at home. Given the basic integration has been successfully tested beforehand, I would expect to see the heating going off as soon as I switch on the guest Boolean… but that was not the case. Automation would not get automatically triggered, even if I toggle input_boolean.guests back and forth. And I presume this means that when me and/or my wife get home, the result will be the same (currently away for a few days).
I then did the following test: while input_boolean.guests was kept set to true and the rest of the scenario was unmodified, I manually triggered the automation. And here the heating got activated.
Here you can find the trace corresponding to me manually running the automation while the heating was ON and WHILE input_boolean.guests was now set to false.
This is my configuration. I would be very thankful if you could take a look at it and help me troubleshoot my case:
alias: 🔥 Heating - Advanced Heating Control V5
description: ""
use_blueprint:
path: panhans/advanced_heating_control.yaml
input:
input_force_eco_temperature: input_boolean.heating_eco_mode_toggle
input_trvs:
- climate.a_comedor
- climate.a_h_jan
- climate.a_h_noah
- climate.a_h_pol
- climate.a_h_suite
input_temperature_comfort: input_number.heating_confort_temperature
input_temperature_eco: input_number.heating_eco_temperature
input_mode_party:
- input_boolean.heating_party_mode_toggle
input_persons:
- person.lauri
- person.marc
input_people_entering_home_duration:
hours: 0
minutes: 5
seconds: 0
input_mode_guest: input_boolean.guests
input_people_leaving_home_duration:
hours: 0
minutes: 15
seconds: 0
input_schedulers:
- schedule.schedule_heating_default
- schedule.schedule_heating_complete_off
- schedule.schedule_heating_holidays_or_guest
input_scheduler_selector: input_select.input_select_heating_schedule
input_temperature_eco_static: 20
input_temperature_comfort_static: 23
input_min_instead_of_off: false
input_proximity_duration:
hours: 0
minutes: 10
seconds: 0
input_mode_winter: input_boolean.global_heating
input_off_instead_of_eco: true
input_reset_temperature: true
input_log_level: warning
input_mode_outside_temperature: weather.home
input_mode_outside_temperature_threshold: 7
input_proximity: a7aa3dfbe7e3c80f63d34f29139b8470
input_startup_delay:
hours: 0
minutes: 0
seconds: 10
input_custom_action:
- action: persistent_notification.create
metadata: {}
data:
message: Cambio en la automatización de autoheating
title: Autoheating
Just following up on this. As described. I had the valve alarm showing up after the actual temperature not reaching the setpoint for about an hour.
check
Heat/winter mode is starts below X themp.
Any change i can change this for the cool/summer automation in start above X?
heating automation would start if outside is below 18°. The second cooling automation would start if outside is above 25°
This is probably realy easy for you but my yaml inst good enouf to tackel this allone.
For now i just made an extra automation to turn on/off the cooling automation. Cant think of any reason wy this woul not work but would be cleaner if it wanst needed. (maby i wil learn enouf by the summer to do it myself 
)
BTW for me this solves the tolerance thing also. there is no need to start up the airco the moment the heat stops.
I’m answering to myself. Based on the testing that I’ve done, it looks like the field “Guest Mode” under section “Persons” is also affected by both “Enter Home Duration” and " Leaving Home Duration".
I honestly did not expect for Guest mode to be dependent on those two options because of its artificial nature. It will not physically “enter” or “leave” the home area, hence I had not anticipated this could be the case. Silly me!
It looks like I’m ready to test the automation. Cheers @panhans! I’m buying you another beer!!
1 Like
First of all, I would like to wish you all a happy new year.
Unfortunately, switching the oven on and off does not work properly even with the latest version 5.2.6.
The switch-off did not work at all, I had to switch off the oven manually. It switched on at 3 o’clock in the morning and the temperature rose to 30 °C. It should stay at 17 °C during the night. The heating schedule scheduler went active at 7:30 am today and switches off at 10 pm.
I also switched it on and off manually yesterday.
I also have a question: is there a hysteresis in the script and if so, how is it set if I have only configured the comfort temperature of 21 °C and the setback temperature of 17 °C?
Hi, would be nice if you let run the automation into the state you don’t want and take a trace log of this moment.
Also the thermostat should handle the temperature if it’s set to 21 and it heats up to 30 there must be something wrong with the thermostat.
Hysteresis isn’t implemented yet since this is part of the thermostat. If you’re using the generic thermostat integration you can configure it using this integration. There is only an option to compensate hysteresis (aggressive mode) because it’s not wanted for the most users.
Thank you for this really amazing blueprint! I just use it now in all of my thermostat automations and it works great.
Just one question. Is there an easy way to store the temperature set by the blueprint to a state?
1 Like
Thank you! Yes, its almost there. Just open the first post of this thread and look for AHC Template Sensor. If you set this up you have access to some variables of the blueprint.
This is designed as a binary sensor. If you need the target temperature as a state and not as an attribute you can edit this to a sensor and intercept the target temperature in the state.