Danfoss Ally TRV working with remote temp sensor

Hardware
,
107

@Ramblurr thank you for sharing.

 {{ (states("sensor.dining_motion_sensor_temperature") | float * 100) | round(0)}}

This instruction provides me next output:

Failed to call service script/1639522561818. Value 2182.0 for Office Thermostat external measured room sensor is outside valid range 0.0 - 100.0

From my point of view seems Ally converter was changed and now asks for usual temp like 21, 22 and so on.

108

I’d recommend you to use the method described in post 98. It is confirmed to work by @BikeViking and me.

1 Like
109

there was a change in Z2M that makes the -8000 value no longer work, there was a change within Herdsman but you won’t see it until the next update.

1 Like
110

@hello-world are you using zha or zigbee 2 Mqtt? Maybe zigbee2mqtt translates the values internally?

111

Thank you. Of course I can wait.

112

I am using zigbee2mqtt. From my point of view zigbee2mqtt supports that value but HA wishes only two-digits temp value.

113

I have quite strange thing with ota on one Danfoss Ally TRV. Only it says that no updates. How to force this process?
image

114

Same question here.

115

I am starting to get some weird behaviour:

I got 2 radiators in the same room, both following an external sensor, with your suggested automation.
Radiator Covered is set to 1, Load Balancing enabled and adaption_run_control.

Sometimes, I got only 1 of the radiators actually heating, while the other having the valve off. If I bump up the set temperature with a couple of degrees, both of the radiators help.

116

Maybe you guys called to the vendor? Tried to replace/repair under warranty?

117

@bjorn.sivertsen My room with 2 radiators is performing OK without any special handling, but I think that’s just by chance. As I wrote above, I think that computing the Load Radiator Room Mean and pushing that number back to the TRVs is likely the way to properly implement it. But, the radiator load isn’t directly exposed in ZHA yet, and apparently there’s no such thing as a zha.get_zigbee_cluster_attribute service even though there’s a zha.set_zigbee_cluster_attribute service!

So, I don’t have an easy way to test that idea. But maybe (for now), you can try manually setting the proper room mean on both TRVs and see if that helps? The problem is that I think the radiator load reported by each TRV changes over the day, so that value may need frequent updating.

118

@BikingViking Is the pi_heating_demand attribute of the valve not the load of the radiator? Maybe that number averaged over a sensible period for all radiators in the room should be pushed back to both?

119

As I understand it, the pi_heating_demand corresponds to the % open of the valve, which is not quite the same thing (and is bounded by 0-100). My load estimate right now, for example, is 302.

Also, I just realized that the mean load attribute doesn’t show up in the “manage clusters” in ZHA anyway. But maybe it can still be set in a YAML script, like we do here for sending the extetnal temperature…

120

@BikingViking where you able to create a group with both thermostat in the room? I am trying on my end (in Z2M) and I am getting an error. The Ally guide does state that radiaors should be grouped together in order to be controlled at once so it should be feasible

edit: so after doing some research this seems to be a hardware limitation. Not sure if we can simulate the group within HA (change settings in one place and affect multiple TRV at once.)

edit2: I have found GitHub - daenny/climate_group: Home Assistant Climate Group which allows to group multiple TRV together but we would need some Ally specific enhancements to share the temperature from a sensor and the average load.

121

@Charlie-R, indeed I’m using that climate group method to make it easier to set the same temperature for each TRV in the same room. But, I think it doesn’t handle the case where the setpoint is manually adjusted by turning the TRV.

Sending the same external temperature to 2+ TRVs is easy enough with a minor adjustment to the basic script. But as I noted above, to truly replicate the Ally’s group functionality, continuously updating the radiator load mean is probably the last missing piece, but I have no idea how to program it. :slight_smile:

122

Hello guys,
This is my first post here.
I’ve Ally TRV and Ally gateway. Just now I had installed HA on my TrueNas server.
I’d like to buy some usb zigbee connector, and then some “opened window” sensor, and temperature sensor. Would You recommend me some devices to be working with Ally TRV and the module described in this topic?
Thanks in advance
BR
Jacek

123

I did a script for the load but currently there is a bug in Z2M which will be fixed in the next update (sets the max load at 100)

first I create a sensor that calculates the average load

sensor:
  - platform: min_max
    entity_ids:
       - sensor.thermostat_salon_1_load_estimate
       - sensor.thermostat_salon_2_load_estimate
    name: salon_avg_load
    type: mean

and then I did a quick script to write the values:

sequence:
  - service: number.set_value
    target:
      entity_id:
        - number.thermostat_salon_1_external_measured_room_sensor
        - number.thermostat_salon_2_external_measured_room_sensor
    data:
      value: '{{ (states("sensor.temp_1_temperature") | float * 100) | round(0)}}'
  - service: number.set_value
    target:
      entity_id:
        - number.thermostat_salon_1_load_room_mean
        - number.thermostat_salon_2_load_room_mean
    data:
      value: '{{ (states("sensor.salon_avg_load") | float) | round(0)}}'
mode: single
alias: Update Thermostat Salon
icon: mdi:radiator

Now sometimes I am seeing some strange begaviour with one radiator at 100% and the other at 0% and sometimes the radiator load is -8000 which obviously gives a negative average. I cases where a radiator does not calcualte a load I am not sure what the default value in the script should be

124

Internal “opened window” sensor is working just fine, no needs additional one.
Regarding external sensor there is no way to use it directly. Only with additional script help (in HA) and even then TRV uses average temp between 2 sensors. It’s not very obvious and useful as for me.

125

I already read this issue, but would be fine for me.
Till yesterday I was using Danfoss Link system with 5 thermostats. It was showing 21C but for sure in the room it was colder. If I can average the TRV temperature and external sensor, it would be more comfortable - I hope :slight_smile:
Going back to the Danfoss Link the open window sensor was not working at all. In many cases, my wife opened window in the kitchen, and the radiator was fully open and extremely hot. When we closed the window in few minutes we got 24-25C in the room.
So now I’d like to have more comfort and less heat consumption. Now I’m waiting for devices to fully start the HA environment.
I had ordered ConBee II zigbee module and Xiaomi Aquara sensors

126

Your statement regarding external room sensor is not true. With firmware 1.18 there is a new attribute called “Radiator covered” which basically turns off usage of internal temperature sensor.
Look at my current bedroom trv. It is detecting temeprature over 30C with setpoint at 22,5 but valve is still opened at 90% because room temperature is still too low.
image

3 Likes