TRV doesnt reach Temp
Opened this issue · 8 comments
Prerequisites
- TRVs: Kasa KE100 (via Tapo integration by petretiandrea)
Description
This is the Graph wich shows my Temps in the Bedroom of our Flat. In all 3 Rooms the same Problem, so i just use the Bebroom as an example:
It does not reach the Target 21°C and settles around 19-19,5°C. I realy dont know, if this is a BTT Problem or with the Tapo Integration or the TRV itself but it worked prior to using them in HA. Does anyone has a clue why that is ? Maby something i could try to get rid of the Problem ? I would love to hear back from you.
BTT Settings:
Which version of BT are you running currently? Did you try switching back to v1.6.1?
Without corresponding statistic graphs of your TRV in HA (setpoint temperature, actual temperature of TRV sensor, offset-value and ideally also valve position, if reported), it's hard to say anything about your issue.
Hey @folfy, I can try to provide this info in my case. I am also seeing the valves (Tado) slow down to mid-thirties heating percentages while a degree under the setpoint, then never really speed back up to hit it. This happens both in 1.7.0-b1 and 1.6.1, but only in certain rooms.
Two questions:
- I haven't been able to find offset value in HA, where should I find it? I assume this is very important and the rest means little without this graph.
- Is the heating percentage for Tado the valve percentage, or linearly related to it? It seems so, but I have never found an explicit confirmation.
I can elaborate a bit more about the setup here: I think part of this is the fact that the radiators in the rooms this is happening are seemingly underpowered and in badly-isolated rooms.
- Offset value usually would be an attribute/entity of your TRV device, called something like "local calibration" (just check your thermostats device page in ZHA).
- Idk about "heating percentage", but if that's the only percentage your valve provides, I'd assume it's the actual valve setpoint / percentage that we'd wanna know/see also.
If you need more help, maybe make a screenshot of your thermostats device page in HA.
It very well could be an issue of BT, but usually I know it's over-compensating/heating, but the opposite (you're 1°C under setpoint) is very odd, so that's why I'd love to see what BT actually is commanding to your TRV from the TRV's statistics graphs.
Hey @folfy,
A quick screenshot of what I could gather (no offset to be found in anything, I guess that's a Tado thing...). I can see if I can get it working with HomeKit, but then we might lose part of the other data.
BamiCharginStation is the Tado TRV's data, Sleep Room is BT.
Let me know what you think, or need!
Oh, might be that the local calibration attribute is not exposed / visible in the UI with Tapo I guess :/
I'd have to see the corresponding graph for the BT entity as well for that timeframe to rly say more, but on first sight it looks like maybe you're limited by the max. offset that is supported by the entity. I think ZHA limits it to +/-2.5°C, which often isn't enough.
a) Please downlaod/provide the diagnostic data for the affected BT thermostat, so we can say if that's the case (this export is broken in v1.6.1 and 1.7.0b1, so use b2 for this; also b2 has a bug with offset calibration not working, PR #1555 is pending, so you'll want to switch back again after, sry):
diagnostic data
IMPORTANT:
Download and paste the diagnostic data from your Better Thermostat Entity(s) below.
https://www.home-assistant.io/docs/configuration/troubleshooting/#download-diagnostics
b) Try target temperature calibration (this can avoid the limits stated above, ofc assuming that's actually the problem)
See also #1545 (comment) - to be put in FAQ
@KartoffelToby / @wtom RFC
I think we should automatically default to target based mode, if the offset is limited to just +/-2.5°C (i.e. less than lets say at least 5°C)? I dunno how big offset rly is needed for some cases, but if the TRV is somewhere enclosed, even 5°C can be very limiting.
Maybe also again generate a (acknowledgeable) repair indication for proposing switch modes, if we for example detect being bound by the limits too much. I.e. soemthing like offset == - offset max & (t_trv - t_sensor) > 0.2 for more than half an hour -> reached max offset, but trv still reading too high, so probably failing to heat properly over this
I'm back to version 1.6.1. I use Hama TRVs with the following details:
Zigbee Model: TS0601
Zigbee Manufacturer: _TZE200_h4cgnbzg
After updating to versions 1.7b1, b2, and b3, I experienced issues with some TRVs. In my bedroom, the TRV did not reach the set temperature. Similarly, in my bathroom, the TRV had the same problem and failed to heat up in the morning.
It seems that while the TRVs received the command to turn on, the calibration did not work correctly, preventing the rooms from heating as expected. However, with version 1.6.1, the TRVs work perfectly without any issues.