Variable automation for climate regulation in case of open window

Mngsps · December 27, 2022, 12:52pm

Dear all,

I created an automation to shut down my heatings (Fritz DECT 302) in case a window in the room was opened (Shelly DW2) and it works fine. However, I do not like the coding and would appreciate a way to include variable instead of copy and paste it 9 times for all my rooms/heatings…
Any Idea to produce a variable automation for all heatings or a script?

All the best and kind regards for your help
Benedikt

- id: heizung_bad_kinder
  alias: Heizung Bad Kinder
  description: ''
  trigger:
  - platform: state
    entity_id: binary_sensor.tfk_kinderbad_door
    to: 'on'
    for: 00:00:30
    id: window_open
  - platform: state
    entity_id: binary_sensor.tfk_kinderbad_door
    to: 'off'
    for: 00:00:30
    id: window_close
  - platform: state
    entity_id: climate.heizung_kinderbad
    attribute: preset_mode
    from:
    id: preset_mode_change
  condition:
  - condition: state
    entity_id: climate.heizung_kinderbad
    attribute: summer_mode
    state: false
  action:
  - if:
    - condition: trigger
      id: window_open
    then:
    - service: climate.turn_off
      data: {}
      target:
        entity_id: climate.heizung_kinderbad
  - if:
    - condition: trigger
      id: window_close
    then:
    - service: climate.turn_on
      data: {}
      target:
        entity_id: climate.heizung_kinderbad
    - if:
      - condition: state
        entity_id: schedule.heizung_eg
        state: 'off'
      then:
      - service: climate.set_preset_mode
        data:
          preset_mode: eco
        target:
          entity_id: climate.heizung_kinderbad
  - if:
    - condition: trigger
      id: preset_mode_change
    - condition: state
      entity_id: binary_sensor.tfk_kinderbad_door
      state: 'on'
      for: 00:00:30
    then:
    - service: climate.turn_off
      data: {}
      target:
        entity_id: climate.heizung_kinderbad
  mode: single

Hellis81 · December 27, 2022, 1:05pm

We would need to know what the other entities are called and/or a naming scheme.

Mngsps · December 27, 2022, 1:17pm

Could always be like:
climate.heizung.room
and
binary_sensor.tfk_room_door

Hellis81 · December 27, 2022, 3:50pm

Perhaps this works.

You just need to add the other entities in the trigger part

- id: heizung_all_rooms
  alias: Heizung all rooms
  description: ''
  trigger:
  - platform: state
    entity_id: 
      - binary_sensor.tfk_kinderbad_door
    to: 'on'
    for: 00:00:30
    id: window_open

  - platform: state
    entity_id: 
      - binary_sensor.tfk_kinderbad_door
    to: 'off'
    for: 00:00:30
    id: window_close

  - platform: state
    entity_id: 
      - climate.heizung_kinderbad
    attribute: preset_mode
    from:
    id: preset_mode_change
  condition:
  - condition: state
    entity_id: 'climate.heizung_{{ trigger.entity_id | replace("climate.heizung_", "") | replace("binary_sensor.tfk_", "") | replace("_door", "")  }}'
    attribute: summer_mode
    state: false
  action:
  - if:
    - condition: trigger
      id: window_open
    then:
    - service: climate.turn_off
      data: {}
      target:
        entity_id: 'climate.heizung_{{ trigger.entity_id | replace("climate.heizung_", "") | replace("binary_sensor.tfk_", "") | replace("_door", "")  }}'
  - if:
    - condition: trigger
      id: window_close
    then:
    - service: climate.turn_on
      data: {}
      target:
        entity_id: 'climate.heizung_{{ trigger.entity_id | replace("climate.heizung_", "") | replace("binary_sensor.tfk_", "") | replace("_door", "")  }}'
    - if:
      - condition: state
        entity_id: schedule.heizung_eg
        state: 'off'
      then:
      - service: climate.set_preset_mode
        data:
          preset_mode: eco
        target:
          entity_id: 'climate.heizung_{{ trigger.entity_id | replace("climate.heizung_", "") | replace("binary_sensor.tfk_", "") | replace("_door", "")  }}'
  - if:
    - condition: trigger
      id: preset_mode_change
    - condition: state
      entity_id: binary_sensor.tfk_{{ trigger.entity_id | replace("climate.heizung_", "") | replace("binary_sensor.tfk_", "") | replace("_door", "")  }}_door
      state: 'on'
      for: 00:00:30
    then:
    - service: climate.turn_off
      data: {}
      target:
        entity_id: 'climate.heizung_{{ trigger.entity_id | replace("climate.heizung_", "") | replace("binary_sensor.tfk_", "") | replace("_door", "")  }}'
  mode: single

Mngsps · December 27, 2022, 10:05pm

Thank you a lot!

I changed entity names to:
climate.room
and
binary_sensor.tfk_room

and tried to adopt your code suggestion:

- id: heizung_fenster_steuerung
  alias: Heizung-Fenster Steuerung
  description: ''
  trigger:
  - platform: state
    entity_id:
      - binary_sensor.tfk_arbeitszimmer
      - binary_sensor.tfk_kinderzimmer
      - binary_sensor.tfk_bad_kinder
      - binary_sensor.tfk_bad_eltern
      - binary_sensor.tfk_schlafen_kinder
      - binary_sensor.tfk_schlafen_eltern
      - binary_sensor.tfk_waschraum
      - binary_sensor.tfk_ankleidezimmer
    to: 'on'
    for: 00:00:30
    id: window_open
  - platform: state
    entity_id:
      - binary_sensor.tfk_arbeitszimmer
      - binary_sensor.tfk_kinderzimmer
      - binary_sensor.tfk_bad_kinder
      - binary_sensor.tfk_bad_eltern
      - binary_sensor.tfk_schlafen_kinder
      - binary_sensor.tfk_schlafen_eltern
      - binary_sensor.tfk_waschraum
      - binary_sensor.tfk_ankleidezimmer
    to: 'off'
    for: 00:00:30
    id: window_close
  - platform: state
    entity_id:
      - climate.arbeitszimmer
      - climate.kinderzimmer
      - climate.bad_kinder
      - climate.bad_eltern
      - climate.schlafen_kinder
      - climate.schlafen_eltern
      - climate.waschraum
      - climate.ankleidezimmer
    attribute: preset_mode
    from:
    id: preset_mode_change
  condition:
  - condition: state
    entity_id: 'climate.{{ trigger.entity_id | replace("climate.", "") | replace("binary_sensor.tfk_", "") }}'
    attribute: summer_mode
    state: false
  action:
  - if:
    - condition: trigger
      id: window_open
    then:
    - service: climate.turn_off
      data: {}
      target:
        entity_id: 'climate.{{ trigger.entity_id | replace("climate.", "") | replace("binary_sensor.tfk_", "") }}'
  - if:
    - condition: trigger
      id: window_close
    then:
    - service: climate.turn_on
      data: {}
      target:
        entity_id: 'climate.{{ trigger.entity_id | replace("climate.", "") | replace("binary_sensor.tfk_", "") }}'
    - if:
      - condition: state
        entity_id: schedule.heizung_eg
        state: 'off'
      then:
      - service: climate.set_preset_mode
        data:
          preset_mode: eco
        target:
          entity_id: 'climate.{{ trigger.entity_id | replace("climate.", "") | replace("binary_sensor.tfk_", "") }}'
  - if:
    - condition: trigger
      id: preset_mode_change
    - condition: state
      entity_id: 'binary_sensor.tfk_{{ trigger.entity_id | replace("climate.", "") | replace("binary_sensor.tfk_", "") }}'
      state: 'on'
      for: 00:00:30
    then:
    - service: climate.turn_off
      data: {}
      target:
        entity_id: 'climate.{{ trigger.entity_id | replace("climate.", "") | replace("binary_sensor.tfk_", "") }}'
  mode: parallel

but ended up with the failure when reloading automations.yaml

Logger: homeassistant.config
Source: config.py:508
First occurred: 22:59:20 (1 occurrences)
Last logged: 22:59:20

Invalid config for [automation]: Entity binary_sensor.tfk_{{ trigger.entity_id | replace(“climate.” is neither a valid entity ID nor a valid UUID for dictionary value @ data[‘action’][2][‘if’][1][‘entity_id’]. Got None Entity climate.{{ trigger.entity_id | replace(“climate.” is neither a valid entity ID nor a valid UUID for dictionary value @ data[‘condition’][0][‘entity_id’]. Got None. (See /config/configuration.yaml, line 48).

Any idea how to overcome this?

All the best and kind regards for the fast help
Benedikt

123 · December 27, 2022, 10:46pm

A State Condition doesn’t support a template for its entity_id option. Replace the State Condition with a Template Condition.

However, the following State Condition, which also employs a template in entity_id, cannot be easily replaced by a Template Condition. It use the for option which isn’t supported by a Template Condition.

    - condition: state
      entity_id: 'binary_sensor.tfk_{{ trigger.entity_id | replace("climate.", "") | replace("binary_sensor.tfk_", "") }}'
      state: 'on'
      for: 00:00:30

The required Template Condition will need to not only check if the entity’s state is on but that it hasn’t changed in at least 30 seconds by check if the entity’s last_changed value is older than 30 seconds.

Hellis81 · December 27, 2022, 11:18pm

Interesting that there is still bits and pieces that are not templateable in automations these days.

What is this trigger?
When you change preset and the door is open for 30 seconds.
What is the real life scenario this is going to catch?

Mngsps · December 28, 2022, 9:18am

Thank you a lot for your efforts!

The scenario is the following:

I wand the heating (climate entity) to turn of (zero heating, no preset mode) when the window is opened. All windows have door-window contacts (Shelly DW2) and the heatings are controlled by AVM Fritz DECT 302 valve controllers. The delay of 30 seconds was an idea to prevent the trigger from being fired in case of just a short opening (e.g. to ask the kids to come in).
Furthermore, the DECT 302 uses two preset modes (i. e. temperatures to set) in case the heating is on: eco (16 degree in my case) and comfort (21 degree in my case). Preset modes are scheduled during the day to only heat the rooms in times we are normally at home and in this room.

Two issues I needed to overcome are:

When the preset mode changed due to schedule in a situation with an open window, the heating will go to eco/comfort again even if the window is open. So I wanted the automation to again shut the heating off in this case.
When closing the window (action: climate turn on), the turn on action forces the heating to the comfort mode regardless the schedule. Therefore, I needed to check the schedule und change preset mode to eco if necessary (otherwise when opening and closing the window during “eco time”, the heating will be in comfort mode after closing).

The automation initially posted by myself fulfills al these needs but I didn’t like the idea of having separate hard coded automations for every of the 9 rooms.

If there would be a smart way to include all rooms in one automation, this would be great

All the best and kind regards
Benedikt

Possible status attributes of one exemplary heating:

Hellis81 · December 28, 2022, 12:15pm

Ok…
I believe #2 is already covered in your automation as it was.
I believe the only one that is an issue is the #1.
But if the thing is that a scheduled task changes the preset and at the same time as you have the window open to call in the kids, that sounds like a very unlikely event.
But I guess it all depends on how often you call on your kids.

As Taras suggested, you can overcome this limitation with checking the last change of the entity, but if I was you I would try with just checking the state without the for: 30 seconds and see if it really is a issue.

Mngsps · December 28, 2022, 5:45pm

Sorry, maybe I did explain it too complicated.
The 30s delay is needed NOT to start the action because it makes no sense to start the shutdown mechanism if we’re e.g. leaving one room (some windows are door-window combination) to the garden or just shortly opening the window to call the kids in.

#1 addresses the situation when you start the shutdown (open longer than 30s, e.g.
window tilt position during whole night or during daytime) but the schedule changes the preset during that time (e.g. going to bed earlier than the preset change in the evening). In that case, the heating would start again in eco or comfort (depending on the schedule) even if the window is open.

Mngsps · December 28, 2022, 5:47pm

@123 can you help me with these template conditions? I’m not sure how to write them.

Many thanks in advance to the both of you and kind regards
Benedikt

123 · December 28, 2022, 6:44pm

Here’s a more compact version of your automation. Review and test it to confirm it meets your requirements. Report any problems you may encounter with it (I don’t have the means to test its operation).

- id: heizung_fenster_steuerung
  alias: Heizung-Fenster Steuerung
  description: ''
  trigger:
    - id: 'window'
      platform: state
      entity_id:
        - binary_sensor.tfk_arbeitszimmer
        - binary_sensor.tfk_kinderzimmer
        - binary_sensor.tfk_bad_kinder
        - binary_sensor.tfk_bad_eltern
        - binary_sensor.tfk_schlafen_kinder
        - binary_sensor.tfk_schlafen_eltern
        - binary_sensor.tfk_waschraum
        - binary_sensor.tfk_ankleidezimmer
      from:
        - 'off'
        - 'on'
      to: 
       - 'on'
       - 'off'
      for: '00:00:30'
      variables:
        oid: "{{ trigger.to_state.object_id[4:] }}"
        climate: "climate.{{ oid }}"
    - id: 'preset'
      platform: state
      entity_id:
        - climate.arbeitszimmer
        - climate.kinderzimmer
        - climate.bad_kinder
        - climate.bad_eltern
        - climate.schlafen_kinder
        - climate.schlafen_eltern
        - climate.waschraum
        - climate.ankleidezimmer
      attribute: preset_mode
      not_to:
        - 'off'
        - 'unvailable'
      variables:
        oid: "{{ trigger.to_state.object_id }}"
        climate: "climate.{{ oid }}"
        binary: "binary_sensor.tfk_{{ oid }}"
  condition:
    - "{{ is_state_attr(climate, 'summer_mode', false) }}"
  action:
    - choose:
        - conditions: "{{ trigger.id == 'window' }}"
          sequence:
            - service: "climate.turn_{{ iif(trigger.to_state.state == 'on', 'off', 'on') }}"
              target:
                entity_id: "{{ climate }}"
            - if:
                - "{{ trigger.to_state.state == 'off' }}"
                - "{{ is_state('schedule.heizung_eg', 'off') }}"
              then:
                - service: climate.set_preset_mode
                  data:
                    preset_mode: eco
                  target:
                    entity_id: "{{ climate }}"
        - conditions:
            - "{{ trigger.id == 'preset' }}"
            - "{{ is_state(binary, 'on') }}"
            - "{{ now() - states[binary].last_changed >= timedelta(seconds=30) }}"
            sequence:
              - service: climate.turn_off
                target:
                  entity_id: "{{ climate }}"
      default: []
  mode: parallel

EDIT

Correction. Change < to >= in last Template Condition.

Mngsps · December 28, 2022, 8:36pm

Thank you a lot!
It works great, except for timedelta condition.
When there is a change in preset mode during open window, it does trigger the automation but it doesn’t fulfill the three conditions. When removing the condition with the timedelta, it works fine.

Another observation: The automation fires again afer being triggered the first time by itself. I guess this happens since every turn on/off action represents also a change in preset mode, thereby triggering “preset” again (luckily without any action since no condition fulfilled.

One examle (closing window during ‘eco’ time):

This is the first and correct execution triggered by closing the window. Then its triggered twice again (I guess by ‘turn on’ and by changing the preset to ‘eco’):

However with no action in both cases:

123 · December 29, 2022, 2:25am

I corrected the example I posted above. In the last Template Condition, it should be checking if the result of the subtraction is greater than 30 seconds. In the original example I had set it to less than 30 which is incorrect.

The automation’s action controls the state of climate entities that the automation also monitors in its trigger. Therefore it’s natural for the automation to trigger itself. For example, when a window is closed (and remains closed for at least 30 seconds), it will trigger the automation which will proceed to set the climate entity to eco mode (if schedule.heizung_eg is off). If this causes the climate entity’s state to change, it will trigger the automation again.

Mngsps · December 29, 2022, 9:18am

OK, thank you, I got it
Another question:
Is it necessary to have the “from” argument in case of the “window” trigger?
Why I’m asking: Sometimes I found the door-window contacts in status “unavailable” which didn’t bother me since they still immediately changed status when e.g. opening the window. However, in that case the automation wouldn’t be triggered, right?

123 · December 30, 2022, 10:07am

Correct. It won’t be triggered by a state-change from unavailable to on or off. If you want it to be triggered by state-changes from unavailable, remove the from option.