It Looks Like minimal temp is Not working in ref Version.
Thermostat temp is in my oppinion wrong
Room temp is 21C, minimal is 18C, why Thermostat Set temp is 27 and 27C is Thermostat temp, the Set temp should bei smaller
can you add extra switch use for water pumps or use none cable using thersmostat trigger to switch (dry contact) for heating. for this 
Custom Action can be use can you give example code
Your scheduler is on, so heating is on.
Target temperature is 21°C.
Thermostat room temperature is 27°C
Real room temperature is 21°C
Target Temperature after generic calibration → 27°C in order to hold the 21°C
Hmm my helpers is Buggy, 21:30 is setted, template that checks for comfort or minimal in visu Trigger also on 21:30, but ahc and History triggers at 22. (Old value)
I recreate this helpers now, maybe this was the same Problem we talked few ich weeks ago. - strange
So adh made all right when he had 21 as value, so i have no Problems with the ref Version in my case. (All other Features are tested but proximity)
Great Work 
1 Like
Yes, I know, this is why I tried it with another automation. Thanks for fixing it. I tried it again and now it works without an error. I will get back if I see any other issue 
Thanks for your work!
BTW: what TRVs do you use or do you recommend any which works great with your blueprint (offset / calibration)? I am not really happy with aqaras anyways.
1 Like
Thank you for your feedback!
I am also looking for good working zigbee based TRVs. I had three different types here. Some were really noisy. Some didn’t close the valve properly. And for three years I use Hama Thermostats (some rebranded TUYA thermostats) that work very well but I think they only can open and close and are not able to adjust the valve position.
So if there are some TRVs working like the Hama with adjustable valve position just let me know. 
I also use a custom quirk to get calibration working. I am also looking for some TRVs on sale. Maybe I get new ones until next winter.
I see, same problem everywhere 
I will invest a little money to test some other configurations because the TRV game really gets on my nerves. I have ordered a Danfoss Ally/Popp TRV, one from Bosch II (may they works better with offset) and one from EVE (Thread). I will get back if i can say anything about it.
BTW: it seems that the automation does not trigger calibration when no external sensor via blueprint is set. But temperature difference was higher then set in the blueprint so it actually should be.
Yes, I’ve interested in. Just report back after you’ve tested them. Would be very helpful.
Yes, calibration only gets triggered when an external sensor is set. It gets triggered by the measured temperature change of the thermostat itself and when the temperature of the external sensor changes. And only if the value doesn’t change for the configured calibration timeout duration.
Furthermore the new calibration values are will be calculated and compared to the old ones. If the difference between old calibration value and new calibration value is greater or equal to the calibration delta the new value will be set.
I see. Then its not really makes a lot of sense to test the automation with aqara and no external sensor. I will swap the configuration to external sensor via blueprint and generic and will see how it works.
Maybe I implement the first version of aqara calibration this weekend. But I am a little bit confused. There are several blueprints out there that aims on calibrating the e1. Most of them based on z2m integration. Some are looking for a number entity (which must be new) and others are calling directly the mqtt broker using cluster commands / mqtt commands.
hm, so in this I am not deep enough in the code. But may I can help with the entities which z2m creates in my case. I used this blueprint to set external sensor which works in my eyes: Aqara TRV E1 external temperature
If you have any questions I can help with, just let me know.
number.kinderzimmer_sensor_temp should be the entity to go with calibration, right?
What value is stored in this entity? The current real room temperature like 20.00 or an integer like 2000?
//EDIT: I will have a look in the docs. 
I have some Aqara TRV around me but i´m also not that happy with it. So i have ordered 2 of the new Bosch TRV and they work very well. There is also the possibility to see the valve status (not only on/off)
2 Likes
I am not sure, how can I find it out?
Heres what I can find out: {
“battery”: 98,
“child_lock”: “LOCK”,
“device_temperature”: 21,
“internal_heating_setpoint”: 19,
“linkquality”: 255,
“local_temperature”: 18.6,
“occupied_heating_setpoint”: 18,
“power_outage_count”: 0,
“preset”: “manual”,
“sensor”: “external”,
“setup”: false,
“system_mode”: “heat”,
“valve_alarm”: false,
“valve_detection”: “OFF”,
“voltage”: 2900,
“window_open”: false
}
The Bosch II? Is calibration also possible?
Nice. I am looking forward to test them. Do you use them with this blueprint?
Just need this information of the climate entities. Could you paste this in dev tools template editor?
{{ device_attr('climate.YOUR_AQARA_THERMOSTAT','manufacturer')}}
Yes it is. You can check this here: https://www.zigbee2mqtt.io/devices/BTH-RA.html#bosch-bth-ra
I have to say that the Bosch has a kinda weird heating pattern. With and without your blueprint.
1 Like
I can, but that there comes out Xiaomi I think you know already!? What do I have to do exactly? 
