-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
All Valves stuck after target temperature is reached (happens every couple of days) #1520
Comments
Could you please provide graphs of the TRV climate entities controlled by BT during that time? Also, consider trying the v1.6.1 of BT, to rule out a bug in the beta version. |
Based on a quick scroll through your log, it seems your valves already try to compensate internally for the temperature change. Therefore BT compensating leads to overcompensation and overheating -> Try enabling "overheating protection" for now. Linear compensation mode would help you as well / even more, but is not done yet (PR #1522). Afaik these Bosch TRVs (and some others) would support an external temperature sensor. They would benefit from using "no calibration" mode, and us/BT simply providing them the sensor temperature via the dedicated input (also read Bosch requires it to be updated / sent at least every 30min, in order to be still considered). Unfortunately I don't have any of those eTRVs, so I can't rly implement or test this (yet) :/ |
Also, as far as I can see, the Bosch is supposed to support local calibration as well - This is supposed to be way better, since we just tell the TRV to consider an offset for the temperature sensor, instead of just "faking" some new target temperature value. This might interfere less with the already existing compensation coded inside the TRV, so you should give it a try. |
Hi @folfy Thanks for taking a look at it and for posting your ideas. Here is the graph of the climate entities: Regarding your last comment with the local calibration - where would I set this up? In zigbee2mqtt I noticed that the "Local temperature calibration" was set between 3-5C plus, which resulted in a "Local temperature" that was way higher than the temperature measured by my climate sensors and therefore completely off. For that reason, I set it to 0C now. In general, I would like BT to only consider the temperature measured by my separate temperature sensors that I set up in the configuration of the BT devices and basically ignore the temperature that the TRV itself reads. Did I possibly choose the wrong settings in that regard? |
The existing offset was probably reason why they kept heating, even though one setpoint went as low as ~17°C. Or your TRVs are having some other issue, because they sure shouldn't be heating anymore at that point 😅 The mode is set in the config flow of your BT entities (I recommend restarting HA after, just to be on the safe side). Unfortunately BT only supports ignoring all values, or full compensation (i.e. offset = t_external - t_trv) atm. I'm already working on a linear compensation, that discards the TRVs temperature. Still some stuff to do, plus maintainers seem rather busy for reviewing / merging it later unfortunately - #1522 |
Prerequisites
Description
The integration works well but every couple of days, this happens:
Once the target temperature is reached, the TRV valve stays stuck in its position. Even if the BT temperature is further lowered or even set to "off", the valve stays stuck. Here a screenshot of the history of both the BT device and the valve:
I found the only way to get it unstuck is to remove a battery and re-calibrate the TRV.
Steps to Reproduce
Expected behavior:
TRV valve should decrease once the target temperature is reached
Actual behavior:
TRV valve gets stuck
Versions
HA:
Core 2024.12.1
Supervisor 2024.12.0
Operating System 14.0
Frontend 20241127.6
BT:
1.7.0-beta1
Additional Information
BT configuration settings (similar for all my devices):
The text was updated successfully, but these errors were encountered: