Thermostat resets back to 5 degrees periodically

[BurningTheSky]

I have set up a Moes BHT-006 thermostat up in BT for controlling my underfloor heating and have noticed that while in heating mode every couple of hours it resets down to 5 degrees. I enabled debugging on BT in HA and I see the following message spamming the logs over and over:
DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: trigger_trv_change test / _old_heating_setpoint: 45.0 - _new_heating_setpoint: 45.0 - _last_temperature: 45.0

Then when temperature resets down to 5 degrees the log changes then repeats the last 2 lines over and over:
DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: trigger_trv_change test / _old_heating_setpoint: 45.0 - _new_heating_setpoint: 45.0 - _last_temperature: 45.0 2025-01-02 20:06:25.527 DEBUG (MainThread) [custom_components.better_thermostat.events.temperature] better_thermostat None: external_temperature changed from 20.7 to 21.2 2025-01-02 20:06:25.531 DEBUG (MainThread) [custom_components.better_thermostat.utils.helpers] better_thermostat None: climate.underfloor_thermostat / heating_power_valve_position - temp diff: 0.8 - heating power: 0.01 - expected valve position: 80% 2025-01-02 20:06:25.531 DEBUG (MainThread) [custom_components.better_thermostat.calibration] better_thermostat None: climate.underfloor_thermostat - new setpoint calibration: 40.5 | external_temp: 21.2, target_temp: 22.0, trv_temp: 23.0 2025-01-02 20:06:25.531 DEBUG (MainThread) [custom_components.better_thermostat.utils.controlling] better_thermostat None: TO TRV set_temperature: climate.underfloor_thermostat from: 45.0 to: 40.5 2025-01-02 20:06:25.552 DEBUG (MainThread) [custom_components.better_thermostat.utils.controlling] better_thermostat None: climate.underfloor_thermostat / check_target_temp / _last: 40.5 - _current: 45.0 2025-01-02 20:06:33.703 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: trigger_trv_change test / _old_heating_setpoint: 0.0 - _new_heating_setpoint: 0.0 - _last_temperature: 40.5 2025-01-02 20:06:33.703 WARNING (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: New TRV climate.underfloor_thermostat setpoint outside of range, overwriting it 2025-01-02 20:06:33.938 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: trigger_trv_change test / _old_heating_setpoint: 0.0 - _new_heating_setpoint: 0.0 - _last_temperature: 40.5 2025-01-02 20:06:33.939 WARNING (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat None: New TRV climate.underfloor_thermostat setpoint outside of range, overwriting it

Does anyone have any insights into what's happening and how I could resolve it? I have heard that this thermostat might error with decimals over mqtt so the "better_thermostat None: TO TRV set_temperature: climate.underfloor_thermostat from: 45.0 to: 40.5" section may be causing the issue but I don't know how to avoid it in future? I have BT configured to use 1 degree steps already

[folfy]

Simply put I think the "AI" algorithm / compensation is bs, cause it just doesn't make sense to me at all, neither the implemantation/code, nor how it behaves. Try "normal compensation", and if that is still causing troubles, the most conservative/reliable option should be the new "linear compensation" in v1.7.0b2.

Rounding by step was also messed up in BT, so that's why it ignored your step size - Please try the new b2 version, it should be vastely improved now ( #1529 / #1475). I'm recommending though to leave it on the minimum supported step size of your TRV (should be detected correctly in AUTO by BT), or otherwise for example "linear compensation" would not be able to make fine adjustments / regulate as "well" as it could.