🔥 Advanced Heating Control

as far as I understood … and how I am using it:
Comfort heating is for when you want to have it cozy, comfortable and warm.

It is activated by schedulers (presence sensors, party mode, etc. ).

If comfort heating is not active then static minimum temperature is set / but heating is still active.

The Comfort Heating Plan allows different Comfort Temps through the day … for example i like to have it a little cooler through the day and warmer late nights. (though i set this manually through an input_number)

[V4 beta]

Starting just now… Thinking about it, I am not sure it will fit my need. Would it make sense to use the proximity sensor to exit the frost protection mode? Another possible way would be to use the distance as a gradient between frost protection and either minimum or comfort. Personally, I disagree with using “on way home” as equivalent to being home.

Comfort Heating is the temperature you want to heat your room too (sometimes called the set temperature), in your case 20*C

[V4 beta]
I also see that the frost protection has precedence over the proximity. In my case, I would potentially (might need more reflection) like to see it as follows:

  • home: comfort,
  • away for short period or close by: minimum,
  • away for long and not close by: frost protection.

There might be an option of introducing a temperature gradient in function of the distance, but I am not sure on how to do it.

@panhans i don´t know if you also want to support other options. For example the Bosch Thermostat II (BTH-RA)? Because this has the ability to set a remote temperature. So there is no need to use the calibration. Bosch BTH-RA control via MQTT | Zigbee2MQTT
So it is similar to the Aqara request some post up

Just a note for Popp/Hive/Danfoss users: if you are on ZHA, it takes some tweaking to enable external temperature support. There is a set of PRs in ZHA and HA core that is being worked on to fix that, but right now you need to use ZHA toolkit (or Z2M of course). See here.
Since the PR’s seem to be in an advanced state and will likely mess up any ZHA toolkit hacked config, I’m currently holding out for them to be merged before I start implementing this blueprint.

Thanks, I just thought you’d have 1 temp, but it’s good to have a choice.

Ideas are always welcome. I just thought that people starting way home e.g. from work and meanwhile heating starts so they arrive and everything is heated to comfort temp.

Haha, I had the same idea. Maybe a small experiment when my refactoring is ready.

If there is somebody out there who owns those thermostates and can help me debugging and function testing, I will implement this.

Just wonder if the current danfoss / popp / hive implementation works. Got no feedback since I’ve updated the calibration.

1 Like

@panhans Can you tell me why in this case the Up-heating Generic Calibration was activ? the temp was allready reched at this time, upheating was higher than 0,7°C (normally he is max 0,5 C upheating, but this time it was round about 1C)

1 Like

i can test this for the Bosch and the Aqara TRVs. I use for my environment Z2M but i should be able to test some things with ZHA.

1 Like

In your trace your thermostat was set to 28°C. The “normal” temperature with the offset.

"domain": "climate",
"service": "set_temperature",
"service_data": {
    "entity_id": "climate.wohnzimmer_comet_dect",
    "temperature": 28
}

Here is the raw data:

"current_valve": "climate.wohnzimmer_comet_dect",
"current_valve_temp": 28.5,
"step": 0.5,
"sensor_temp": 21.6734388888889,
"min_temp_r": 8,
"max_temp_r": 28,
"new_temperature": 28

Your sensor timeout is set to 1 minute.
If the sensor temperature changes several times in less than a minute, the trigger may not be activated until much later. This can happen if the temperature rises quickly.

1 Like

Very strange, because you see in my screen the blueprint sends 30°C and not 28°C to my Thermostat.
Also the overheat from 0,7°C is strange.

This Problem was only yesterday, we will see. Maybe a hangup.

Thanks for checking

Hi there panhans!

Two questions:

  • do you know if this integration works well with this blueprint? Airzone - Home Assistant I’ve started to test it, and it looks like it’s working, and the integration actually creates a thermostat for each room, but the system is an air heating one, hence the valve concept does not apply all that well…
  • also, is it expected that, when using a comfort template, heating party will revert back to the static comfort temperature when disabled? I remember you saying above that you wanted to refine the temperature handling, so maybe that is something you had already identified.

Thanks!!

Can you tell me when the blueprint is triggered? (Sometimes i have no Run over 15 min.
My Thermostat Trigger time is each 15 min and the right temp on the Thermostat has mostly at night 30 min delay.

Hello

Is there a way to reduce the temperature at night or it is always the Eco temperature?

The automation trigger depends on your configuration. But mostly every entity you specify in options is also a trigger.
Automation gets triggered when:

  • scheduler switches its state
  • scheduler switched to another
  • presence turns on/off
  • window closes / opens

Do you use Fritz Dect Thermostats? Are they only changing on timestamps like 15:00, 15:15, 15:30? Maybe this blueprint needs another modifier for this thermostats so the target temperature will change some seconds earlier before scheduler switched its state or some kind of periodical trigger.
So atm you have to set the schedule times 30min before the real schedule starts?!

Atm the only possibility is to use v4 and select an input helper for minimum temperature. Then you need a 2nd automation to set the value of this entity timebased. But it will be possible in future to set this right out of the blueprint.

1 Like

Yep, its fritzdect (comet dect), i will check the exactly timestamps for changes

Hi again @panhans,

still testing your blueprint with my Airzone (Airzone - Home Assistant). I’ve noticed they HVAC system does not get started by the automation, and I suspect it is because this setting

⚙️ Off Instead Of Minimum Temperature
If enabled your climates turn off instead of lower temperature to minimum temperature.
 

actually was interpreted as HVAC = off, as a result of that setting.

I’ve now switched that setting to off and I wonder if I should rather add a custom action to force HVAC to heating, when the automation gets triggered.

Any thoughts?

The timestamps for the comet dect syncs are the following:
xx:32
xx:47
xx:02
xx:17

1 Like

@panhans Do you have an idea to optimize our “calendar.get_events” template´?
i have currently 3 evetns in this template, 1 of them should only run in the time of the event and than back to the “default” scheduler, this is only work when this get_event do check the event start and end times, can you optimize this?
i hope you understand what i want :slight_smile: