BT turns all thermostats in a group up to 30C if one thermostat are out of battery #1608
Assignees
Labels
Comments
|
Can you provide the actual debug log from Home Assistant/Better Thermostat, as described in the issue template (copy of it is also in #1568 (comment))? The Z2M isn't rly helping much unfortunately 😐 Probably related to the known issue: |
|
config_entry-better_thermostat-01JCQXRC55YR3XZAPYHD53NGPB.json I hope you can use this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In a group of multiple thermostats and an external sensor, if one thermostat runs out of battery, BT turn all thermostats up to 30C
This has now been experienced in two different groups. One group with 5 thermostats, and in a group with 8 thermostats.
In one example 'C2_COM_Galleriet1_1' is out of battery, and for some reason this causes it to go to 30C.
When BT is enabled the BT climate entity is then also set to 30C, which in turn turn all other thermostats in the group to target 30C
Entities in the group (with the BT entity disabled)
History of the BT climate entity - you can se when the battery ran out.
Steps to Reproduce
Expected behavior:
All thermostats with enough battery, continues to work and keep a normal temperature, only the thermostat with low battery could maybe have a weird behaviour.
Actual behavior:
All thermostats in the group incl. the BT climate entity is set to 30C and when you try to turn it down, it resets to 30C after a short period of time.
Versions and HW
Home Assistant: 2025.2.4 and 2025.2.5
Zigbee2MQTT: 2.1.1-1
Better Thermostat: 1.6.1
TRV(s): Aqara SRTS-A01 + 1 external sensor pr group: Aqara WSDCGQ12LM Temp & humidity sensor
Debug data
diagnostic data
{ <html><head><title>500 Internal Server Error</title></head><body> <h1>500 Internal Server Error</h1> Server got itself in trouble <script defer src="https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015" integrity="sha512-ZpsOmlRQV6y907TI0dKBHq9Md29nnaEIPlkf84rnaERnq6zvWvPUqr2ft8M1aS28oN72PdrCzSjY4U6VaAw1EQ==" data-cf-beacon='{"rayId":"919048705ea798eb","version":"2025.1.0","r":1,"token":"487d177cfcac4d5c9675f22604ef6048","serverTiming":{"name":{"cfExtPri":true,"cfL4":true,"cfSpeedBrain":true,"cfCacheStatus":true}}}' crossorigin="anonymous"></script> </body></html> }debug log
Log from the Z2M integration running the involved thermostat. The issues has been observed on two different installations of Z2M on the same HA installation (running 4 in total)
Log file attached:
9336c2b0_zigbee2mqtt_2025-02-28T12-04-12.065Z.log
graphs
Additional Information
The text was updated successfully, but these errors were encountered: