Target temperature in GUI changes by itself randomly

Pabstiii commented 11 months ago

Prerequisites

Fritz Dect 301

{
 {
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2023.10.3",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.11.5",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Berlin",
    "os_name": "Linux",
    "os_version": "6.1.21-v8",
    "supervisor": "2023.10.0",
    "host_os": "Home Assistant OS 11.0",
    "docker_version": "24.0.6",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "better_thermostat": {
      "version": "1.3.0",
      "requirements": []
    },
    "hacs": {
      "version": "1.33.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    }
  },
  "integration_manifest": {
    "domain": "better_thermostat",
    "name": "Better Thermostat",
    "after_dependencies": [
      "climate"
    ],
    "codeowners": [
      "@kartoffeltoby"
    ],
    "config_flow": true,
    "dependencies": [
      "climate",
      "recorder"
    ],
    "documentation": "https://github.com/KartoffelToby/better_thermostat",
    "iot_class": "local_push",
    "issue_tracker": "https://github.com/KartoffelToby/better_thermostat/issues",
    "requirements": [],
    "version": "1.3.0",
    "is_built_in": false
  },
  "data": {
    "info": {
      "name": "Schlafzimmer",
      "temperature_sensor": "sensor.ble_b_2_sz_temp",
      "off_temperature": 14,
      "humidity_sensor": "sensor.ble_b_2_sz_hum",
      "outdoor_sensor": "sensor.temp_outside_aquarium_temp",
      "window_sensors": null,
      "weather": null,
      "window_off_delay": 0,
      "model": "FRITZ!DECT 301/FRITZ!DECT 301",
      "tolerance": 0.5
    },
    "thermostat": {
      "climate.hz_sz_1": {
        "name": "HZ SZ 1",
        "state": "off",
        "attributes": {
          "hvac_modes": [
            "heat",
            "off"
          ],
          "min_temp": 8.0,
          "max_temp": 28.0,
          "preset_modes": [
            "eco",
            "comfort"
          ],
          "current_temperature": 25.0,
          "temperature": 0.0,
          "preset_mode": null,
          "battery_low": false,
          "battery_level": 90,
          "holiday_mode": false,
          "summer_mode": false,
          "window_open": false,
          "friendly_name": "HZ SZ 1",
          "supported_features": 17
        },
        "bt_config": {
          "calibration": "target_temp_based",
          "calibration_mode": "heating_power_calibration",
          "protect_overheating": true,
          "no_off_system_mode": false,
          "heat_auto_swapped": false,
          "child_lock": true,
          "homaticip": false
        },
        "bt_adapter": "fritzbox",
        "bt_integration": "fritzbox",
        "model": "FRITZ!DECT 301"
      },
      "climate.hz_sz_2": {
        "name": "HZ SZ 2",
        "state": "off",
        "attributes": {
          "hvac_modes": [
            "heat",
            "off"
          ],
          "min_temp": 8.0,
          "max_temp": 28.0,
          "preset_modes": [
            "eco",
            "comfort"
          ],
          "current_temperature": 25.0,
          "temperature": 0.0,
          "preset_mode": null,
          "battery_low": false,
          "battery_level": 90,
          "holiday_mode": false,
          "summer_mode": false,
          "window_open": false,
          "friendly_name": "HZ SZ 2",
          "supported_features": 17
        },
        "bt_config": {
          "calibration": "target_temp_based",
          "calibration_mode": "default",
          "protect_overheating": true,
          "no_off_system_mode": false,
          "heat_auto_swapped": false,
          "child_lock": false,
          "homaticip": false
        },
        "bt_adapter": "fritzbox",
        "bt_integration": "fritzbox",
        "model": "FRITZ!DECT 301"
      }
    },
    "external_temperature_sensor": {
      "entity_id": "sensor.ble_b_2_sz_temp",
      "state": "18.6",
      "attributes": {
        "state_class": "measurement",
        "unit_of_measurement": "\u00b0C",
        "device_class": "temperature",
        "friendly_name": "BLE_B_2 SZ Temp"
      },
      "last_changed": "2023-10-18T14:10:56.948765+00:00",
      "last_updated": "2023-10-18T14:10:56.948765+00:00",
      "context": {
        "id": "01HD1J049MWQM9FAAXCND0H7Z8",
        "parent_id": null,
        "user_id": null
      }
    },
    "window_sensor": "-"
  }
}
}

Description

Target temperature is randomly set to a higher value. E.g. 26 or even 30°. My guess is, that the temperature meant for the thermostat is set as a target temperature of better thermostat, as it also changes in the gui. It happens randomly and regardless of the room temperature. I use the AVM Fritz Dect 301 Valve Thermostats.

Steps to Reproduce

Set a temperature in the gui higher than the room temperature, so the heating turns on.

Expected behavior:

The target temperature set in the gui should not change by itself.

Actual behavior:

The target temperature in the gui changes by itself.

Versions

HA: Home Assistant OS 11.0 BT: 1.3.0 BT UI: 2.1.3

Additional Information

darthdule commented 10 months ago

Have the same problem. Installed my new sonoff dongle and played alot with the integration. At some point temp ist just decreasing. Greetings from Germany.

lop3r87 commented 10 months ago

I have the same issue, seems to be happening to the ones where I have more than one trv combined.

nurunet commented 10 months ago

EDIT:

Obviously, I'm just stupid. There was a default schedule set for the bedroom radiator - which switched to 21°C at 06:00 AM. D'oh.

Yesterday evening, I added the (single!) bedroom TRV to Raspberrymatic. I did not set up a Better Thermostat with it yet. I did set its target temperature to 14°C through Home Assistant though.

This morning, I woke up to the thermostat motor whirring. Its target temperature had increased to 21°C. I am starting to wonder if this isn't really an underlying issue with HA instead of Better Thermostat.

I think I'll uninstall BT to see if the issue persists.

darthdule commented 10 months ago

@KartoffelToby: Do you have a hint what may be the problem? How can we help? Is there anyone using BT who does not have this problem? I am using the new Sonoff TRBZB. No Sonoff hub or app, just clean with Sonoff Dongle.

denbus2023 commented 10 months ago

Is it possible that this is not a BT bug but something already in Home Assistant? I did not want to wake up today to tropical temperatures, so I disabled BT in the living room. I set both the Homematic and the Aqara TRVs to ~21°C via the device settings. This worked for the Homematic, but the Aqara's target temperature jumped to ~30°C twice before the correct temperature took. What gives?

When I delete all BT thermostats I don't have the issue.

Same here, tried it without BT installed for a few days, steady as a rock... Now this mornig installed BT again, temperatures going everywere... BT is definitely the problem.

accik commented 10 months ago

Had 1.3 installed (or 1.4 cannot remember since I just got my trv's) and similar issues were happening. Downgraded to version 1.21 and no issues so far (~10 days). Didn't make any other change, no automations etc. I can test 1.4 later and see if the issue arise.

1Tomber commented 10 months ago

Ok, so I went through my logs I posted and several new ones and found out the following - I'm using Tado with the Homekit integration:

I had two TRVs assigned to one room in Tado, so when BT changed the target temperature for one TRV, the Tado controller (Internet bridge) changed the target temperature for the other TRV, this was interpreted by BT as a manual change, which then triggers another target temperature change on the other TRV ... and so on.
There are changes to the target temperature send by the Tado controller that I can't find out where they are coming from.

And my fixes:

I fixed the first problem by separating the two TRVs into two separate room in the tado app. This already helped a lot and maybe needs to be communicated on the website, if there is a controller involved, don't put TRVs in the same room as it triggers automatic sync on the controller side (@KartoffelToby). No bug in BT.
The ghost changes I couldn't get hold of, so I put the "child lock" setting onto all BTs, this solved all my problems.

cocochaa commented 10 months ago

Same problem. In the history I can see it happen at 8:29:45 seconds. The Code:

2023-11-15 08:29:45.097 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat BT Wohnzimmer: TRV climate.homematic_wz_re update received 2023-11-15 08:29:45.097 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat BT Wohnzimmer: trigger_trv_change / _old_heating_setpoint: 27.5 - _new_heating_setpoint: 30.0 - _last_temperature: 27.5 2023-11-15 08:29:45.097 DEBUG (MainThread) [custom_components.better_thermostat.events.trv] better_thermostat BT Wohnzimmer: TRV climate.homematic_wz_re decoded TRV target temp changed from 20.5 to 30.0 2023-11-15 08:29:45.103 DEBUG (MainThread) [custom_components.better_thermostat.utils.helpers] better_thermostat BT Wohnzimmer: climate.homematic_tz / heating_power_valve_position - temp diff: 11.6 - heating power: 0.0284 - expected valve position: 100% 2023-11-15 08:29:45.103 DEBUG (MainThread) [custom_components.better_thermostat.utils.controlling] better_thermostat BT Wohnzimmer: TO TRV set_temperature: climate.homematic_tz from: 27.5 to: 30.0 2023-11-15 08:29:45.217 DEBUG (MainThread) [custom_components.better_thermostat.utils.controlling] better_thermostat BT Wohnzimmer: climate.homematic_tz / check_target_temp / _last: 30.0 - _current: 30.0

"TRV climate.homematic_wz_re decoded TRV target temp changed from 20.5 to 30.0"

This is where it happens. Any ideas? I dont really have to time to dig through the code.

1Tomber commented 10 months ago

@cocochaa I can highly recommend enabling debug output on the TRV devices (homematic, tado, zigbee implementation) to see where the changes are coming from, in your case homematic. BT is doing a check against their last target temp change, to determine if the temperature was changed on the thermostat manually, if there is an update coming from the TRV that differs from the the last set target temp, then it assumes it was changed on the TRV itself. To debug it would help to show the target temp changes before the actual wrong change and also the debug of the homematic device. If you don't need to change the temp on the TRV by hand, consider using the "child lock" feature, which should fix the problem.

cocochaa commented 10 months ago

Great input. Never thought Homematic was the problem since it happend on Zigbee as well. Child lock has cured the problem at the moment. If it happens again I will enabel all debuging. For now no problems at all.

nukleuz80 commented 10 months ago

I think the BT child lock function solves it... I had only issues with HomeMatic - not Zigbee

lippertmarkus commented 10 months ago

I don't think that it's an issue only with the TRV integrations themselves:

You said that the TRV itself changes it's temperature which leads to the BT thermostat to jump as well. But if you uninstall BT and look at the history of the TRV target temperature I don't see it changing on it's own, not only for a few milliseconds
Why does it work fine with older versions of Better Thermostat although the TRV integration are the same there?

g0mga commented 10 months ago

Is there any fix for this yet? All very dissapointing. Now having to spend 2 days a week fire fighting Home Assistant problems. With time running out on my body clock, I am begining to wish I never heard of HA.

Gave up trying to resolve emory issues whereby RAM was being consumed at alarming rate until HA crashed. Resolved that myself by kicking out Z2M and Mosquitto. So no longer have 2mqtt. But at least my system functioned for a week !!!

Now have spotted 2 of my 9 TRV's radomly changing temperature. Each is programmed identically, all are the same make and model. Both the culpritts always go high, eg they appear to set themselves sometimes at 21 and other times at 23. ( Initial setting usually 19)

Have done as others have suggested. Downgraded to 1.2.1 No fix Have used the BH childlock, No fix.

Any other suggestions from anyone. I hate to say this but are there any other UI that can be used. I took a quick look at An-Awesome and aslo Versatile thermostat, but neither even recognised the entity of my TRV!

I have climate sensors in each room, for temp and humidity and I would rather stick to using external sensor if possible.

But having 2 rads in the house decide that they want 23 degrees in the middle of the night and in 2 rooms which are empty is quite a lot of wasted gas.

thanks

Simon I have 9 TRV's. Recently migrated to 1.4 after a different problem

paulbrause commented 10 months ago

The BT child lock function did not help me, only the downgrade of BT to version 1.2.1 and BT UI to version 2.1.1 solved the problem for me. No abnormalities for about 1 week. (only zigbee-devices via zigbee2mqtt)

denbus2023 commented 10 months ago

The BT child lock function did not help me, only the downgrade of BT to version 1.2.1 and BT UI to version 2.1.1 solved the problem for me. No abnormalities for about 1 week. (only zigbee-devices via zigbee2mqtt)

Same here, tried almost everything to fix it but nothing worked. What I did:

Remove all better thermostats and integrations
Install better thermostaat 1.2.1
Configure the thermostats
Never change any better thermostat setting after the initial configuration!!! That causes the same problem, even in 1.2.1.
update tot 1.4.0, now no problems at all for about 5 days.
I have not installed and used BT UI in this setup

g0mga commented 10 months ago

Thanks for suggestions.

I'll have a go at what Paul says and see what happens.

From: paulbrause @.> Sent: 19 November 2023 12:48 To: KartoffelToby/better_thermostat @.> Cc: g0mga @.>; Comment @.> Subject: Re: [KartoffelToby/better_thermostat] Target temperature in GUI changes by itself randomly (Issue #1097)

The BT child lock function did not help me, only the downgrade of BT to version 1.2.1 and BT UI to version 2.1.1 solved the problem for me. No abnormalities for about 1 week.

— Reply to this email directly, view it on GitHubhttps://github.com/KartoffelToby/better_thermostat/issues/1097#issuecomment-1817845426, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANO7EGP24HSSU7AHU7YGI2DYFH53FAVCNFSM6AAAAAA6FUNTUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXHA2DKNBSGY. You are receiving this because you commented.Message ID: @.***>

g0mga commented 10 months ago

that didnt work either for me. Same 2 trv's changed their own set points 4 times in 2 hours. Not sure its going to help me in my situation to remove the BT UI, surely I would no longer be able to have access to external room thermostat.

Are there any straight forward scripts around to pull the current room temp from my climate sensor and write that value to the standard HA TRV card without the need for BT.

maglat commented 10 months ago

The BT child lock function did not help me, only the downgrade of BT to version 1.2.1 and BT UI to version 2.1.1 solved the problem for me. No abnormalities for about 1 week. (only zigbee-devices via zigbee2mqtt)

Same here, tried almost everything to fix it but nothing worked. What I did:

Remove all better thermostats and integrations

Install better thermostaat 1.2.1

Configure the thermostats

Never change any better thermostat setting after the initial configuration!!! That causes the same problem, even in 1.2.1.

update tot 1.4.0, now no problems at all for about 5 days.

I have not installed and used BT UI in this setup

4 days ago, I switch out my Homematic IP devices with Aqara E1 (Zigbee) For the first time I started using ABT. I directly went with the latest version + latest version of the UI. Very quickly I received random temperature seetings all over the place. Luckely I found this topic. I followed your steps (besides updating to 1.4.0) and for now, It looks like, its working after the first 24 hours. In long term, I hope this issue get fixed so I can use the latest version + the ABT UI as well.

g0mga commented 10 months ago

I tried all the above and nothing worked. However!

I removed my Dell 5010 thin client and replaced it with a spare RPi4. I was always bothered by how long it was taking for restarts and it more often than not would not make backups, despite adequate memory. The thin client had dual core processor, 4GB ram and 32GB SSD. Enough you would think and should out perform a RPi4.!

I gave up with ZHA since I was unable to cure the erratic TRV behaviour. However I had previously given up with Z2M since there was some kind of issue with RAM usage that used to trickle upwards by the minute until eventually the whole system would crash around me. This problem did not exist with ZHA.

But with a RPi4 I re-installed HA, mosquitto and Z2M and all is well. The ram stays constant at around 20.5% usage and NO TRV's change whats so ever, in-fact they are far more stable than ever, each TRV within just a fraction of a degree from the setpoint at all times.

Fianally I get my life back!. Why any changes that I made should make a difference I do not know! The only major change is from an X86 based cpu to an ARM cpu.

Simon

SpecialT131 commented 10 months ago

The BT child lock function did not help me, only the downgrade of BT to version 1.2.1 and BT UI to version 2.1.1 solved the problem for me. No abnormalities for about 1 week. (only zigbee-devices via zigbee2mqtt)

Same here, tried almost everything to fix it but nothing worked. What I did:
* Remove all better thermostats and integrations

* Install better thermostaat 1.2.1

* Configure the thermostats

* Never change any better thermostat setting after the initial configuration!!! That causes the same problem, even in 1.2.1.

* update tot 1.4.0, now no problems at all for about 5 days.

* I have not installed and used BT UI in this setup

This also fixed it for me. HA 2023.11.3 Thermostat: Homeatic IP

Only encounter the problem in a group of thermostats (1 BT for 2 thermostats)

isibizi commented 10 months ago

The BT child lock function did not help me, only the downgrade of BT to version 1.2.1 and BT UI to version 2.1.1 solved the problem for me. No abnormalities for about 1 week. (only zigbee-devices via zigbee2mqtt)

Same here, tried almost everything to fix it but nothing worked. What I did:
* Remove all better thermostats and integrations

* Install better thermostaat 1.2.1

* Configure the thermostats

* Never change any better thermostat setting after the initial configuration!!! That causes the same problem, even in 1.2.1.

* update tot 1.4.0, now no problems at all for about 5 days.

* I have not installed and used BT UI in this setup
This also fixed it for me. HA 2023.11.3 Thermostat: Homeatic IP

Only encounter the problem in a group of thermostats (1 BT for 2 thermostats)

I can confirm, at the moment it seems that this workaround is working. I have BT Lovelace Card installed.

stavroskool commented 9 months ago

I have Danfoss Ally TRV's. Happened to discover BT just yesterday which I quickly installed. So I installed the latest and IT SEEMED TO BE WORKING FINE.

Only after I "touched" the thermostat with tweaks the same problem (target temp changed irrationally) was generated. So I am thinking that maybe the issue is the "new" installation. Installing an older version just resets some flags and then upgrading to latest should work. Maybe just uninstalling does not clears everything. degrage and upgrade does the job. If this is the case any version should work? For degrade?

I have not tried the child lock by the way

Also using the latest BT UI without any issues

saxxonian commented 9 months ago

Update on mine, all TRVs behave normally, that is according to the scheduler, during the day. At 00:00 hours though, some, randomly, jump to 21°C. This value isn't in any of the schedules! I created a group of all schedules that I use to toggle all off and on again, and it's fine till next midnight. Maybe that gives a clue to more knowledgeable users?

maglat commented 9 months ago

I wonder if its worked on this issue? the project feels abandoned.

g0mga commented 9 months ago

After at least a month, I have had no further issues of either:

a: gradual hour by hour increase in RAM usage b: Inconsistent and erratic behaviour of the BT integration

after switching from x86 based pc to RPI4 which is of course Arm based.

Maybe there is something wrong with the core. regards

SImon

From: maglat @.> Sent: 15 December 2023 13:42 To: KartoffelToby/better_thermostat @.> Cc: g0mga @.>; Comment @.> Subject: Re: [KartoffelToby/better_thermostat] Target temperature in GUI changes by itself randomly (Issue #1097)

I wonder if its worked on this issue? the project feels abandoned.

— Reply to this email directly, view it on GitHubhttps://github.com/KartoffelToby/better_thermostat/issues/1097#issuecomment-1857901903, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANO7EGN5P5PHEOVUKFI67WTYJRHULAVCNFSM6AAAAAA6FUNTUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXHEYDCOJQGM. You are receiving this because you commented.Message ID: @.***>

firebowl commented 9 months ago

I have exactly the same problem with one of my TRVs. I tested BT on one radiator for two weeks without any problems. Today I switched the other radiators to BT and one of the thermostats is constantly set to fantasy values. It's totally annoying, I don't feel like constantly checking whether one of my rooms is turning into a sauna. Is this project still alive or do I need to look for an alternative straight away?

matschbirne commented 9 months ago

I also had similar issues with randomly changing temperatures with "AI Time Based" mode. I deleted my BT and created a new one with "Normal" mode as @baskham suggested earlier and now the temperature value stays stable. I've noticed that just changing the configuration of the existing BT doesn't help.

firebowl commented 9 months ago

@matschbirne I'll try this!

NikGro commented 9 months ago

For me, the target temperature changed whenever the temp sensor became unavailable. I use zigbee temp sensors and when restarting the Z2M integration, they go unavailable briefly. During this period, the BTT cards also show unavailable. When everything is back, that's usually when the changes in target temperature are happening

KartoffelToby commented 9 months ago

Its possible that you need to set this advanced settings in z2m however this means i need to tweak the state reload on Startup because this Sounds Like a Bug

saxxonian commented 9 months ago

Its possible that you need to set this advanced settings in z2m however this means i need to tweak the state reload on Startup because this Sounds Like a Bug

Mine were set like that all the time, also while it is happening. What usually works for me is disabling and re-enabling the schedules! All goes back to what is set in the schedules. It tends to happen just exactly at 00:00 hours! Maybe this info helps?

schummar commented 9 months ago

I have some observations that might help solve this. I noticed that I got this problem with randomly changing target temperatures after updating some aspect of a Better Thermostat Instance. E.g. adding a window sensor. I happened until I restarted HA some time later.

I enabled debug logging and deliberately deleted an instance of Better Thermostat, then recreated it with a different name. After that I could see that the old instance was still active and reacting to target temperature changes.

So my suspicion is this:

The old instance is not cleaned up, so there are two instance active at the same time.
When one instance sets the target temperature on the real thermostat (Target Temperature Based), the other instance sees this change as manual change and therefore adapts the new target temperature as its own - checking for the context fails in this case, because the other instance's context is different of course:
```
# Check if the update is coming from the code
if self.context == event.context:
return
```

=> When updating the config or deleting an instance, make sure that the controlling loop actually shuts down. I am not deep enough into the code yet to understand where this goes wrong. But maybe the hint already helps.

Hapi-D commented 8 months ago

I have a single BT controlling four POPP TRVs. The BT is set on "Target Temperature Based", calibration mode "Normal". The BT setpoint changes at random moments to a probably random value, I observed changes to values between 17C and 24.5C. I am certain that I made no BT parameter changes immediately before the random change. Changing the BT setpoint back to the original value doesn't help, restarting HA does restore the original setpoint. Note: the BT setpoint changes. The setpoints of the individual TRVs are set by BT so I assume.

Additional information: the BT temperature setpoint is set by a single scheduler device. The scheduler device sets the same setpoint to two BT devices. Not both BT devices go haywire at the same time: one of them remains at the same setpoint, the other tries to cook me by raising its setpoint. I have seen both BT devices getting confused, not at the same time though. I just found out that by changing the temperature setpoint in the scheduler both BT devices get back in line and follow the scheduler provided (changed) setpoint. Restarting HA is not really required.

Because only one BT devices gets confused, not both, I assume that the BT device changes its setpoint, and that the scheduler maintains its original setpoint.

bartoszkaminski commented 8 months ago

I have this problem on 1.4.0 using Tado TRVs via HomeKit integration. Temperatures changes randomly, sometimes it's -1,5℃ sometimes +3,5℃. With 5 TRVs it happens on the daily basis. I'm using Target Temperature Based calibration with AI mode.

KartoffelToby commented 8 months ago

@bartoszkaminski is your tado only controlled by ha or is it connected to the tado Cloud or some homekit actions?

Keep in mind with target Temperatur calibration the offset is done by adjust the target Temperatur on the real device.

You can also Checkout the beta 1.5.0

tobimai commented 8 months ago

1.5 Beta seems to resolve it for me.

EDIT: Nope, it didn't. Only for a few days

dolezeldavid commented 8 months ago

My z-wave devices (3 of 7) are still changing the temperatures from 19C to 21C, even with the 1.5 Beta :-(

bartoszkaminski commented 7 months ago

@bartoszkaminski is your tado only controlled by ha or is it connected to the tado Cloud or some homekit actions?

@KartoffelToby it is connected to the cloud but I never adjust them in the Tado app. There's no schedule also.

I understand that with target temperature calibration Tado's temperature changes. This is intended. The problem is that it's the better-thermostat thermostat set value that randomly changes.

1Tomber commented 7 months ago

@bartoszkaminski are the thermostats misbehaving grouped into rooms in the tado app? I noticed when one changes the other one(s) follow and betterthermostat gets confused as the values change.

bartoszkaminski commented 7 months ago

@1Tomber I'm not sure if I understand. I have rooms setup in Tado app (can it work any other way?), each room has one thermostat. Temperature changes randomly and I didn't notice that any particular thermostat fails more often than others.

HansCPille commented 7 months ago

I apologise for my late reaction. Version 1.5 seems to have solved my problems: in 1.5 months no unexpected or unexplained setpoint changes. Good job, thank you!

Lejouz commented 6 months ago

I have the same issue with changing temperature and the feeling that is has something to do with the 'AI Time Based'. Still on BT 1.4. Upgrading to 1.5 beta now an will monitor how the situation changes. Below you can see the real temperature in the room measured with an external sensor and the way too low temp set by BT: Bildschirmfoto 2024-03-22 um 08 54 35

ww-audio commented 3 months ago

Hello there I use danfoss Ally termostats for my floor heating, the thermostats are sitting about 40cm above the floors in every room, the roomsensors (Danfoss Ally) about 2 meters away. Everything works perfect. What would be very interesting is to be able to use the weeather forecast temperatures for in about 3 days, which would allow to keep the temperature in the house more stable. Is there any solution somewhere? cheers Werner

KartoffelToby / better_thermostat