Temperature of BT itself always changing to maximum. #1079
Comments
|
had the same issue for all of my 14 better thermostat integrations. the temperature changes randomly to ~29° or ~7°, don't know why. |
|
same here. I am setting a target temp of e.g. 20 and then suddenly/randomly the target temp changes to e.g. 10 or 16.5. I have seen various new target temps...so no pattern at least to me neither on temp or when its happening. This makes this addon useless somehow...unfortunately |
|
currently i fixed this with 2 automations alias: Better Thermostate - fix to low temperature
description: ""
trigger:
- platform: state
entity_id:
- climate.better_buro_heizung
- climate.better_ankleidezimmer_heizung
- climate.better_badezimmer_heizung
- climate.better_duschbad_heizung
- climate.better_eingang_heizung
- climate.better_esszimmer_heizung
- climate.better_gastezimmer_heizung
- climate.better_keller_heizung
- climate.better_kinderzimmer_heizung
- climate.better_kuche_heizung
- climate.better_rumpelkammer_heizung
- climate.better_schlafzimmer_heizung
- climate.better_spielzimmer_heizung
- climate.better_wohnzimmer_heizung
attribute: temperature
condition:
- condition: template
value_template: "{{ trigger.to_state.attributes.temperature <= 18.0 }}"
action:
- service: climate.set_temperature
data_template:
entity_id: "{{ trigger.entity_id }}"
temperature: 19
hvac_mode: heat
mode: singlealias: Better Thermostate - to high temperature
description: ""
trigger:
- platform: state
entity_id:
- climate.better_buro_heizung
- climate.better_ankleidezimmer_heizung
- climate.better_badezimmer_heizung
- climate.better_duschbad_heizung
- climate.better_eingang_heizung
- climate.better_esszimmer_heizung
- climate.better_gastezimmer_heizung
- climate.better_keller_heizung
- climate.better_kinderzimmer_heizung
- climate.better_kuche_heizung
- climate.better_rumpelkammer_heizung
- climate.better_schlafzimmer_heizung
- climate.better_spielzimmer_heizung
- climate.better_wohnzimmer_heizung
attribute: temperature
condition:
- condition: template
value_template: "{{ trigger.to_state.attributes.temperature >= 23.0 }}"
action:
- service: climate.set_temperature
data_template:
entity_id: "{{ trigger.entity_id }}"
temperature: 22
hvac_mode: heat
mode: single |
|
I've experience the same but only with minimum temperature. Further BT then assumes that the real thermostat is off since 7 degrees (in my case with Essentials Model 120112) correspond to HVAC state off and switches to off itself. |
|
4yi: my automation runs multiple times for some radiators
|
|
Same problem here with Bosch and Aqara thermostats. @b2un0 thanks for the code. That is a workaround for the moment. 
|
|
Just found this in the logs, maybe it helps:
EDIT:
|
|
Hey, I have the same Problem. While I did not Review the Code yet I have the feeling like the problem might be caused by a mistake where instead of adjusting the real thermostat the BT gets adjusted. Then the real thermostat gets adjusted calling the same code thereby adjusting the BT aswell until the BT and real Thermostat reach either the lowest or highest possible Temperatur. |
|
Also had this in my logs at the same time when my thermostat was set to 30 degrees C: Then, also, it warns that no weather entity was found, not sure if it is related: My thermostat is: Xiaomi SRTS-A01 |
|
Same here, but only for one BT where a tuya thermostat is involved. When the BT changed to 25°C, this entry shows uo in the log: |
|
I have now set the tolerance value on 1st config page now to "0.3" rather than an empty "" value before and now I do see (again) target temps going wild. Funny fact is that I cannot reset the tolerance field again to be "empty" in the config now. |
I cannot get the tolerance back to "0". Not sure if that would help but now I do see various temp changes whioch did not happen before.... unsure |
|
Also happening for HomematicIP TRVs jumps to 30.5°C |
|
Same issue - using Aqara TRVs. |
|
I have tuya HY367 . same |
|
I will check it if I find the time. But time is rare at the moment. |
|
I had another case where my thermostat was set to 28.5, but the logs look different, then last time. I changed the tolerance value in the thermostat settings and then it happened. Logs: Might be a separate issue, not sure. But it also has the missing weather entity error. Just wanted to add one more datapoint. |
|
It seems like this behavior occurs when changing the tolerance. But only on devices that are already set up. On initial setup I don't see that problem. In my case a restart (not only config yaml reload) of HA seems to solve that behavior. On startup I get the following warning in the logs: Don't know if this correlates to this issue. |
|
I had problems with 35*C constantly overriding my setting too. |
|
I can confirm: a restart of HA seems to solve these random temperature adjustments BT makes to my desired temperature. |
|
@ovizii i need to prove my guess, everyone with this Problem use more than one trv (group) Looks like BT cant handle the Changes of more then one trv at this time, this was solved in the past, but looks like ha internal changed events. I will look for a fix asap |
Right for me. I had 3 BTs running fine, added a group (of 2 TRVs) and the problem started. |
The problem also only occurs with trv groups for me. |
The problem occurred for me with two different HA instances. |
|
I have no TRV groups. Only 5 thermostats and the same problem. |
|
Same as RAYs3T- 5 thermostats that are not grouped. |
I have no group and 5 TRVs running. |
Only 1 BT controlling 1 thermostat (MELCloud) in my installation, irregular jumps in BT setpoint here too. Could BT be setting its own setpoint rather than the thermostat to be controlled? I can't find any similarity's in the behavior other than the setpoint jumps is often in the same range it sets the MELCloud thermostat to. |
|
Same here, the BT thermostats just move around on their own. This morning my office (one TRV) was down to 13 degrees : The other day I was hearing my TRVs in the living room (group of 3 sonoff zigbee valves) opening and closing constantly so I looked and I could see the temperature setpoint just moving up and down every few seconds on it's own in the BT lovelace card. |
|
The problem started since I added a group to the thermostats. I removed the group from the original thermostat and the better thermostat and things look good now. |
Prerequisites
Hassio generic thermostat
2x Eurotronic SPZB0001 (with normal working firmware)
Description
Temperature of BT itself always changing to maximal allowed by main (Hassio generic) thermostat.
If i change it manually or via UI or via service command in few seconds it's again changing on maximal possible.
Same in heat and eco mode of BT.
Settings of thermostats does not impact, tried almost all combinations (sort of calibration, calibration mode, etc.)
Generic thermostat settings:
- platform: generic_thermostat name: Bedroom heater: input_boolean.bedroom_heat target_sensor: sensor.bedroom_climate_sensor_temperature min_temp: 12 max_temp: 20 ac_mode: false target_temp: 18 cold_tolerance: 0.5 hot_tolerance: 0 min_cycle_duration: minutes: 10 initial_hvac_mode: "heat" away_temp: 17 precision: 0.5Steps to Reproduce
HA 2023.10.1
BT 1.3.0
BT 1.2.2
UI 2.1.3
The text was updated successfully, but these errors were encountered: