You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before creating any new issue, please use the search function, and make sure your problem or feature request hasn't already been reported before. Merging duplicates is also quite some work, that we could spent on actually fixing issues.
Known issues
This is a short summary, of the most common and critical issues currently. The list refers only to issues in the latest release and beta version, others are removed.
Critical
#1195 - BT not heating after window closed (with "5°C instead of off" enabled, or if TRV does not support off mode) #1314 - Tolerance is not working #1474 - External Sensor updates are not processed in a timely manner #1511 - BT can get stuck in a loop and lock up HA (if e.g. the TRV is not responding/offline) #1410 - Local calibration sometimes stops updating till TRV temperature changes again (if TRV doesn't respond to the changed calibration value, e.g. common bug observed in SONOFF TRV with Z2M) #1580 - AI calibration: Big drops in temperature in short heating periods over 1min can cause BT to never start heating again
Major
#1545 (comment) - TRV doesnt reach Temp (issue of offset calibration with some TRVs in ZHA: only +/-2.5°C calibration range allowed, use offset mode or report issue to ZHA to expand offset range to what your TRV rly supports) #1532 - Temperatur changes without manual change (usually an issue with the TRV, try enabling child lock in BT) #1500 - Eco mode can be enabled, but doesn't turn on BT (if heating wasn't already enabled before) #1469 / #1569 - Diagnostic data export broken in v1.6.1, v1.7.0b1 and v1.7.1b3 #1588 - BT crashes when cooling device min/max temp is higher/lower than expected
Minor / feature
#1383/#1431 - ignore sensor if unavailable (you have to check the logs to find out which connected entity is unavailable / blocking BT startup) #1530 - Warning "setting option flow config_entry is deprecated"
How to report on known problems
If you find a similar issue, and you just want to indicate that you have the same issue, please use the "thumbs up" reaction on the issue. If you got more details than already reported, then provide an actual description of your problem/situation in the same issue. Please really try to also include logs and details of your setup, as indicated in the copy of the bug report template below. This is very crucial information and data.
FAQ
This is supposed to be summarized up and included on the webpage. For now there's an FAQ label with the corresponding issues to be added there, which can be found here.
The text was updated successfully, but these errors were encountered:
This is already presented to you when filing a new bug report issue, but in case you wanna provide feedback to an existing issue: Here's your reference what we would need, and how to get it.
Please take care to fill the data as complete as possible.
The more information you provide, the higher the chances are that we can reporoduce and fix the issue for you!
Description
<-- Description of the issue -->
Steps to Reproduce
<-- First Step -->
<-- Second Step -->
<-- and so on… -->
Expected behavior:
<-- What you expect to happen -->
Actual behavior:
<-- What happens -->
Versions and HW
<-- Provide both, HA (Home Assistant) and BT (Better Thermostat) version -->
Home Assistant:
Better Thermostat:
TRV(s): <-- Thermostat valve model(s) -->
graphs
For issues in regards to the calibration / control routines, it is very helpful to also
provide statistics graph screenshots from HA for the following entities (from the time you had issues):
BT climate entity
TRV climate entities controlled by BT
(optional) Valve opening states
Additional Information
<-- Any additional information, configuration, or data that might be necessary to reproduce the issue. -->
Before creating any new issue, please use the search function, and make sure your problem or feature request hasn't already been reported before. Merging duplicates is also quite some work, that we could spent on actually fixing issues.
Known issues
This is a short summary, of the most common and critical issues currently. The list refers only to issues in the latest release and beta version, others are removed.
Critical
#1195 - BT not heating after window closed (with "5°C instead of off" enabled, or if TRV does not support off mode)
#1314 - Tolerance is not working
#1474 - External Sensor updates are not processed in a timely manner
#1511 - BT can get stuck in a loop and lock up HA (if e.g. the TRV is not responding/offline)
#1410 - Local calibration sometimes stops updating till TRV temperature changes again (if TRV doesn't respond to the changed calibration value, e.g. common bug observed in SONOFF TRV with Z2M)
#1580 - AI calibration: Big drops in temperature in short heating periods over 1min can cause BT to never start heating again
Major
#1545 (comment) - TRV doesnt reach Temp (issue of offset calibration with some TRVs in ZHA: only +/-2.5°C calibration range allowed, use offset mode or report issue to ZHA to expand offset range to what your TRV rly supports)
#1532 - Temperatur changes without manual change (usually an issue with the TRV, try enabling child lock in BT)
#1500 - Eco mode can be enabled, but doesn't turn on BT (if heating wasn't already enabled before)
#1469 / #1569 - Diagnostic data export broken in v1.6.1, v1.7.0b1 and v1.7.1b3
#1588 - BT crashes when cooling device min/max temp is higher/lower than expected
Minor / feature
#1383/#1431 - ignore sensor if unavailable (you have to check the logs to find out which connected entity is unavailable / blocking BT startup)
#1530 - Warning "setting option flow config_entry is deprecated"
How to report on known problems
If you find a similar issue, and you just want to indicate that you have the same issue, please use the "thumbs up" reaction on the issue. If you got more details than already reported, then provide an actual description of your problem/situation in the same issue. Please really try to also include logs and details of your setup, as indicated in the copy of the bug report template below. This is very crucial information and data.
FAQ
This is supposed to be summarized up and included on the webpage. For now there's an FAQ label with the corresponding issues to be added there, which can be found here.
The text was updated successfully, but these errors were encountered: