Ok. My fault. I thought i can See the Temperature in Z2m in the external temperature input. But that value stays at null
But the local temperature is changing. And thats what i need and want.
Thanks 
Following the Z2M update, the blueprint no longer works, I came here and found a correct update (super cool), but I would have liked the update to be able to do this automatically.
Should we just replace the blue print or rebuild all the automations? ,
Hi @pavax I was wondering why my heating hadn’t been working today after being rock solid for months with this blueprint and was really happy to see it had been updated yesterday to work with the updated z2m. Thank you so much, working perfectly again!
1 Like
Hi @pavax , just wanted to say thank you for this great blueprint! I find it extremely useful in my configuration, and it’s great you even updated it since the latest breaking z2m update!
1 Like
you should be good with simply re-importing the blueprint
I’m just testing the blueprint thinking it might help with my heating system. I use the Aqara TRVs with Aqara external temp monitor in most rooms. I do use the Better Thermostat add-on to combine things and take most of the logic away from the TRV itself but I thought what harm can it do to set the external sensor.
I have found now however that when the automation fires off to update the external temp it does correctly change the TRV to external as this was on internal previously but the temp does not get set. On checking the trace and looking at the timeline it just stops, the timeline says:
Triggered by the state of sensor.temp_sensor_4_temperature at 6 February 2024 at 21:19:18
Stopped because only a single execution is allowed at 6 February 2024 at 21:19:18 (runtime: 0.00 seconds)
Reading the state of the TRV in Zigbee2MQTT is says:
“external_temperature_input”: null,
Any idea why it isn’t setting it?
This is fantastic, somehow my automation stopped with the latest HA update , and using this BP I can set my aqara thermostat with just couple of clicks to use external sensor. Great job bro!
p.s. only need to figure out how to constantly update automation to use it every minute or something
I am still using Z2M version 1.35.1 and need to change the name of the external temperature topic. Unfortunately I do not get a device to choose from because the device selector filter does not match, so I ask for an adjustment so that the old name is found.
aqara_trv_device:
name: The Aqara TRV
description: The TRV that the temperature willl be set to
selector:
device:
multiple: false
filter:
- integration: mqtt
manufacturer: Aqara
model: Smart radiator thermostat E1 (SRTS-A01)
- integration: mqtt
manufacturer: Xiaomi
model: Aqara Smart Radiator Thermostat E1 (SRTS-A01)
Thank you so much for putting the work into this, and especially for maintaining it.
I noticed that my E1s seem to report their manufacturer/model a bit differently, so I had to adjust the entity filter to be able to select them. For some reason, they report “Xiaomi” as their manufacturer, and add the “Aqara” in front of the model. You can probably update the filter to look like this:
filter:
- integration: mqtt
manufacturer: Aqara
model: Smart radiator thermostat E1 (SRTS-A01)
- integration: mqtt
manufacturer: Xiaomi
model: Aqara Smart Radiator Thermostat E1 (SRTS-A01)
To enable selection of both E1s that report themselves in both ways.
Edit: It seems like @Ecronika seems to have made the same suggestion 4 days ago, should have checked the timeline before posting this
Any way to make it work whit TuYa TRV’s?
Depends, do those ones (and there’s dozens of models) support an external temperature sensor? If so is how to use that documented anywhere?
i have the problem that the external_temperature_input is unavailable in HA. I have this for all my 3 TRVs.
Any Idea?
Hello,
Thanks for this blueprint. I noticed that the battery live is shorter since I am using it compared to internal sensor. Therefore, I would suggest not to sync each time the external temp change, but only if the difference between the previous temperature and the one from the external sensor is higher that a value (which can be an option)
1 Like
Yep. I noticed the TRVs in my bedroom that are synced with temperature sensor on wifi air purifier have had pretty bad battery life, due to constant updates, because the air purifier measures temperature with 2 decimal places accuracy and updates its state rapidly.
Fixed by adding this condition to the blueprint.
{{ (trigger.to_state.state | float - state_attr('climate.' + device_attr(aqara_trv_device, 'name'), 'current_temperature')) | abs >= 0.066 }}
It should also fix issue with constant updates, when the temperature sensor state “oscillates” around x.x5 values.
Sorry, I’m not an expert home assistant user, could you give some more info on how to do this?
Thanks.
Hi,
I’m sometimes getting the error below. Could you help please?
z2m: Publish ‘set’ ‘sensor’ to ‘Office radiator valve’ failed: ‘Error: ZCL command 0x54ef4410006fd472/1 manuSpecificLumi.write({“65522”:{“value”:[170,113,52,68,19,90,2,65,49,102,160,255,0,61,5,84,239,68,16,0,111,212,114,0,21,141,0,1,157,27,152,8,0,7,253,22,10,2,10,201,232,177,184,212,218,207,223,192,235,0,0,0,0,0,1,61,4,101],“type”:65}}, {“timeout”:10000,“disableResponse”:false,“disableRecovery”:false,“disableDefaultResponse”:true,“direction”:0,“srcEndpoint”:null,“reservedBits”:0,“manufacturerCode”:4447,“transactionSequenceNumber”:null,“writeUndiv”:false}) failed (SRSP - AF - dataRequest after 6000ms)’
Change in Home Assistant Core 2024.8.0
Line 85
„playload_template“ change only in „playload“
2 Likes
Thank you for the fix - I updated the blueprint
Hello,
First a big thank you for this awesome blueprint.
I‘ve installed it yesterday and everything seemed to go on fine.
But today it stopped working, throwing the following errors:
10000ms)))’
[2024-09-14 18:14:58] error: z2m: Publish ‘set’ ‘external_temperature_input’ to ‘Ventil Schlafzimmer’ failed: ‘Error: ZCL command 0x54ef4410009731fd/1 manuSpecificLumi.write({“65522”:{“value”:[170,113,19,68,18,124,5,65,16,0,21,141,0,1,157,27,152,0,1,0,85,69,2,160,0],“type”:65}}, {“timeout”:10000,“disableResponse”:false,“disableRecovery”:false,“disableDefaultResponse”:true,“direction”:0,“reservedBits”:0,“manufacturerCode”:4447,“writeUndiv”:false}) failed (ZCL command 0x54ef4410009731fd/1 manuSpecificLumi.write({“65522”:{“value”:[170,113,19,68,18,124,5,65,16,0,21,141,0,1,157,27,152,0,1,0,85,69,2,160,0],“type”:65}}, {“timeout”:10000,“disableResponse”:false,“disableRecovery”:false,“disableDefaultResponse”:true,“direction”:0,“reservedBits”:0,“manufacturerCode”:4447,“writeUndiv”:false}) failed (ZCL command 0x54ef4410009731fd/1 manuSpecificLumi.write({“65522”:{“value”:[170,113,19,68,18,124,5,65,16,0,21,141,0,1,157,27,152,0,1,0,85,69,2,160,0],“type”:65}}, {“timeout”:10000,“disableResponse”:false,“disableRecovery”:false,“disableDefaultResponse”:true,“direction”:0,“reservedBits”:0,“manufacturerCode”:4447,“writeUndiv”:false}) failed (Timeout - 46277 - 1 - 221 - 64704 - 4 after 10000ms)))’
Any hints for me?
Best regards, Thorsten
Hello,
This blueprint was working like a dream with my Aqara E1 radiator valve to my SONOFF Temperature sensor. But since I updated the valves firmware to 0.0.0_1030 through ZigBee2mqtt OTA, the valve no longer uses the external sensors anymore even with it being set to external, I’ve rebooted HA just to be sure too.
I was just wondering if this is a known issue and if so, does anybody know how do I go about getting this resolved or if there’s any future fixes?
It doesn’t look like I downgrade the firmware either.
Thank you.
EDIT: My work around was to use better thermostat. This is still an issue people should be aware of if they run into it.