Dear Beny_44,
maybe stupid question but i see you have programming mode weekday and Saturday and Sunday. I only see workdays_schedule. how can i make the schedule as you have in separate days?
i have the same problem only -6 to 6 but the automatisation dont know which range he can use.
Possible calibration values are: -6, -5, -4, -3, -2 ,-1 , 0,1,2,3,4,5,6
And no floating number
The original blueprint did not work with this device as it provided for adding the current value of the calibration to the newly measured temperature delta. This resulted in a “race to the bottom” where the calibration was continuously adjusted downward, and soon MQTT appeared overwhelmed with messages, resulting in my Zigbee devices becoming unresponsive. That behavior was observed by other users, as well. The optimized blueprint therefore does not add the current calibration value to the temperature delta.
The new calibration value is also capped at the -9 minimum. There is no cap at the maximum, as this does not appear to be a practical scenario.
In order to prevent excessive MQTT traffic caused by repeatedly setting the minimum calibration value (in case the actual temperature delta is lower than the minimum), the blueprint checks whether the minimum calibration setting of -9 has already been reached and in that case only proceeds if the new calibration setting would be above -9.
If your device has different valid calibration values, it should be easy to adjust on the basis of this revised blueprint.
@nivong: I was not sure my version would fit everybody since you will probably have had a reason for setting your blueprint up the way it was and different TRVs may behave differently. I assume you did not experience downward adjustment loops yourself, did you?
Logger: homeassistant.components.mqtt.number
Source: components/mqtt/number.py:191
Integration: MQTT (documentation, issues)
First occurred: 12:10:52 (44 occurrences)
Last logged: 12:20:32
Invalid value for number.valve_wz_local_temperature_calibration: 4294967273 (range -6.0 - 6.0)
EDIT: Wow, what a coding trip But it was cool, I never know what it possible with the developer-area and how python works in case of variables etc.
I checked the blueprint yesterday. My SEA802 TRV has completely different attributes. It starts with the fact that the measured temperature on the adapter itself is addressed via ‘current_temperature’.
The calibration goes from a range of -6 to +6. In addition, the calibration is adjustable via a separate entity. In my case:
states(‘number.valve_wz_local_temperature_calibration’)
But I need to say that I am not 100% sure if its representate the original logic. Perhaps @nivong or @bk1 can tell me if I am on the right train to success SchuuuSchuuuuuu
On my SEA802-Z01 TRV I had 2 temperature attributes:
Hello @bk1@JamieMe@nivong
i tried the blueprint. The function is given. It change the range only between -6 to 6. My problem is, that the change is to frequently and the TRV can´t handle it.
@LukasVyhlidka Hi! Just wanted to say THANK YOU! This is the best automation I tested so far for this scenario (I have 9 radiators). Better thermostat is too ambitious and unfortunately filled with bugs. I tested other blueprints but had problems here and there, your work is the best one by far!
i got an BRT100 two and got some issues with the sync to an external sensor. I tried yours aswell and got the same result. The problem seams that the current temperature of the trv isnt reported to homeassistant that frequently.
Do you discovered this issue aswell?
sorry for late response (probably not properly configured notifications). To be honest I have not experienced such an issue. If I remember correctly, the TRV is sending data when something changes. I am using zigbee2mqtt, maybe it can be different with home assistant ZHA integration?