🔥 Advanced Heating Control

panhans · October 25, 2024, 9:29am

Try to overlap the presence schedule with the normal schedule.

Normal schedule: 08:30 - 21:30
Presence schedule: 21:00 - 3:00

When the normal schedule ends the presence state is already evaluated as true if the room is occupied.

Bonzenpaule · October 25, 2024, 12:30pm

Hi!

First of all thank you very much for this great automation.

I have a question regarding comfort and room temperature. When I disable the room temperature and set no treshold my thermostat won’t be set to my comfort temperature. So the thermostat stays off even though the temperature at the thermostat is below my comfort temperature and the shedule is on.

When I add an room thermostat and a treshold (nothing else changes) the thermostat is set to the comfort temperature and the heating starts. But it only stops at the value of the room thermostat treshold, not at the value of the comfort temperature. So for example if I set the room thermostat treshold to 21,5° and the comfort temperature to 23° the heating stops at 21,5° room temperature. If I set the comfort temperature to 20° the heating doesn’t stop at 20° and stays on until room temperature reaches 21,5°.

So the flexible comfort temperature doesn’t really do anything for me, which is probably not the way the automation is intended.

I have to traces and automationsettings one with room temperature and one without. Any help would be appreciated. I don’t know what I’m doing wrong.

Without Room Temperature: https://controlc.com/7fea0665
With Room Temperature Sensor and Treshold: https://controlc.com/4308757e

panhans · October 25, 2024, 12:49pm

What do you want to achieve? This option is useful for cooling but not for heating. (see the description )

If you want to turn off the thermostats if the room temperature mets the target temperature there is a tweak Off If Above/Below Room Temperature.

Bonzenpaule · October 25, 2024, 12:56pm

Just the second one. I want both thermostats to turn off when the room temperature is reached.

But do I have to set a sensor for the room temperature or stops the automation when the temperature at the thermostat is reached?

panhans · October 25, 2024, 1:27pm

Enable the tweak I’ve mentioned and select a room sensor in the calibration section.

The sensor in the on/off section isn’t needed. I will clean this up with the next version. Atm. this only works with an external sensor and not the thermostat temperatures.

Ohana_Means_family · October 25, 2024, 2:41pm

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.

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. According to the automation, it should be 22 °C.

tco95ttocs · October 25, 2024, 3:54pm

hey guys,

i have defined an outside temperature sensor for all my automations. if the temp is below the threshold all automations start working as they should. But if the temp is above this threshold some of the automations didn’t trigger to go to “off”! What could that be?

Bonzenpaule · October 25, 2024, 4:06pm

Thanks for your assistance! Sadly it still doesn’t work. Here is a Screenshot of my “comfort temperature” (left), the room temperature (middle) and my thermostat (right)

here is the configuration and trace: https://controlc.com/7933e024

Bonzenpaule · October 25, 2024, 4:50pm

Okay! Managed to fix it! The problem was (as it is so often) in front of the screen.

I deleted and rebuild the automation and added the sensor to the calibration and now everything works as intended. Probably made a different mistake somewhere down the line before. Guess thats why it wasn’t working.

Thanks again for your awesome blueprint and for your customer service.

Have great weekend!

Michael_Dahl · October 25, 2024, 5:22pm

Sorry, does not work

Rufan · October 25, 2024, 6:00pm

Hello people

I use the Mitsubishi WF-RAC Integration to control my AC within HA.
I like to use this automation, but have a minor problem.

The integration supports the following modes:
hvac_modes: off, auto, cool, dry, heat, fan_only

I tested running the automation in “auto” mode, this sets the AC into auto mode.
But the downside of my AC in auto mode: is when heating to target and the temp overshoot the target the AC start cooling again. This is a bit waist of energy.

Now I set automation into heat operation, this work like a charm.
But when summer arrive I need to manually set automation to cooling operation.

My question is, can the automation be modified to work in heat and cooling mode?
Not HVACMode.HEAT_COOL this is not supported by the integration.

Thank you in advance.

say1897 · October 25, 2024, 8:15pm

Hello,

I have the following error message in Home Assistant running on a PI5:

Logger: blueprints.panhans.heatingcontrol
Source: components/system_log/__init__.py:331
First occurred: 22:01:34 (3 occurrences)
Last logged: 22:01:34

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

I don’t really understand this error message. Everything seems to be working fine, so I’m not sure if it’s something I need to address. Can someone tell me how to resolve this?

Arvideo · October 26, 2024, 9:38am

You should make 2 automations. One for summer/cooling and one for winter/heating.

You can use the [On/Off Automation Options]> [Winter Mode / Automation Toggle] to alternate between them. (one of 2 inverted).

I also made 2 automations that do the switching of the wintermode for me. (if temp is below treshold for 60min > wintermode on & if temp i above 23 for 60 min > wintermode off)

Rufan · October 26, 2024, 2:16pm

That is a good option until I find a better solution.
In my situation it means 12 automations for heat and cooling.

Thank you for the idea

CarstenJ · October 27, 2024, 10:19am

Hi, first of all, thank you for the great blueprint. The functionality is great, and I was able to activate a schedule, window and door detection, comfort and eco temperatures for each room, winter and party mode without any problems. It’s terrific to have all that in one blueprint.

However, it seems that calibration does not work, so that rooms are generally too cold. I’m using Danfoss Allys which are claimed to be supported, and external Aqara temperature sensors, both integrated via ZHA. The Allys are using an integrated quirk that seems to have come with one of the recent HA updates.

It seems that the Allys have actually never received a calibration value. I’m reading out the AHC values via a sensor, and the last_calibration value is just empty. Is there anything else that I have to set up other than the AHC integration (of course I have specified the external temp sensor there)? I believe that a separate automation that writes external temperatures onto the Ally is not needed when AHC is used, right?

I am using a calibration timeout of 1 minute and a delta of 0.5 °C. Often, the external and internal temperatures are way off, and most of the time the external temperature doesn’t change at all over half an hour or several hours, so timeout and delta should not be a problem. I have tried both covered and uncovered modes in the TRV (quirk) settings, with no noticeable change in behaviour.

What else can I try? Your help is much appreciated - thank you very much!

P.S.: Here’s the latest trace: https://controlc.com/24a4ca34

panhans · October 27, 2024, 12:52pm

Yes, just setup the uptime integration.

Right!

Could you paste this into the template editor, edit the climate entity to yours and post the output here?

{% set climate = 'climate.YOUR_CLIMATE_ENTITY'%}

{{ device_entities(device_id(climate)) |
      expand | selectattr('domain','in','number') |
      map(attribute='entity_id') | list }}

Could you check

CarstenJ · October 27, 2024, 2:25pm

Sure. Here’s the output:

Ergebnistyp: list

[
  "number.thermostat_bad_regelungssollwert_offset_2",
  "number.thermostat_bad_min_heizungssollwertgrenze_2",
  "number.thermostat_bad_max_heizungssollwertgrenze_2",
  "number.thermostat_bad_laderaummittelwert_2",
  "number.thermostat_bad_externer_temperatursensor_2",
  "number.thermostat_bad_beginn_der_ubung_2"
]

Dieses Template überwacht die folgenden Ereignisse, die einen Zustand ändern:

    Entität: binary_sensor.thermostat_bad_montagemodus_aktiv_2
    Entität: binary_sensor.thermostat_bad_vorheizstatus_5
    Entität: binary_sensor.thermostat_bad_warmebedarf_2
    Entität: button.thermostat_bad_identifizieren_2
    Entität: climate.thermostat_bad_thermostat_2
    Entität: number.thermostat_bad_beginn_der_ubung_2
    Entität: number.thermostat_bad_externer_temperatursensor_2
    Entität: number.thermostat_bad_laderaummittelwert_2
    Entität: number.thermostat_bad_max_heizungssollwertgrenze_2
    Entität: number.thermostat_bad_min_heizungssollwertgrenze_2
    Entität: number.thermostat_bad_regelungssollwert_offset_2
    Entität: select.thermostat_bad_anpassungslaufbefehl_2
    Entität: select.thermostat_bad_blickrichtung_2
    Entität: select.thermostat_bad_sollwert_reaktionszeit_2
    Entität: select.thermostat_bad_tastatursperre_2
    Entität: select.thermostat_bad_trainingstag_der_woche_2
    Entität: select.thermostat_bad_ventilausrichtung_2
    Entität: sensor.thermostat_bad_batterie_2
    Entität: sensor.thermostat_bad_hlk_aktion_2
    Entität: sensor.thermostat_bad_lastschatzung_2
    Entität: sensor.thermostat_bad_lqi_9
    Entität: sensor.thermostat_bad_motorschrittzahl_2
    Entität: sensor.thermostat_bad_offenes_fenster_erkannt_2
    Entität: sensor.thermostat_bad_pi_warmebedarf_2
    Entität: sensor.thermostat_bad_quelle_der_sollwertanderung_2
    Entität: sensor.thermostat_bad_rssi_9
    Entität: sensor.thermostat_bad_softwarefehler_2
    Entität: sensor.thermostat_bad_status_des_anpassungslaufs_2
    Entität: sensor.thermostat_bad_vorheizzeit_5
    Entität: switch.thermostat_bad_anpassungslauf_aktiviert_2
    Entität: switch.thermostat_bad_externen_temperatursensor_priorisieren_2
    Entität: switch.thermostat_bad_externer_fenstersensor_2
    Entität: switch.thermostat_bad_interne_fenstererkennung_verwenden_2
    Entität: switch.thermostat_bad_lastausgleich_verwenden_2
    Entität: switch.thermostat_bad_montageart_2
    Entität: switch.thermostat_bad_warme_verfugbar_2
    Entität: update.thermostat_bad_firmware_2

Thanks again!

panhans · October 27, 2024, 2:44pm

The automation is looking for the default exposed entity ids in your case the calibration entity needs to match the keyword external. If you put external anywhere in the following entity_id number.thermostat_bad_externer_temperatursensor_2 like number.thermostat_bad_external_temperatursensor_2 it should work as expected.

But if you like I will make this editable in the next release.

Noorbertt · October 27, 2024, 4:32pm

Anyone using this blueprint with tado? How should I setup? Offset? Tado integration? Tado app should be empty with no heating setting?

CarstenJ · October 27, 2024, 4:41pm

Thank you, this might help. However I will try your solution in the mean time. So if I understand correctly, the whole thing is “disconnected” because the “standard” entities of the Danfoss device got translated into German when I recently added this device. Do I need to “translate back” any other entities to ensure complete functionality of the blueprint, or just the single one you mentioned, given the fact that all my entities currently have German names?

Thanks again very much for your help!