🔥 Advanced Heating Control

[panhans]

Sry! You’re totally right. I had no issues because I set the durations to 0! Fix is out. Just update!

@cborn Could you set the log level to warning and share the trace log after the wrong temperature is set?

[extreme4u]

Ah, perfect. Just tested it. Everything works now as expected. Thank you

[cborn (Christian)]

Most thermostats have now set up the correct and intented temperature. One thermostat is still not set up correctly. I am currently thinking about it being a problem with my bluetooth proxies. I have two Atom Lite ESP proxies but 8 thermostats and 2 other bluetooth devices. I will probably get one more proxy since they have limited slots for concurrent connections.

I have scanned the log and I have found one warning regarding the blueprint.

Logger: blueprints.panhans.heatingcontrol
Quelle: components/system_log/init.py:331
Erstmals aufgetreten: 21:32:15 (52 Vorkommnisse)
Zuletzt protokolliert: 21:43:47

AHC - To make Advance Heating Control work properly just setup the Uptime integration.

[myriad]

Hey panhans,

I’m currently setting up the thermostats at my parents’ house. However, I haven’t yet found a working solution for a specific use case. The aim is to ensure that a manual change to the target temperature is reset to the static values defined in the blueprint after a certain period of time. On the forum, I saw that version 3.4 introduced the functionality to start a party timer when the target temperature is physically changed on the thermostat. As far as I know, this option is no longer included in the current version (4.3.14). Because I use Bosch thermostats, I configured the aggressive mode for small corrections of the heating behavior, if that is relevant. I would be grateful for any suggestions.

Regarding the Reset Temperature tweak, I would find it handy if, in addition to the reset at the end of schedules or presence, one could also set a timer that starts when a change in the target temperature is detected that does not come from the blueprint itself. However, I cannot tell to what extent this is implementable. Perhaps it would also be useful for other users to be able to set a particular time of day for the reset.

Many thanks for your absolutely brilliant work so far!

[MikeDeltaHH (Michael)]

Hi there!

After updating the Blueprint from 4.3.4 to 4.3.14 all my heating automations no longer work, there is the same error everywhere - I have gone through the blueprints but can’t find the cause, can someone please help me?

