Question about BT suddenly raising the "desired" temperature

[ovizii]

I have had this problem for years but haven't given up. Every year shortly before winter I check back with BT to see if it has made any progress. Sadly it only runs fine for about 1-2 weeks then it starts changing my “desired” temperature, so I can't trust it to work unsupervised and switch back to the default HA thermostat.

Now the reason I am writing this post is:

Is there a legitimate reason for BT to even have a function which can change the “desired” temperature?

In my simple mind, I see no reason at all as that is the one change a human has to make and which should never be touched by BT. I mean this is the setting I give BT and its job is to reach and keep that temperature while not touching it at all.

Am I missing something or not seeing the big picture? Today BT decided that when I opened the window, what I actually wanted was to set my “desired” temperature to 27.5 degrees C. How on earth is this a function BT even has access to?

EDIT:
I changed target temperature to "desired" temperature, I wasn't perfectly sure what that value is called. If I check with the developer tools to the BT TRV, it is simply called “temperature”. Weirdly enough, in the screenshot of the history it is called target temperature.

hvac_modes:
  - heat
  - "off"
min_temp: 5
max_temp: 30
target_temp_step: 0.5
preset_modes:
  - none
current_temperature: 20.6
temperature: 20.5
hvac_action: idle
preset_mode: none
window_open: false
call_for_heat: true
last_change: "2024-11-20T11:44:04.710295"
saved_temperature: null
humidity: 55
main_mode: heat
tolerance: 0.3
heating_power: 0.0108
errors: "[]"
batteries: >-
  {"sensor.bedtemphum_temperature": {"battery": "65", "battery_id":
  "sensor.bedtemphum_battery"}, "sensor.bedtemphum_humidity": {"battery": "65",
  "battery_id": "sensor.bedtemphum_battery"},
  "binary_sensor.bedroom_window_contact": {"battery": "100", "battery_id":
  "sensor.bedroom_window_battery"}, "climate.thermobed": {"battery": "100",
  "battery_id": "sensor.thermobed_battery"}}
friendly_name: BetterBedThermostat
supported_features: 401

[Asakash]

Hi,
maybe check the logs of BT if you see this line decoded TRV target temp changed from xx.x to yy.y. It may be the same Issue as in #1387 .
In my case one of the TRVs changed its own set temperature (I do not know why) and BT interprets this change as a manual change of the TRV (e.g. via the buttons) which in turn changes BTs target temperature. This feature is unfortunately not well documented.
Setting child lock for all TRVs in Better Thermostat should fix that problem as the function to change the overall target temperature will not run when child_lock=true.

Hope that helps.

[ovizii]

Thanks for the tip. I “usually” have all child-lock on as I do not use any manual changes but let me double-check and see if the problem occurs again after making sure it really is on.

[Asakash]

Yeah I usually also have it enabled but typically in the settings of the trv. That's why I did not also check it in Better Thermostat. Hope it works for you.

…

On Tue, Nov 26, 2024, 12:08 ovizii ***@***.***> wrote: Thanks for the tip. I “usually” have all child-lock on as I do not use any manual changes but let me double-check and see if the problem occurs again after making sure it really is on. — Reply to this email directly, view it on GitHub <#1483 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAX5GPIUJ3IY6HWQWDWBCXL2CRJDDAVCNFSM6AAAAABSEEDZDKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZYGI2TOMQ> . You are receiving this because you commented.Message ID: <KartoffelToby/better_thermostat/repo-discussions/1483/comments/11382572@ github.com>