BT status does not match with default climate entity #1507
Replies: 4 comments
-
I think I might have a similar problem. I have 2 TRVZB in my living room and one of them shows the behaviour you describe. But only one off them. |
Beta Was this translation helpful? Give feedback.
-
I completely removed and re-installed BT these days and stopped tinkering with the offset on the device itself. I did not see this behavior since then. Might have been buggy calibrations. |
Beta Was this translation helpful? Give feedback.
-
Had the issue tonight again. Calibration stuck at -13° the hole night, without any re-calibration. The TRV was heating, but BT climate was idle. I am now fed up with this unreliable behavior of BT. |
Beta Was this translation helpful? Give feedback.
-
Based on my preliminary analysis, I consider the "AI time based" algorithm flakey at best - Try normal mode instead 😐 If you have issues related to the calibration/control loop, please enable debug mode for the BT integration, reproduce the issue (document when you have trouble), and provide the logs afterwards. That's the only way for us to diagnose what's going on, and it can provide valuable feedback for fixing / improving algorithms for your specific TRVs. |
Beta Was this translation helpful? Give feedback.
-
I am using BT for my Sonoff TRVZBs with external room temperature sensors.
BT's climate entity's hvac_action changes from heat to idle as soon as the room temp reaches the target.
But the thermostate valve remains open and the default climate entity still shows hvac_action: heating accordingly. As soon as the thermostat's internal temp sensor reaches the target it closes. It seems that the default climate entity overrules BT.
Calibration is set to Offset based and mode is AI time based
Is there something going wrong or did I fail to understand something?
Beta Was this translation helpful? Give feedback.
All reactions