Advanced scheduled heating control with calibration and window detection

[panhans]

Hey, where you want to set the 19.5°C? I have no problem with the slider in the automation itself. When you mean the comfort temperature, than you have to edit your input helper to allow 0.5 steps.

Do you have another automation that sets presets? Or maybe an automation of your bridge? In my opinion the preset is persistent until you set a new one. But If you want to extend the blueprint your right in the action section:

action:
  - service: climate.set_preset_mode
    target:
      entity_id: !input 'heating'
    data:
      preset_mode: 'permanent'
  - service: climate.set_hvac_mode
    target:
      entity_id: !input 'heating'
    data:
      hvac_mode: "{{ mode }}"

  - condition: template
    value_template: "{{ mode == 'heat' }}"
  - delay: 3
  - service: climate.set_temperature
    data:
      entity_id: !input 'heating'
      temperature: "{{ temperatur | float }}"

[diegot (Diego)]

Many thanks for your help! At first in the automation it shows an error when I choose the .5 temperature. After a reset it was working correct m.

The second one is a bit strange, I use the Honeywell Evohome and that system changes the preset to temporary and it shows the schedule of my Evohome in stead off the schedule from HomeAssistant I setup as you mentioned.

This is a problem of my Evohome I guess, so putting the preset on Permanent will make sure that I only follow the HA schedule.

I will try the add on you suggested, tomorrow when I have some time! Thanks

[panhans]

If you want you can test the blueprint with temperature calibration. It isn’t merged in the main branch.
You need a number entity which is part of the device id of the trv. The entity id must contain ‘calibration’. It’s the case if you are using z2m for example. So you just need to define an external sensor and every 10 minutes the trv will be calibrated.

panhans/homeassistant/blob/f86d5b4a7fb60696b25da89d7694fc1960df228f/blueprints/automation/panhans/heating_control.yaml

[dafinkom]

Good day. I really appreciate your work and admire you. I set everything up according to your description. I have only one problem so far. My heads (TS0601_thermostat) are always set to the desired temperature, but the

system mode->heat 
force->open.

I would need to change it to

system mode->auto 
force->normal

… is it possible to modify it somehow? It really looks very usable and is close to perfect for me.

[panhans]

Hey, changed mode to auto instead of heat. Just refresh your blueprint.

//EDIT: I dont know if auto is the right mode. When set my thermostats to auto they regulate themselfes to 20 degrees. I think the auto mode activates the inbuild scheduler of the TRVs. Correct me if I am wrong.

[dafinkom]

apparently you were right about the automatic mode. So I deleted it to be sure and set everything anew and it still opens the heads to the maximum even when the desired temperature is set. Is it possible that the headers do not support it?

[panhans]

I’ve read something about this. It’s a bug in the firmware of the ts0601 trvs but maybe there is a solution for you:

Thermostat won't stop heating (Tuya TS0601)

I managed to solve the problem. The problem was the TRV using an algorithm for heating depending on a profile for an average room with an average count of windows and draught. It’s possible to disable this algorithm by following the guide by brainzap: This document describes on page 7 how to disable this algorithm. This guide is in german. For all non german speaking people, here is the translation: 3.1. The thermostat does not close on reaching the desired temperature The thermostat uses …

Further more the some trvs dont regulate the valves in small steps. Some of these just open up to 100% and close to 0%. So for some devices there is just on and off. I think my hama trvs regulate like this.

[lucidwings]

@panhans

The entity id must contain ‘calibration’.

Could you please provide an example? I don’t quite understand what I should set up in Z2M. Thank you! This blueprint is amazing!

[panhans]

It depends on your trv. If it supports calibration e.g. z2m provides an calibration entity. In its id calibration is set per default.
If its the case you can simply provide an external temperature sensor.

[panhans]

UPDATE: You can now add an external sensor. If your TRVs supports calibration and there is a calibration entity with calibration or offset in its id you are free to add an external sensor. Now the TRVs get calibrated every 10 minutes. It doesn’t matter which zigbee integration you prefer.

[rahulpuk (Rahul)]

First off, thank you for building this blueprint, it’s exactly what’s needed to control TRVs in my house.

Can I request ‘If-then’ style functionality for selecting across multiple Schedulers? The use case is to have user-defined criteria to select between a ‘regular’ schedule for the TRV and another schedule e.g. when the kids are at home for school holidays and room occupancy is different.

Separately, I don’t think my TRVs support calibration based on the entities I can see below.

Is there a way to update the blueprint to calibrate TRVs like mine to external temperature sensors? I guess that for now I could use your blueprint in conjunction with this blueprint to achieve the same outcome? Blueprint to set external sensor temperature to Aqara E1 thermostat · GitHub

[panhans]

Hi Rahul,

yes the aqara e1 has no calibration support yet. Maybe there will be a custom quirk in future. Have an eye on that repo.

Ofcourse you can simply use an additional blueprint for that purpose. Just be sure that temperature and mode will not be set by it and leave the external sensor empty since your trv gets support for calibration.

For your first problem: You want to add a 2nd scheduler for holidays and you need an input (boolean) to switch between the holiday and the regular scheduler. Is that correct?

[rahulpuk (Rahul)]

Yes, in my case since I have only two variants: ‘regular’ and ‘school holidays’ an input boolean would work great.

[kostovster (Ivan Kostov)]

Hey, guys!
panhans, thank you for this amazing blueprint!

On my end, when the automation is enabled, the aqara e1 is set to hvac_mode: ‘off’, disregarding all values in the “Comfort temp” and “Scheduler” helpers.

If you have faced similar issues, can you please share how to overcome them or maybe ideas on how to debug?

[panhans]

Did you specify an input boolean for winter mode? It has to be enabled otherwise the trvs will always be set to off.

[kostovster (Ivan Kostov)]

Actually the only setting I did not try. Thank you for your prompt response

[panhans]

Indeed that should be optional. Will be fixed in the next release.

[panhans]

Here is a beta branch of the blueprint with holiday capability. Feel free to test it and give feedback.

panhans/homeassistant/blob/3237e90160df96349f5e17e3802506c528bd6a79/blueprints/automation/panhans/heating_control.yaml

[panhans]

UPDATE

• 2nd holiday scheduler and input boolean to switch between regular and holiday scheduler
• presence sensor: You can define a time window before your scheduler turns off next time. If that sensor turns off the trv will be set to your minimum temperature

In my case I defined a binary sensor based on the states off my lights. If I turn off the lights two hours before the scheduler turns off the trv will be set to minimum. Thats the case if I want to go to bed earlier.

[CaptainZb]

Thank you for this blueprint which will help me with my heating system.
I don’t have much experience, I’m trying to learn as much as I can.
I have a question, at the moment I have a relay switch that allows me to turn my boiler on or off and TRVs in some rooms. Where should I set my relay swich so that my boiler turns on when the comfort temperature is not reached ?