Target temperature in GUI changes by itself #913
Comments
|
I see the same behaviour with my TV02 (_TZE200_hue3yfsn) This thermostats ZHA integration does not update it's internal temperature by itself. I've created an automation that switches the offline toggle every 10minutes (this updates all values). |
|
It would also be very nice if the temerature shown on the thermostat would be the target temperature set in home assistant and not the temperature set by bt to reach this temperature. As nedis can work with a tuya central, I think the thermostat (and others) should support this. Ideally one would be able to set the target temperature on the thermostat as well. |
|
I reverted to bt 1.0 beta and the problem is gone. |
To which beta version? |
|
1.0.0-beta |
All betas have a number. So which one? 🫣 |
|
I thought that is the number. Where do I find what you would like to know? |
|
I reverted to 1.0.0-beta56 |
|
Similar issue here. Automation changes target temperature to 18 at 1900hrs and 21 at 0600hrs but it is randomly changing itself. I installed BT for the first time yesterday so I wasn't sure if I'd misconfigured something but it seems potentially not.
BT 1.0.0 |
Is the valve opening /closing all the time. If so, try a HA reboot and see if that makes any difference |
Unfortunately ZHA doesn't track the valve state but I've rebooted HA anyway and it is still happening. Edit: It is altering the TRV target temperature therefore it's safe to assume that the valve is being actioned. |
|
Child lock should prevent it in the BT options. Can you try? |
Thanks, that does appear to have stopped the problem. I will continue to monitor. |
|
It worked for a bit but it's back up to 35 degrees again unfortunately. |
|
I got the same problem. Juste delete the thermostat from integration and recreate it. If it doesn't work, try to unpair and pair again the thermostat in Z2M. It worked for me. It usually happens when you change the options in BT integration. |
|
I believe I'm having the same issue where BT is changing it's own temperature (seemingly randomly) but with Tado Homekit TRVs rather than Zigbee ones. Going to delete & recreate them and turn on child lock.... Can't see anything in the logbook why it changed. |
|
I‘m having the same issue with an Aqara Thermostat E1 |
|
|
Now you mention it, mine started misbehaving after I reconfigured the integration to add the external weather entity. I’ve deleted and re-added both the TRV and BT and so far it is behaving as expected. |
|
I also get this on my POPP/Danfoss. Have tried reinstallations, grouping, non-grouping, childlock and everything and nothing works. When outside temperature isnt changing that quick its usualy not happening but with large drops below zero for example it seems to push the temp up to +35 direct! Im not sure and cannot prove it but I get the feeling that its connected with outside temperaturechanges in some way. |
|
I have the same issue with POPP/Danfoss, but in a minute interval. Restarting HA, deleting and adding the Better Thermostat entity, childlock, non-grouping, not setting outside temp. settings, ... did not help.
|
|
@Kukuruts did you delete and add the Better Thermostat and then leave it. It looks like it could be going back in to reconfigure it causing the issue. I recreated mine and have left it alone and it seems to be stable now. |
|
@CHARL13is Yes, I tried that as well, didn't help. What did help in the end was to recreate all my Better Thermostats, set the calibration mode to "normal" (I used "AI Time Based" before) and then restart HA. |
|
Hum indeed, installed BT for the first time yesterday, and I wasn't sure why would it change change the target temperature I set, seeing nothing in the documentation about that. |
|
My thermostats are changing their target temperature as well by them self. BT 1.0.0 release
|
|
Trying to help debug I have setup a few different TRVs:
I have a theory that whenever a setting is changed it 'checks' the current temperature of the TRV and resets the thermostat to match. BT tells Tado to heat to 25c when it wants to 'aggressively heat', then I am wondering if BT reads back the 25c as a change it should be listening to (essentially listening to it's own instruction). Without heavily digging through the code I am unsure if this is the case, but it certainly looks like it. Update, I setup child lock on all the TRVs and they still have randomly increased to 25 (the max for a tado TRV) |
|
I also see this behavior. I have two of the same Nedis TRV's and one works perfectly now that i turned on overheating protection (before it would agressively heat the room and overshoot but approx 3 degrees.). However one of the rooms seems to have randomly changing target temperature :( the other seems quite stable. First i thought i was hitting the card in the mobile interface by accident by scrolling but sinc ei set it last night before sleep and this morning saw it had changed by itself in the middle of the night that theory is out. What i can say is both TRVs are identical in the BT setup. today i'll try to re-setup the problematic room from scratch and see what this does. Is there any debug info i could/should provide that makes sense ? As can be seen below it randomly changes the target temp at 04:00 for no specific reason. Hoever it does seems to follow a kind of pattern in regards to the heating curve. So perhaps the TRV target temp is somehow getting set as the BT target temp sometimes ? It looks like it hits target temp and tries to compensate almost like the internal TRV temp likely does.
|
|
Maybe this can help: I've integrated my TRV with ZHA and found the following in the System Log: This is fine and also works. But when I would remove BT and reconfigure it, there would be a warning for both the old (deleted) and the new configuration. At one time I found a warning for 4 different BT configurations but only one was actually there. These incorrect warnings disappear when Home Assistant is restarted. Could it be that after each reconfiguration (and probably also delete and re-add) the old configurations stay active until Home Assistant is restarted? Maybe they interfere with the target temperature calculation and set incorrect values. |
|
Same problem here with HMIP-eTRV. |
|
Still get the same problem temp goes up to 28C by itself with 1.01v |
|
Same here, worked around the problem writing automation to bring my old temp back(have to set the proper temp there) but at least doesn't heat my house to 35*C :D |
|
Same problem here with one of six HMIP-eTRV. Five BT installations works well. |
|
I have the same problem. One of my two Better Thermostat integrations is acting up. I set the target temperature to 19.5 degrees, and a few minutes later it suddenly jumps to 29.5 degrees. Same sensors - Same thermostats. The only difference is that I control 1 thermostat in the living room and two in the office. In the living room - no problems. (I had noticed the problem before and therefore disabled the integration (i.e. also the 0 before). ) |
Do you know if the ones having this issue uses the generic adapter? For my case all thermostats fallbacks on the generic adapter and I think more people with this problem also have the generic. Might be something connected to that!? |
|
I had the same problem and it seems to have stopped after I excluded the non better thermostat in Homekit and only included the better thermostat. Now it seems to work and doesn't change target temperature randomly. I use Zigbee2mqtt with Aqara E1 TRV and Danfoss Ally. |
|
I just setup BT some days ago and have the same issues with my tado Thermostats. I then noticed that the thermostat keeps heating / stops heating, and the temperature on the display jumps back and forth between 21.5 degrees and 18 degress. After a HA restart everything looks fine for now. I'll keep an eye on that. |
|
same here, I'm going crazy with the target temperature in the last two days. Going to remove it |
|
Had the same issue and as some other already mentioned, I was able to solve it by removing the homekit integration. |
|
The problem for me still exists. BT worked fine after initial setup. Then I tried to tweak some things (aggressive mode, tolerance) and after that it changed the target value by it self. A reboot may have fixed it for now, but is this really the solution? If so, there should be a hint to do a reboot... BT is version 1.4.0. (installed on 01.12.23), thermostats are Hama (_TZE200_h4cgnbzg). Two TRVs in the sleeping room set up as one BT, and anothter TRV in the bathroom, set up as one BT. |
|
@MadCyborg315 I siwtched to Versatile Thermostad, which unfortunatley has less functions then BT but works without any issues on my end. |
|
Hi there, same issue for me. After initial setup all worked. Then changed the calibration mode and the TVR changed itself to 22.5 or 29.5°C. I rebooted, reintegrated the BT part but nothing helps. I will look into Versatile Thermostat, thanks for the suggestions @xTim18. I'd be pretty happy with BT, but when I wake up sweating in the middle of the night, thats a no-go. |
|
Yeah pretty much did the same thing. So many issues with BT it's a no-go especially when it comes to your comfort/bills and time wasted on trying to sort out odd problems. |
|
I had the same Issue earlier last year when i was on another Version of "Better Thermostat". It only occured on one single Aqara Thermostat. Then i updated BT to the latest version at that time and I think I also updated HA and the problems were gone. I am still on that BT version now. In the last days I updated "Home Assistant" and suddenly the problem was back on another Thermostat. All the others were fine. Sudden changes of target temperature to 30°C in the middle of the night. Always around 1:50 am to 2:15 am. Random changes of 1°C. You know it. A living nightmare :D Seems like I got rid of the problem now. At least I didnt have any problem now for 24hours. -Reconfigure the BT device of that Thermostat I did the following and it DID help. (i don't know which of the both though)
No problems so far. But Im watching on the Dashboard anxiously every hour :D I hope I'm fine now. These kinda things driving me nuts. |
|
problem also reappeared for me on new sonoff trvs |
|
Getting the same Problem with my brand new sonoff TRVs. |
|
I have same problem with Aqara TRV with homekit integration. Logger: custom_components.better_thermostat.events.trv '<' not supported between instances of 'float' and 'NoneType'` Edit: I finally decided to remove BT and then I set my TRVs to correct values. Aparently they kept on going crazy. I suspect it's indeed the homekit integration, because it's based on Aqara app which means both HA and Aqara are trying to control the TRV, and due to the delay in communication, the signals are missinterpreted. Just a guess. Haven't restarted HA yet. |
|
Happens to me too. I've installed BT (1.4) yesterday and got target temperature changes to seemingly random values after editing tolerance. HA restart and "child mode" fixed nothing, but removing configured thermostat and adding it again fixed the issue for me. Btw, why this issue has been closed? Is this supposed to be fixed? |
|
Ditto here with Aqara E1 and BT deciding by itself what temperature is better for me :-( |
|
I have the same problem here with one of my aqara devices. It seems there are multiple people effected using aqara thermostats. |
|
@KartoffelToby It might be a good thing to re-open this considering so many people having problems with the same thing and clearly bug has not been fixed, |
|
The temperatures have been constant since I updated HA Core and OS yesterday. |
For me as well, have installed sonoff TRVs all over the house and all of sudden living room target temp changed to 35 degree. |
|
I thought I was alone until I discovered this but I see the issue is closed? |
|
Yeah, it's a shame the developer is just not acknowledging this and ignoring the issue. I recommend you switch to a Versatile Thermostat. It's by far more reliable. |
|
I have been struggling with the same issue. It suddenly appeared. I didn't change anything really. I'm using tado x through matter integration. I tried to child lock idea. First it didn't work. But going into configuration again, for some reason, the settings were not saved properly. I enabled child lock and double-checked in configuration again so that it is enabled. Now it seems like it is fixed. Will report once more after observing longer. |
and others
Prerequisites
{ "home_assistant": { "installation_type": "Home Assistant Container", "version": "2022.11.2", "dev": false, "hassio": false, "virtualenv": false, "python_version": "3.10.7", "docker": true, "arch": "aarch64", "timezone": "Europe/Berlin", "os_name": "Linux", "os_version": "5.15.0-1023-raspi", "run_as_root": true }, "custom_components": { "better_thermostat": { "version": "1.0.0", "requirements": [] }, "hacs": { "version": "1.29.1", "requirements": [ "aiogithubapi>=22.10.1" ] } }, "integration_manifest": { "domain": "better_thermostat", "name": "Better Thermostat", "documentation": "https://github.com/KartoffelToby/better_thermostat", "issue_tracker": "https://github.com/KartoffelToby/better_thermostat/issues", "iot_class": "local_push", "version": "1.0.0", "config_flow": true, "dependencies": [ "climate", "recorder" ], "after_dependencies": [ "climate" ], "codeowners": [ "@kartoffeltoby" ], "requirements": [], "is_built_in": false }, "data": { "info": { "name": "Office", "temperature_sensor": "sensor.tz3000_xr3htd96_ts0201_temperature", "off_temperature": 20, "humidity_sensor": "sensor.tz3000_xr3htd96_ts0201_humidity", "outdoor_sensor": "sensor.temperature_outside_temperature_2", "window_sensors": "binary_sensor.tz3000_au1rjicn_ts0203_iaszone_2", "weather": "weather.forecast_home", "window_off_delay": 15, "model": "TS0601" }, "thermostat": { "climate.thermostat_office_thermostat": { "name": "Thermostat Office Thermostat", "state": "heat", "attributes": { "hvac_modes": [ "off", "heat" ], "min_temp": 7.0, "max_temp": 30.0, "current_temperature": 24.5, "temperature": 21.5, "hvac_action": "heating", "system_mode": "[<SystemMode.Heat: 4>]/heat", "occupied_heating_setpoint": 2150, "friendly_name": "Thermostat Office Thermostat", "supported_features": 1 }, "bt_config": { "calibration": "target_temp_based", "calibration_mode": "default", "protect_overheating": false, "no_off_system_mode": true, "heat_auto_swapped": false, "child_lock": false, "homaticip": false }, "bt_adapter": "zha", "bt_integration": "zha", "model": "TS0601" } }, "external_temperature_sensor": { "entity_id": "sensor.tz3000_xr3htd96_ts0201_temperature", "state": "20.6", "attributes": { "state_class": "measurement", "unit_of_measurement": "\u00b0C", "device_class": "temperature", "friendly_name": "Temperature Office" }, "last_changed": "2023-01-23T09:58:25.916898+00:00", "last_updated": "2023-01-23T09:58:25.916898+00:00", "context": { "id": "01GQF114BW58B0M8A62JRX88C6", "parent_id": null, "user_id": null } }, "window_sensor": { "entity_id": "binary_sensor.tz3000_au1rjicn_ts0203_iaszone_2", "state": "off", "attributes": { "device_class": "opening", "icon": "mdi:window-closed", "friendly_name": "Window Office" }, "last_changed": "2023-01-23T07:33:31.780136+00:00", "last_updated": "2023-01-23T07:33:31.780136+00:00", "context": { "id": "01GQERQT041Z8P3GM07Q407P23", "parent_id": null, "user_id": null } } } }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. The warmer the room gets, the less this happens. So once it is about 20° and the desired temerature is more or less the temperature of the valve, the target temperature will not be set to a much higher one anymore. Before Version 1.0.0 this did not happen.
Steps to Reproduce
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 1.29.1
BT 1.0.0
BT UI 1.0.3
Logfile attached
logfile 2023 01 23 10 35 26 034.txt
The text was updated successfully, but these errors were encountered: