-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Target temperature changing at random #1387
Comments
Same hardware (Aqara SRTS-A01) + same HA version + same issue. Target temperature is set to 22C. Value randomly change to 5C, to 27C. Heating mod change from heating to off randomly. |
+5 seems logical, my setpoint is 25 and temperature was changed to 30. |
Activate child lock on the BT settings should fix it. |
looks like this fixed it for me. what about the temperature sensor setting. keep internal or set to external. I set to external so when internal, the thermostat do not reduce heating on a wrong room temperature. I am aware that the external only is meant for the aqara native integration and setting to external inside home assistant wont receive any temperature data. what i disabled as well is the window detection which is handled by better thermostat as well. |
Regarding setting temperature sensor to external and thus preventing HA/BT to recieve the temperature reading from the thermostat. How then does the thermostat active? Does not BT achieve this by manipulating the setpoint in reference to the reported temperature from the actuator? Im interested in a definite answer for this as my actuator is mounted in a technical closet where the temperature sometimes is above 30 degree - exceeding the maximum setpoint of the actuator and thus preventing it from turning on the heating. --- EDIT --- LIKELY SOLUTION --- Realized after typing out my question that I can achieve what I want by setting the temperature sensor in Z2M to external and using the slider to set the temperature to a static 20 degrees. |
got similar problem with version 1.6 and 1.4, but with avm 301 and external tuya sensors. It randomly switches the target temperature. But there is a fix temperature, where he is goining back, its the target temp which is set from AVM in the 301. |
BT will change the Target temp based on the Sensor and TRV data, this is how it works ;) but sometime devices make false true events, so the childlock "hack" work, but the childlock shoud be enabled on the org. device. if someone can provide better logs i can figure out whats wrong. |
Just wanted to share, that setting the child lock in the BT Integration fixed my Issue that I mentioned in #1441. |
Disclaimer:
My first bug report, will updated with other information if I missed the mark here.
May also be resolved if anyone know where I can find the trigger for target temperature changes in BT.
Prerequisites
Aqara SRTS-A01
Output from Home Assistant Developer Tools state e.g.
hvac_modes: heat, off
min_temp: 5
max_temp: 30
target_temp_step: 0.5
preset_modes: none
current_temperature: 26.3
temperature: 25
hvac_action: idle
preset_mode: none
window_open: false
call_for_heat: true
last_change: 2024-09-09T08:27:01.815908
saved_temperature: null
humidity: 53
main_mode: off
tolerance: 0
heating_power: 0.0115
errors: []
batteries: {"sensor.bathroom_air_temperature": {"battery": "77", "battery_id": "sensor.bathroom_air_battery"}, "sensor.bathroom_air_humidity": {"battery": "77", "battery_id": "sensor.bathroom_air_battery"}, "climate.bathroom_floor": {"battery": "31", "battery_id": "sensor.bathroom_floor_battery"}}
friendly_name: Bathroom_floor_virtual
supported_features: 401
Description
Target temperature changing to 30 deg. C at seemingly random times. Strangely it only happens for one of two SRTS-A01 in my better thermostat setup.
Steps to Reproduce
Unknown, happens rarely and I have not found a pattern.
Expected behavior:
Target temperature to stay where it should.
Actual behavior:
Target temperature changes at seemingly random times to 30 deg. C.
Versions
BT: 1.6.0
HA: 2024.9.1
Additional Information
The text was updated successfully, but these errors were encountered: