Coupling two thermostatic valves

Configuration
1

Hi,
I have a room with two radiators. Each of them mounts a z-wave thermostatic valve, but it makes no sense to me to have different control over the two valves. I have tried the following automation in order to couple the two temperatures: as one is changed the other follows, but it just seems not to work at all. What am I doing wrong?


- id: '1613419540106'
  alias: Livingroom radiators coupling
  trigger:
  - platform: state
    entity_id: climate.radiator_livingroom_sx,climate.radiator_livingroom_dx
    attribute: temperature
  action:
  - service: climate.set_temperature
    target:
      entity_id: '{{ thermostats|reject(''eq'', trigger.entity_id)|list }}'
    data:
      temperature: '{{ trigger.to_state.attributes.temperature }}'

I have also tried the following unsuccessfully:

- id: '1637327773954'
  alias: Livingroom radiator master sx
  description: ''
  trigger:
  - platform: state
    entity_id: climate.radiator_livingroom_sx
    attribute: temperature
  condition: []
  action:
  - service: climate.set_temperature
    target:
      entity_id: climate.radiator_livingroom_dx
    data:
      temperature: '{{ states(''climate.radiator_livingroom_sx'', ''temperature'')
        | float }}'
  mode: single
2

Creating a group doesn’t work?

3

Yes, I tried that but it did not work :frowning:

4

What exactly doesn’t work?
If you create a group with the two entities, it should create a group entity you then interact with

group:
  climate:
    name: Climate
    entities:
      - climate.radiator_livingroom_sx
      - climate.radiator_livingroom_dx
5

Thermostat lovelace card doesn’t allow to put groups as entities.

6

I tried the following approach throught an automation but it doesnt work, what am I doing wrong?
Here’s my code:

- id: '1637327773954'
  alias: Livingroom radiator master sx
  description: ''
  trigger:
  - platform: state
    entity_id: climate.radiator_livingroom_sx
    attribute: temperature
  condition: []
  action:
  - service: climate.set_temperature
    target:
      entity_id: climate.radiator_livingroom_dx
    data:
      temperature: '{{ states(''climate.radiator_livingroom_sx'', ''temperature'')
        | float }}'
  mode: single
7

I’d use something like:

{{ states.climate.radiator_livingroom_sx.attributes.temperature | float }}
8

Nothing… :frowning:
Maybe I have to wait for the thermostatic valve to wake up? Or on lovelace it shows the set temperature regardless of what is currently shown on the thermostatic valve?

9

This is the result of the trace of the automation, if usefule

Executed: November 21, 2021, 1:12:49 PM
Result:

params:
  domain: climate
  service: set_temperature
  service_data:
    temperature:
      '[object Object]': null
    entity_id:
      - climate.radiator_livingroom_dx
  target:
    entity_id:
      - climate.radiator_livingroom_dx
running_script: false
limit: 10
10

Tested on my configuaration and this code worked for me:

  - id: '1637327773954'
    alias: bedroom sync
    description: ''
    trigger:
    - platform: state
      entity_id: climate.valve_mirek
      attribute: temperature
    condition: []
    action:
    - service: climate.set_temperature
      target:
        entity_id: climate.valve_bedroom
      data:
        temperature: >
          {{ state_attr('climate.valve_mirek', 'temperature') | float }}
    mode: single

After changing target temp on climate.valve_mirek it took ~30 seconds to get this reflected on climate.valve_bedroom.

1 Like
11

Nothing on my side :frowning: