Just got another TRVZB thermostat and I’ve got a strange behavior with this one, the adaptive mode won’t stay switch on in the settings after I remove the batteries.
Even if I enable it and test it it still opens and closes completely, my first TRVZB does not do that with adaptive mode on and also does not loses the setting after the battery is changed.
The temperature, child lock settings remain unchanged after a battery removal.
What could be the reason that the adaptive mode won’t stay switched on after a battery removal? or even won’t switch on at all considering the behavior of the new TRVZB?
Both (old and new TRVZB) are running the the 1.4.4 firmware alongside with the ZBBridge Pro-P with 3.3.0 firmware.
Performed a full reset on the ZBBridge Pro-P. And started by re-adding the TRVZB’s first on a clean network. When starting with the first one that worked and did not have this problem I noticed the same behavior as the second one. Now both thermostats won’t work as expected. This seems to be a firmware problem.
Adaptive Mode is not stored inside the TRVZB itself. It’s a control mode managed by the ZBBridge Pro‑P/eWeLink. When you remove the batteries or reset the bridge, the TRV loses that mode and falls back to simple fully‑open/fully‑closed regulation.
Since both thermostats started behaving the same way after resetting the bridge, this is not a hardware defect. It’s the bridge losing its configuration. ZBBridge Pro‑P firmware 3.3.0 has a known issue: it can lose TRVZB configuration, reset control modes and fail to resync settings after re‑pairing. This behaviour points to a bridge firmware problem, not defective thermostats.
To understand your setup better, could you describe step‑by‑step how you paired the TRVs, what settings you changed, and what exactly you see in the app?
When I got the first TRV in May I don’t remember doing anything special besides basic procedure -installed it on the radiator correctly, then batteries and after that ran the initial calibration by short-pressing the wheel-button. After that I used the ewelink app, clicked the ZBBridge and pressed the add button. Rotated the wheel all over until it was displaying OFF and kept pressed the button until the wifi logo flashed, after the TRV was found I did the update (took a while) and when it was done I renamed it , set the correct room and activated the adaptive mode. I did the same with the new TRV.
What I quickly found out was the adaptive mode that was not working - to be more precise, I activate the toggle in the app but it’s not acting like it’s on (I can hear the motor fully opening and closing the valve). After starting some quick debugging involving batteries out and batteries back in I found out the toggle switched back to off.
During my debugging I also deleted all 15 devices, reset the TRV’s by holding the wheel-button and placing the batteries in and reset the bridge. Left the bridge without power for more than 15 minutes to allow cache/cloud session cleaning, and after starting fresh I got the same result (now with both TRV’s).
Is there any other method that I might missed during my debugging ?
Short update: I left the bridge without power for 15 minutes but I didn’t touch any other device. After powering up the bridge I found the adaptive setting stayed switched on (on both trv’s, but in reality both run fully open or closed ).
I repeated the same test but this time with batteries out from both trv’s. After 15 minutes I powered on the bridge and the inserted the batteries in trv’s. The adaptive mode switched back to off.
Are any beta firmware updates available that I may try?
With the kind of 35°C heat we’ve had in Europe lately, your TRVs are basically on summer vacation, and that’s exactly why Adaptive Mode won’t behave normally right now. When the room temperature is already far above the target, the TRVZB keeps the valve fully closed, so the algorithm has nothing to modulate. The full open/close movements you hear are just calibration, not real regulation. What you’re seeing is completely normal: with no heating demand, Adaptive Mode simply stays inactive.
Good to hear you’ve solved it. What you’re seeing now makes perfect sense: Zigbee2MQTT exposes the real “Smart Temperature Control” parameter, which actually enables adaptive regulation on the coordinator side.
On the ZBBridge Pro‑P this setting doesn’t exist - the “Adaptive Mode” toggle in eWeLink is only a UI flag and isn’t sent to the TRV, which is why the device fell back to full-open/full-close behavior.
So the difference isn’t in the TRV itself, but in how the coordinator implements temperature control. Z2M has a proper algorithm, eWeLink doesn’t. As far as a proper update is concerned, there simply isn’t one that could ever fix what you described. As far as I know, the thing you expect the update to do is something the ZBBridge Pro‑P is architecturally incapable of doing.
