Using another Temperature Sensor as a reference for my Thermostats

Configuration
, , ,
1

Hi I am trying to find a really simple way to combine my Aqara room sensors with the Devolo - Z-Wave Thermostats. Instead of using the sensor that comes within the Thermostate I would rather use the room tempeature sensor from Aqara which is located at a better location within the room. How do I do this?
The Climate BluePrints seem to be far too advanced for this and they overwhelm me with functionalities which I am afraid to use at this stage.
So basicly it is just the entity of this sensor:

climate.devolo_thermostat_09356

. I can only find this info in my attributes (looking in the Developer Tools) but I don’t know how to use the aqara sensor as this reference instead.

sensor.lumi_lumi_weather_2f12c902_temperature

There must be a simple way to do this.
Thank You for helping me out.

2

Have you looked at the generic thermostat integration?

3

O no, I shall look at it thoroughly tomorrow.
Thx

4

I just checked the Generic Thermostat and tried to set it up with the following settings.

climate:
  - platform: generic_thermostat
    name: Badtest
    heater: climate.devolo_thermostat_09356
    target_sensor: sensor.lumi_lumi_weather_2f12c902_temperature

But unfortunately that does not work at all.
This is just the minimal configuration but it does not get me anywhere.

5

You are on the right way. You just need a lot more configuration :slight_smile:

I would suggest you add a input boolean that the generic thermostat switches as the heater.
That way when the boolean flips on/off you can trigger an automation to set the temperature of the TRVs to {{ generic thermostat temperature + 5 }} as the target temperature.
Because you set the target temperature above what the generic thermostat asks for the TRV will remain on even if the sensor on the TRV has reached the temperature.

And when the boolean goes off you can switch off the TRV or set it to a lower coast value.

And you can easily expand this automation with presence and such.

6

Ok so after giving it some thinking I guess I know what you mean. Technically
the thermostat is just a simple On-Off Switch (on if the target temp is below the desired room temperature and Off if it is above {{ generic thermostat temperature + 5 }} is just that it doues not keep turning in and off all the time (I think it is called Hysterese in Gerrman). What does TRV mean?
And you think that when adding a boolean I will actually get a new entity to use within Home Asisstant after correctly setting up the generic Thermostat?

7

TRV stands for Thermostatic Radiatior Valve (or something like that).

You can use the thermostat card with the generic thermostat, to control it from your dashboard.

image

This also includes a history display:

image
image743×646 26.5 KB

8

As Stiltjack said.
It’s the thing you mount on the radiator that actuates the closing pin on the radiator.

Yes you make it a on-off essentially. But off can also be 15 degrees to if you are still home and 0 if you left the home.
We have ours set up to be generic thermostat +5 and when the generic thermostat switches off the radiators are set to 0.

They keep the temperature good. My TRVs are getting worn in some of the rooms and are not always closing the valve fully. And sometimes the sun is shining and heats up the rooms.

image
image1266×446 36.3 KB

9

Sorry, I haven’t gottten any further rhen this for now as I was quite busy.

climate:
  - platform: generic_thermostat
    name: Badtest
    heater: climate.devolo_thermostat_09356
    target_sensor: sensor.lumi_lumi_weather_2f12c902_temperature

where do I add the input boolean? So what I wanna do is that the TRV is using the aqara sensor target_sensor: sensor.lumi_lumi_weather_2f12c902_temperature
rather then the internal sensor and then adjusts the
heater: climate.devolo_thermostat_09356
accordingly.
Do I need an automation or do I just have a helper to combine the sensor from aqara and the switch from devolo?
I am confused. Help or an example would be greatly apppreciated. Once I got that I could use that in several places arround the house.

10

So generic thermostat something like this:

climate:
  - platform: generic_thermostat
    name: Badtest
    heater: input_boolean.trv
    target_sensor: sensor.lumi_lumi_weather_2f12c902_temperature

You might what to add some of the other parameters also such as target temp, hot and clod tolerance.

Then the automation something like this:

description: ""
mode: single
trigger:
  - platform: state
    entity_id:
      - input_boolean.trv
    to: "on"
    id: "on"
  - platform: state
    entity_id:
      - input_boolean.trv
    to: "off"
    id: "off"
  - platform: state
    entity_id:
      - zone.home
    to: "0"
    id: "nobody_home"
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - "on"
        sequence:
          - service: climate.set_temperature
            target:
              entity_id: climate.devolo_thermostat_09356
            data:
              temperature: "{{ state_attr('climate.badtest', 'temperature') |float + 5 }}"
      - conditions:
          - condition: trigger
            id:
              - "off"
        sequence:
          - service: climate.set_temperature
            target:
              entity_id: climate.devolo_thermostat_09356
            data:
              temperature: 15
      - conditions:
          - condition: trigger
            id:
              - "nobody_home"
        sequence:
          - service: climate.set_temperature
            target:
              entity_id: climate.devolo_thermostat_09356
            data:
              temperature: 0

This means it’s off when nobody is home, it’s on with generic temperature +5 when heating the room, and when the room is “hot” it idles at 15 degrees

11

Ho
I added the sensor as shown in the
configuration.yaml

- platform: generic_thermostat
    name: Badtest
    heater: input_boolean.trv
    target_sensor: sensor.lumi_lumi_weather_2f12c902_temperature

Unfortunately the input_boolean.trv is not shown in my entites.
Therefore my automation does not work.

image
image1249×485 21.6 KB

Looks like I need another helper.

12

Yes.
input_boolean.trv. Create the helper and try it again.

13

I tried again the automation seems to be changing.
I added a helper:

image
image1168×126 5.03 KB

, however it loks different than the other sensor which I origionally have.
image
image1144×587 32.9 KB

The right one does not have a color indication. So I am not quite happy with the result yet. . .

14

That’s because it’s Aus.
Turn it on and it will be orange.

15

I did, but it is still shown as idle.

image
image1000×573 29.5 KB

I think my problem is that I chose the wronhg helper. The automation does not work as expected. It does not trigger, bevause input_boolean.input_boolean_trv wont`t change.
My automation:

alias: "Handtuchheizung "
description: ""
trigger:
  - platform: state
    entity_id:
      - input_boolean.input_boolean_trv
    to: "on"
    id: "on"
  - platform: state
    entity_id:
      - input_boolean.input_boolean_trv
    to: "off"
    id: "off"
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - "on"
        sequence:
          - service: climate.set_temperature
            target:
              entity_id: climate.devolo_thermostat_09356
            data:
              temperature: >-
                {{ state_attr('climate.handtuchheizung_neu', 'temperature')
                |float + 5 }}
      - conditions:
          - condition: trigger
            id:
              - "off"
        sequence:
          - service: climate.set_temperature
            target:
              entity_id: climate.devolo_thermostat_09356
            data:
              temperature: 15
      - conditions: []
        sequence:
          - service: climate.set_temperature
            target:
              entity_id: climate.devolo_thermostat_09356
            data:
              temperature: 0
mode: single

The problem is that the trigger does not work.

 input_boolean.input_boolean_trv

is never on.
I added input_boolean.input_boolean_trv as a helper - type switch. I gave it a name and an icon.
Whar stupid mistake did I make?
Thanks

16

What happens if you move the target temperature up/down above/ below the room temperature?
Does this change the state of the boolean?

17

It does not do anything to the automation. I can only manually trigger the automation and not by changing the dial on the climate card.
For some reason the Badtest is still in my entities and but I have no way to really getting t rid of it. It is not shown in the configuration. yaml
Im confused…

18

I’m not talking about the automation.
Does the input boolean change when the generic thermostat is changed. Lets start there.
Have you reloaded the generic thermostat yaml to make sure everything is correct?

19

Hi.
After messing up my configuration I decided to start over again. Unfortunately, the result is not much better.
So first of all I edited the configuration.yaml and added the following sensor.

climate:
  - platform: generic_thermostat
    name: xHandtuch
    heater: input_boolean.trv
    target_sensor: sensor.lumi_lumi_weather_2f12c902_temperature

Next I created a helper input boolean :

image
image790×789 34.2 KB

The name of the helper equals the entity from the generic Thermostat I created.

But obviously that does not work. unfortunately, that would explain, that the state of the climate Card is Always “Untätig” and does not change even if I turn the dial on the right.

image
image997×555 34.6 KB

On the left you can see the Danfoss entity as it is, on the right the climate card which is derived from the Generic Thermostat. The Temperature shown is correct it equals the number derived from the Apara sensor which is what I intended). The automation is only triggered, when theinput_boolean.trv is on, but that never happens.
Probably there is only a simple step missing, but I just can’t think of it.
I Think I might have solved it while I tried to recreate and explain the issue. I had to initially turn on the input_boolean.trv on manually. Then the automation started triggering.

image
image966×553 73.3 KB

As you can see il now shows Heizbetrieb which seems to be much better. Now I wonder why the display on the left does not update. Shouldn’t that be the same? Weird that the one ion the sight is static. Once I am home Im am goanna check which temp is shown on the Thermostat device. I will keep you posted.

20

I do not quite like my automation.

alias: Handtuchheizung Test
description: ""
trigger:
  - platform: state
    entity_id:
      - input_boolean.trv
    to: "on"
    id: "on"
  - platform: state
    entity_id:
      - input_boolean.trv
    to: "off"
    id: "off"
condition: []
action:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - "on"
        sequence:
          - service: climate.set_temperature
            target:
              entity_id: climate.devolo_thermostat_09356
            data:
              temperature: "{{ state_attr('climate.xhandtuch', 'temperature') |float + 5 }}"
      - conditions:
          - condition: trigger
            id:
              - "off"
        sequence:
          - service: climate.set_temperature
            target:
              entity_id: climate.devolo_thermostat_09356
            data:
              temperature: 15
      - conditions: []
        sequence:
          - service: climate.set_temperature
            target:
              entity_id: climate.devolo_thermostat_09356
            data:
              temperature: 0
mode: single

Something seems wrong there. .