🔥 Advanced Heating Control

Since the Blueprint Sensor Template i get ofter this Error, with the old one not:

Logger: homeassistant.helpers.template
Quelle: helpers/template/__init__.py:1750
Erstmals aufgetreten: 07:55:19 (17 Vorkommnisse)
Zuletzt protokolliert: 08:08:01

Template variable error: 'trigger' is undefined when rendering '{{ trigger.event.data.is_person_defined }}'
Template variable error: 'trigger' is undefined when rendering '{{ trigger.event.data.state_proximity_way_home }}'
Template variable error: 'trigger' is undefined when rendering '{{ trigger.event.data.active_party_entity }}'
Template variable error: 'trigger' is undefined when rendering '{{ trigger.event.data.state_window }}'
Template variable error: 'trigger' is undefined when rendering '{{ trigger.event.data.is_guest_mode }}'

Please update the blueprint. As stated in the changelog, the entity IDs of the offset entities must now contain the word “offset” in order to generalize the calibration and avoid having to maintain multiple manufacturer groups.

The rule for recognizing the offset entity is now as follows: The entity ID must contain either “offset” or “calibration,” but not the word “external.” So an update would solve your problem.

I will check this.

//EDIT: Did you already disable your old sensors? I had this problem with them but not with the blueprint based. However, if the problem persists, I will revise the blueprint again.

Definitely the Sonoffs:

  • Regular updates
  • Support offset and external temperature input
  • Precise valve control (not just simple on and off)
  • They are quiet
  • You can sometimes get them for €15-20

But I must also say that I haven’t been able to test Tado, Eve, and co. myself. :wink:

1 Like

I updated the calibration entity key word to offset (even though, the TRVZB has no entity that contains the work offset)

For the external thermometer, do I need to have an automation which updates the _external_temperature_input entity of my thermostat, or is that all done in the automation?

The thing im wondering the most about, is that the _local_temperature_calibration (which seems to be found correctly) is constantly at the max of +12.7°C. But I can’t quite get how this number comes to be. My thermometer measures e.g. 20°C, i have a comfort temperature set of 23°C, but still the resulting thermostat temp is only 17°C, meaning the heater is completely off. So I think there must be something configured weirdly here…

image

No, you don’t have to edit the keyword but the entity id of the offset entity itself. But this is no longer the case. Stay with your old configuration and simply update the blueprint.

If you want to switch to external temperature just set the key word to e.g. ‘external_temperature_input’ and set the ‘old’ offset entities to 0 manually.
The rest will be done by the automation. (ZHA is untested but should work, too (never got feedback of a zha user with sonoffs))

It definitely is setting something, I’m just not understanding the gap of 6°C between my set comfort temperature, and the temperature set on the thermostate.
T_room = ~20°C
T_comfort = 23°C
T_setOnThermostate = 17°C

I think this is why. Away mode seems to be on. A trace log would be helpful.

1 Like

Im using primary the old, and for Tests 1 new+old

Thanks a lot, that did the trick, or rather, I also had the Presence Away Mode active, even though I only have a proximity sensor up (since that feels like it’s doing the same, but with the added benefit of starting heating, when I start coming home). After I disabled that option (keeping Schedule Away Mode enabled) it now seems to be working!

Presence away Mode works with presence sensor. Schedule away Mode with person proximity. Maybe I have to rename it but the description should clearify.

1 Like

@panhans The documentation link in #1 is wrong. Should probably be 🔘 Thermostats & Sensors - Panhans | Blueprints and Snippets

What is the recommended way to update the blueprint? In my case I would be starting with 5.3.4 in the majority of cases but I have some older ones. Thanks in advance.

I need to set the target temperature into a helper, but find no way to do it (and no non ubiquitous search words to search here).

Does not work:

action: input_number.set_value
metadata: {}
target:
  entity_id: input_number.target_az
data:
  value: "{{ temp_target|float(18) }}"

Hey, is it possible to have different temperatures set for different thermostats / rooms? Thanks!

yes its possible, than each thermostat need its own automation!

Hello Panhans
Thanks again for this really great blueprint. Just found out that i could also use a ping entity instead a person :slight_smile:. This is very helpfull in my office to use the ping identity from my notebook to set my heating control.
Donation (52P14059TJ9810721) sent.

Best regards
Bernd

1 Like

Hello. Thank you for this great automation. Can I ask why the “Off instead of Eco” setting has been removed in the latest version? Now my ACs are permanently on at all hours, instead of turning off when the schedule or presence changes. Unless there is another setting I am missing?

Thanks again.

I have imported the blueprint and im having difficulty getting it to work. I have a friend who has it as well and his blueprint looks way different to mine. I cant see a dropdown button named “Temperature” fx.
What am I doing wrong?

Ok, thanks. I need to update the whole documentation as well.

Depends on your configuration and if it hits a breaking change. Hard to tell. But you can copy an rename your old blueprint as backup before updating.

I’m sorry. I don’t quite understand. :sweat_smile:

As @tco95ttocs mentioned, just setup one automation per room.

Thank you very much! I also recommend to use device trackers instead of persons for this purpose.:pray:

As I mentioned in the changelog and again in the first post :wink: :

I can’t remember this. Maybe he uses a custom selector or another blueprint?

First of all, many thanks to you @panhans for all the work. I really appreciate it when someone puts so much time into something.

I have now saved your blueprint for all thermostats and configured it accordingly. The only thing that is not yet entirely clear to me is how I can set it so that, for example, when the room temperature is 18 degrees and the target temperature is 20 degrees, the thermostat knows that when I enter the room, it should not only open to 50% but directly to 100% so that it warms up quickly.

Where do I need to make which settings for this? The Pesimitic setting at (Dynamic Valve Positioning / PID) ? My Valve opening positions are in etntities like that: sensor.thermostat_eg_buero_position and it goes in 25% steps. Or is it possible to use the [Boost heating (binary)] Mode of my thermostats in any way in the blueprint?

And one more question… What’s the best way to do this… If someone goes to bed and an external helper has been switched on, how can I set a specific temperature for as long as this helper is switched on?

Many thanks in advance.

INFO: These are the Thermostats I have: Moes BRT-100-TRV control via MQTT | Zigbee2MQTT

1 Like

Just have a look into the Dynamic Valv Positioning section. Set the Max Opening Valve Position to 100% and the Positioning Temperature Difference to that value when the valve should close slowly. That means if you set it to 1° and your room temperature is 1° below the target temperature. The valve will close slowy the closer it gets to the target temperature.
But I don’t know how this works with your thermostat since min supports a step size of 1%. Just set it to 20% step size and report back if it works. Also have a look into your logs if you get errors. But good to know there are predefined step size. I will put this on my list to avoid issues here.

Just create an input boolean helper or a timer, whatever you like with your desired target temperature at the end in its name like Go to sleep 18 and set this as a party mode entity. If you toggle the helper on it will override the target temperature and set it to 18° as long as it is on or active.

//EDIT: Does you thermostat/climate support one single target temperature? regarding the docs it only supports a minimum and maximum temperature. At the moment the blueprint wont support this kind of setting temperatures.