šŸ”„ Advanced Heating Control

Just one question please, instead of using a seperate temperature sensor here I would like to use the temperature sensor of the TRV, is this possible because the only entity I can think about is the ā€˜local_temperatureā€™ but I canā€™t find it back as an entity in the MQTT listing but in Z2M the status shows this

{
    "battery_low": false,
    "boost_timeset_countdown": 0,
    "child_lock": "UNLOCK",
    "comfort_temperature": 20,
    "current_heating_setpoint": 21,
    "eco_temperature": 17,
    "error_status": 0,
    "frost_protection": "OFF",
    "heating_stop": "OFF",
    "holiday_start_stop": "2021/01/01 01:01 | 2021/01/01 01:01",
    "holiday_temperature": 17,
    "linkquality": 163,
    "local_temperature": 17.9,
    "local_temperature_calibration": 0,
    "online": "ON",
    "open_window": "OFF",
    "open_window_temperature": 13,
    "preset": "manual",
    "schedule_friday": "06:00/16 12:00/21 14:00/17 17:00/21 24:00/17",
    "schedule_monday": "06:00/16 12:00/21 14:00/17 17:00/21 24:00/17",
    "schedule_saturday": "06:00/16 12:00/21 14:00/17 17:00/21 24:00/17",
    "schedule_sunday": "06:00/16 12:00/21 14:00/17 17:00/21 24:00/17",
    "schedule_thursday": "06:00/16 12:00/21 14:00/17 17:00/21 24:00/17",
    "schedule_tuesday": "06:00/16 12:00/21 14:00/17 17:00/21 24:00/17",
    "schedule_wednesday": "06:00/16 12:00/21 14:00/17 17:00/21 24:00/17",
    "system_mode": "heat",
    "working_day": "mon_sun"
}

May I misunderstood you. Do you have working TRVs with climate entities in home assistant and a boiler switch you want to toggle?

If yes, please navigate to your developer tools, state section filter for your climates and check if they own the attribute hvac_action.

1 Like

yes sir, but with the climate.radiator_badkamer_beneden it does not work, it wonā€™t turn on the heater switch, thatā€™s the strange part

Sorry I donā€™t understand how a physical thermostat should trigger a heater. Lets write DM please. This is offtopic an bloats this thread.

1 Like

Hello could you change ā€œoutside temperature tresholdā€ to be an entity


And also ā€œaway temperature offsetā€ to be also an antity but not offset but to be real temperature like 18degres C.

I want to achieve this:

That people can set it as they want all these temperatures.
Thank you. Youā€™re doing great job.

Hello!

First of all thanks for a great blueprint sharing. I have a question. Iā€™m using Winter mode for general enable of all my heating thermostats during winter/heating season. Is it possible to add another Input_boolean for controling some of thermostats, as I want to control few thermostats that depends on another input_boolean.

@marekpro
Iā€™d put this on my list. :wink:

@bojke
I think this is for the most users a bit confusing and hard to realize with the possibilities of jinja and yaml code. Couldnā€™t you just clone your automation, remove the climates you donā€™t want for the other input boolean and just set it?

Hi,
I just updated to the current v5.x version and migrated all of my automations from the v4.x version. I basically opened the old automation twice and changed to the new blueprint while copying over the settings from the old one in the other tab. Long story short I have 2 rooms which would require a guest mode to be turned on to run at the comfort temperature. This worked fine with the v4.x version and I checked that guest mode is not set (turned off) but with the new blueprint the rooms were heating up anyways although they should not. Did something change here with the pure guest mode or am I missing something?

Could you share your automation configuration for a room?

Sure, here we go:

alias: GƤstezimmer
description: ""
use_blueprint:
  path: panhans/advanced_heating_control.yaml
  input:
    input_trvs:
      - climate.heizkorper_gastezimmer
    input_temperature_comfort_static: 21
    input_temperature_eco_static: 15
    input_temperature_comfort: input_number.gastezimmer_manual_comfort_temperature
    input_adjustments:
      - time: "00:02"
        scheduler: Arbeitswoche
        comfort: "18"
        calibration: "off"
      - time: "06:00"
        days:
          - Mon
          - Tue
          - Wed
          - Thu
          - Fri
        scheduler: Arbeitswoche
        comfort: "17"
        calibration: "off"
      - time: "20:00"
        days:
          - Sun
          - Mon
          - Tue
          - Wed
          - Thu
        scheduler: Arbeitswoche
        comfort: "22"
        calibration: "off"
      - time: "22:30"
        days:
          - Sun
          - Mon
          - Tue
          - Wed
          - Thu
        scheduler: Arbeitswoche
        comfort: "20"
        calibration: "off"
      - time: "00:30"
        days:
          - Sat
          - Sun
        scheduler: Arbeitswoche
        comfort: "18"
        calibration: "off"
      - time: "10:00"
        days:
          - Sat
          - Sun
        scheduler: Arbeitswoche
        comfort: "17"
        calibration: "off"
      - time: "21:30"
        days:
          - Fri
        scheduler: Arbeitswoche
        comfort: "22"
        calibration: "off"
      - time: "23:00"
        days:
          - Fri
        scheduler: Arbeitswoche
        comfort: "20"
        calibration: "off"
      - time: "00:30"
        scheduler: Feiertag/Urlaub/Krankheit
        comfort: "18"
        calibration: "off"
      - time: "10:00"
        scheduler: Feiertag/Urlaub/Krankheit
        comfort: "17"
        calibration: "off"
      - time: "21:30"
        scheduler: Feiertag/Urlaub/Krankheit
        comfort: "22"
        calibration: "off"
      - time: "23:00"
        scheduler: Feiertag/Urlaub/Krankheit
        comfort: "20"
        calibration: "off"
    input_mode_guest: input_boolean.guest_at_home
    input_schedulers:
      - schedule.arbeitswoche
      - schedule.feiertag_urlaub_krankheit
    input_scheduler_selector: input_select.zeitplan_heizprofil
    input_liming_protection: true
    input_liming_in_winter: true
    input_mode_winter: input_boolean.heizmodus
    input_mode_outside_temperature: sensor.gw1100a_outdoor_temperature
    input_mode_outside_temperature_threshold: 20
    input_people_entering_home_duration:
      hours: 0
      minutes: 1
      seconds: 0
    input_people_leaving_home_duration:
      hours: 0
      minutes: 5
      seconds: 0
    input_proximity_distance: 5000
    input_proximity: 89a390e651335751f50b7b10d4a81c0b

I guess itā€™s your proximity sensor, right? It got handled like a person now. So when youā€™re home comfort heating is set.
Did you use proximity in this configuration? If yes it could be that in v4 the comfort was only set if someone is on way home. But if home it has no impact anymore?

But maybe you could go a step further and share just a trace log. Thanks!

You mean, I should not set a proximity sensor at all? The way it used to work was when the guest at home mode was turned on it used the scheduler and heated the room accordingly. If disabled the room remained at the eco temperature. So if I understand you correctly, not setting the proximity sensor would do the trick?

1 Like

No, my guest mode entity was not enabled.

I think Iā€™ve fixed this now, but I wonā€™t know for sure until nobody is at home again. Iā€™ve now got the target temperature in all rooms reacting in the same way and in the way I want them too.

Itā€™s quite easy to miss a setting when your creating as many automations as I have.

1 Like

Stupid question: Since the tracelog is rather big, where would be the correct place to put it? :thinking:

For example here.

Hi again @panhans,

im still struggling to setup the new V5 to work as V4 before.

Im somehow stumbling around with the Comfort/ ECO / Away Temperautresā€¦

I just want it so:

At home and in the room 21Ā°C
At home but no presence 19Ā°C
No one at home 17Ā°C

how Iā€™m able to achieve this within V5?

Edit: I found that we had such a discussion already in April this year. But somehow your suggestion you had:

Nobody home ā†’ eco temp
Home but no presence detected ā†’ comfort temperature - away offset
Home and presence detected ā†’ real comfort temperature

is not really working in V5 anymore. Was there something changed between V4 to V5?

Unfortunately, the calibration of the second TRV does not work. It retains the internal temperature measured on the TRV. The TRV is set to external. Aqara TRV.

alias: šŸ”„AHC Flur OG
description: ""
use_blueprint:
  path: panhans/advanced_heating_control_dev.yaml
  input:
    input_trvs:
      - climate.thermostat_flur_og
      - climate.thermostat_pc_zimmer
    input_temperature_sensor: sensor.thermometer_flur_og_temperature
    input_temperature_eco_static: 20
    input_persons:
      - person.chris
    input_people_entering_home_duration:
      hours: 0
      minutes: 1
      seconds: 0
    input_people_leaving_home_duration:
      hours: 0
      minutes: 1
      seconds: 0
    input_schedulers:
      - schedule.zeitplan_nachtabsenkung
    input_away_offset: 3
    input_away_scheduler_mode: true
    input_windows: []
    input_windows_reaction_time_open:
      hours: 0
      minutes: 0
      seconds: 1
    input_windows_reaction_time_close:
      hours: 0
      minutes: 1
      seconds: 0
    input_calibration_timeout:
      hours: 0
      minutes: 0
      seconds: 2
    input_calibration_delta: 0
    input_mode_outside_temperature: sensor.aussensensor_balkong_temperature
    input_mode_outside_temperature_threshold: 18
    input_calibration_key_word: external

Thank you for your answer,
I have now set to heating, as my thermostat now shows me the manual mode, furthermore I have not made any changes except for opening.
Do you have any beginnerā€™s tips for optimizing the thermostats?
Greetings

@Break
Could you share your current configuration in yaml?

@Ohana_Means_family
Are you on the latest stable? Looks like youā€™re using still the dev version. Did you also check if the calibration entity has external in itā€™s id? No other entity of this thermostat should have this keyword in its id.

@cgott82
Not really. I own some Tuya TRVs and now Sonoff. My Tuyas needs aggressive mode. The Sonoff TRVs are working fine without any tweak. It depends as always. :wink:

Here my Room as example:

alias: šŸ”„ AHC Martin
description: ""
use_blueprint:
  path: panhans/advanced_heating_control.yaml
  input:
    input_trvs:
      - climate.heizung_martin
    input_temperature_sensor: sensor.zsensor_martin_temperatur_temperature
    input_temperature_eco_static: 17
    input_temperature_comfort_static: 21
    input_adjustments: {}
    input_persons:
      - person.daniela
      - person.martin
    input_presence_sensor: binary_sensor.mmwave_presence_sensor_martin_belegung
    input_presence_reaction_on_time:
      hours: 0
      minutes: 0
      seconds: 10
    input_presence_reaction_off_time:
      hours: 0
      minutes: 5
      seconds: 0
    input_away_offset: 2
    input_away_presence_mode: false
    input_windows:
      - binary_sensor.fenster_martin
    input_liming_protection: true
    input_liming_in_winter: false
    input_mode_winter: input_boolean.sommer_winter
    input_mode_outside_temperature: sensor.gw2000a_outdoor_temperature
    input_mode_outside_temperature_threshold: 20
    input_generic_calibration_offset: 5

I already played with the input_away_presence_mode: false but no changes at all there.