Closed R1DEN closed 12 months ago
when i have time, i will implement this.
the problem here is, to find the right entity. yours is called bedroom_trv_number_temperature_calibration and for my TRV for example it's number.heizung_badezimmer_number_temperature_offset.
@KartoffelToby wrote it here in the comments, hacky way. https://github.com/KartoffelToby/better_thermostat/blob/master/custom_components/better_thermostat/utils/helpers.py#L527:L566
We would now need to add our cases, and then more and more. In the future. But the Temperature based calibration should also work, so i think this is not a prio?
we would then also need to add some code to the adapters. like it is in the mqtt adapter. all the offset related code.
maybe i will try it tomorrow and test it with one of my thermostats.
Are there any drawbacks with replacing that with a more generic
'temperature_calibration' in uid
||
'temperature_offset' in uid
?
P.S. Sorry, posted it from wrong account. reposting so that the history is not lost)
I've made a PR.
Prerequisites
Description
BT doesn't allow offset compensation
Steps to Reproduce
Try to add a new BT integration
Expected behavior:
BT has the option to compensate with offset as my TRV has the offset property
Actual behavior:
BT doesn't allow offset compensation
Versions
HA 2023.8.3 BT 1.2.2
Additional Information