Fehler: „extra keys not allowed @ data[‘actions’]. Got [{‘if’: [{‘condition’: ‘template’, ‘value_template’: “{{ trigger.id in [‘hastart’] }}”}], ‘then’: [{‘delay’: {‘seconds’: 10}}]}, {‘if’: [{‘condition’: ‘template’, ‘value_template’: ‘{{ valves_unsupported | count > 0 }}’}], ‘then’: [{‘action’: ‘system_log.write’, ‘data’: {‘level’: ‘warning’, ‘logger’: ‘blueprints.panhans.heatingcontrol’, ‘message’: “AHC - Your selected hvac mode {{ input_hvac_mode }} isn’t support by some of your climate entities: {{ valves_unsupported | join(', ') }}\n”}}]}, …
extra keys not allowed @ data[‘conditions’]. Got [{‘condition’: ‘template’, ‘value_template’: ‘{{ not scene_creation_block }}’}, {‘condition’: ‘or’, ‘conditions’: [{‘condition’: ‘template’, ‘value_template’: ‘{{ is_warning }}’}, {‘condition’: ‘template’, ‘value_template’: ‘{{ calibration_number | count > 0 }}’}, {‘condition’: ‘template’, ‘value_template’: ‘{{ calibration_tado | count > 0 }}’}, {‘condition’: ‘template’, ‘value_template’: ‘{{ changes | count > 0 and not is_temp_change_by_thermostat }}’}, {‘condition’: ‘template’, 'value_templ…
required key not provided @ data[‘action’]. Got None
required key not provided @ data[‘trigger’][0][‘platform’]. Got None“.

[panhans]

Update to Home Assistant 2024.10.X should solve your problem.

[MikeDeltaHH (Michael)]

Thanks a lot for your fast hint!

[cwein]

Hi there!

Awesome work!
One question: What ist the Party_mode exactly doing?

I tried it out but don’t really understand:

• I entered an input_boolean in that field and turned it to “on”
• After that I increase the temperature at the thermostat and was expecting, that nothing happens until I turn the boolean to off again.
• a few minutes later the automation sets the set-temperature to 16°C (don’t know where that number comes from)
• 1 min later the automation turns the thermostat “off”
• again 1 min later it turns the thermostat to “auto” to comfort-temperature
• again 1min later back to 16°C

[stephanschleichstr13]

i have still this log issue, maybe you can have a look again

Here the config, i think this is the only one that can be, this is a 90% prepared automation for rooms which are coming in future (but the automation is disabled)
i think the problem is that i have no scheduler selected?

alias: Advanced Climate Control Büro
description: ""
use_blueprint:
  path: panhans/heating_control.yaml
  input:
    input_trvs:
      - climate.buero_klimaanlage
    input_hvac_mode: cool
    input_temperature_minimum_static: 25
    input_temperature_comfort_static: 25
    input_persons:
      - person.xxxxx
      - person.xxxxx
    input_schedulers: []
    input_mode_party:
      - input_boolean.advanced_heating_control_wohnzimmer_party_mode
    input_mode_guest: input_boolean.advanced_heating_control_wohnzimmer_guest_mode
    input_windows:
      - binary_sensor.wohnzimmer_comet_dect_window_open
    input_temperature_sensor: sensor.thermal_comfort_wohnzimmer_hitzeindex
    input_mode_winter: input_boolean.kuehlperiode
    input_tweaks:
      - reset_temperature
      - off_instead_min
    input_mode_outside_temperature_threshold: 15
    input_scheduler_offset: 2
    input_away_offset: 0
    input_away_options: []
    input_mode_outside_temperature: weather.penthouse

[panhans]

@cwein

One question: What ist the Party_mode exactly doing?

Party mode forces comfort heating. If there is a number at the end of the entity name it will takes as the desired temperature for the duration party mode is enabled.

Before party starts states of climates get stored in a scene. At the end this will be recovered.

The 16°C is maybe your eco temperature. Without a trace log or configuration I can’t say more.

@stephanschleichstr13

Here the config, i think this is the only one that can be, this is a 90% prepared automation for rooms

I pasted this in the template editor without any error. But have a look into your automations with schedules defined and schedule selector. There must be one automation where a selector value doesn’t match to any friendly name of a scheduler, so the automation can’t figure out a valid schedule.

Like:

Selector Value: “Holiday”

Schedules: “Work”, “Work from Home”

[panhans]

@myriad

As far as I know, this option is no longer included in the current version (4.3.14).

I will try if this works with current configuration. But I think the automation will call itself recursively. As long condition blocking works well I see no problem.

@myriad

I configured the aggressive mode for small corrections of the heating behavior, if that is relevant.

I will implement an option to calculate the aggressive mode values to the calibration offset. But I wonder if the Bosch have the ability for calibration and if yes does it work already with AHC?

@myriad

Regarding the Reset Temperature tweak, I would find it handy if, in addition to the reset at the end of schedules or presence

If comfort turns on, eco temperature will be reset. If eco is active, comfort temperature will be reset.
You also can disable this feature and “reset” the temperatures e.g. at night using schedule adjustments.

@myriad

one could also set a timer that starts when a change in the target temperature is detected that does not come from the blueprint itself

That’s not possible atm caused by a home assistant bug. Cant differ between the sources of automation or physical device.

@myriad

Perhaps it would also be useful for other users to be able to set a particular time of day for the reset.

As I said. Just use the schedule adjustments. I will reorder the ui a bit in the future. This is also without any schedules possible.

[panhans]

@cborn

I have scanned the log and I have found one warning regarding the blueprint.

Logger: blueprints.panhans.heatingcontrol
Quelle: components/system_log/init.py:331
Erstmals aufgetreten: 21:32:15 (52 Vorkommnisse)
Zuletzt protokolliert: 21:43:47

AHC - To make Advance Heating Control work properly just setup the Uptime integration.

No need to worry about. It’s just for a better evaluation of durations of e.g. frost protection. You can setup the uptime integration and this warning is gone. It has nothing todo with calculating temperature or something like this.

[stephanschleichstr13]

i found it now, thanks. Is there a way to show in the log the exact automation with this error?

[panhans]

The error was logged by the template engine of home assistant not the automation itself. Only way to avoid this is to catch those errors and throw custom errors / warnings. Home assistant logs are some kind of misleading when it comes to template errors in scripts and automations.

[myriad]

@panhans

I will implement an option to calculate the aggressive mode values to the calibration offset.

That would be neat.

@panhans

But I wonder if the Bosch have the ability for calibration and if yes does it work already with AHC?

Yes, the Bosch thermostats can be calibrated, and it does indeed work with AHC already. I should mention that I updated their software to version 3.05.09 using the scraped zigbee-OTA images provided here: GitHub - Koenkk/zigbee-OTA: A collection of Zigbee OTA files so I don’t know much about previous versions. They have a lot of other settings too, as seen here: https://controlc.com/0f8dd569 or in the picture below.

@panhans

You also can disable this feature and “reset” the temperatures e.g. at night using schedule adjustments.

I hadn’t thought about the schedule adjustments. Nice hint, I’ll try that.

@panhans

That’s not possible atm caused by a home assistant bug. Cant differ between the sources of automation or physical device.

Thanks for the clarification. I’d appreciate it if you could add that to your list of possible future enhancements, provided the bug is resolved. I think a fallback timer would be awesome for occasional manual preheating of rooms or other use cases.

Thanks for your help!

[Michael_Dahl]

Screenshot from today, it did not trigger before i came home:

it’s almost a straight line home, only a few curbs when almost mode (5-700 meters from home)

[tco95ttocs (Mario)]

Could it be, that if the target temp is lower than the real temp, that the “agressive” offset will be substracted from the target temp?
Example:
target (eco): 16,5
Room: 21
agressive offset: 2
new target: 14,5

I think that schould not be! Because the agressive mode is for faster heating and should only be enabled when the comfort temp is active! Otherwise the room will cool down more! Or is there also the range component? So if the room temp nears to 16,5 the offset will be 0 and the new target is than 16,5!?!

[panhans]

@Michael_Dahl

Screenshot from today, it did not trigger before i came home:

Could you also share the screenshot of the history / logbook of the direction sensor for that specific duration? Thank you!

@tco95ttocs

I think that schould not be! Because the agressive mode is for faster heating and should only be enabled when the comfort temp is active! Otherwise the room will cool down more!

My thermostats only react when the temperature differs 1°C. So they also don’t close when the target temperature is reached and the room will overheated.

@tco95ttocs

Or is there also the range component? So if the room temp nears to 16,5 the offset will be 0 and the new target is than 16,5!?!

Exactly, there is a range, e.g +/- 2°C and also the offset 2°C and if the room temperature is in that range no offset is set. Lets say:

Target Temperature (in C°)	Room Temperature (in C°)	Aggressive Target Temperature (in C°)
20	20	20
20	17	22
20	22	20
20	22.5	18

[Michael_Dahl]

[tco95ttocs (Mario)]

thx for the short explanation. normaly the aggressiv mode works as it should.
I only was confused, when the eco-temp is set that it will be lower with the aggressiv offset. Maybe i will see what will happen if the room temp goes down to the eco-temp!