Same here. Still no solution? Not to mention the external sensor issues — it keeps disconnecting and reconnecting. It was working so well before. Too bad I updated it. 
Hi everyone and the SONOFF support team,
I’ve started a new thread with a similar issue. In my case, I’ve updated both the ZBBridge-U (to v1.16.0) and the TRVZB (to v1.4.1). Now it’s unclear which update is to blame…
The cause of the external sensors (SNZB-02D, SNZB-02P) disconnecting from TRVZB has been identified. The issue was not with the new TRVZB firmware, but with the ZBbridge-U version 1.16.0 update . Technical support provided version 1.16.1 upon request, and there hasn’t been a single disconnection in about 7 hours now — before this, there could be several disconnections per hour. They promise an official release of version 1.17.0 in the coming days.
However, there’s still an unclear story with the TRVZB update to version 1.4.1 . Some devices received the new skin with the turbo mode, while others did not. It’s not clear whether the TRVZB or the ZBbridge is responsible for this.
Does anyone have any information?
1 Like
I have 1.4.2 and there is no turbo mode
To be honest, I personally don’t see the point of ‘Turbo Mode’ at all. My temperature reading comes from an external sensor. If the radiator hasn’t heated the room to the set temperature, it’s effectively in ‘Turbo Mode’ anyway. But aesthetically, having different skins on identical devices is a bit… 
P.S. However, the skin with the “Boost” button has a significant advantage: it displays both the current and the target temperature, which is undoubtedly convenient for visual information perception!
1 Like
Hello, i have an issue with trvzb 1.4.1 valves and zbbridge-p 2.8.0
As u can see from pic, the app shows the trvzb on heating mode and the scene that off the boiler is not running correctly. Tried to change to anti-freeze, manual with no results….always heating.
if I physically go to look at the display of trvzb it shows me correct mode (idle), so it seems an issue on communication between trvzb and bridge pro.
The only way to restore is to use boost function….sometimes it needs more than one activation but finally it goes on standby mode.
I am missing information on how much percent the head is open or closed.
Hi, I got the message that the new firmware 1.4.4 is available.
Does anyone have any news?
Currently only on one of 5.
Thanks
with the bridge-p at version 3.0.0 and the trvzb valve at version 1.4.4 the adaptive function has been added
I received notifications about the new 1.4.4 version on both of my TRVZBs, and when I update via the app or web it says “Success” but after refresh both devices are still on 1.4.1. Device IDs are a48010c132 and a48010c0b1.
One in three of mine has update
I don’t see any changes.
The changes will be visible when your gateway receives updates. The update schedule is provided in this blog.
1 Like
Even though Sonoff describes the new features introduced in firmware 1.4.4 and even provides an official so‑called quirk for ZHA, it’s still unclear how to perform the update in Home Assistant. OTA updates for the TRVZB are a sensitive topic among ZHA users, and there’s no indication this will change anytime soon. And although I’ve managed to set up daily scheduling through automations and pass temperature readings from external sensors, the whole setup feels like walking on thin ice.
Previously, I used TRVZB paired with an NSPanel Pro, exposing entities via MQTT, and that wasn’t smooth either. Add to that the communication issues with the eWeLink platform, and it’s hard to say which option is better or worse.
The conclusion is that the only things you can fully rely on are the physical knob and the TRVZB’s internal schedule — both work flawlessly. As for the automations I created, they may not be perfect, but they work and allow reasonably precise control.
@Archarr @Daniel_Zhan The real problem is the “Zigbee language” of the TRVZB, implemented so poorly that Home Assistant can’t interpret it correctly without a special patch (quirk). The main issues are:
-
Boost and Timer modes are fake — the device looks like it has three different modes, but in reality it only has one. The rest are just placeholders.
-
Some settings use incorrect data types — for example, something that should be a simple switch is defined as a number.
-
Temperatures are reported in a strange format — instead of normal degrees, the device sends values multiplied by ×100.
-
Some features are marked as “special,” but the device doesn’t behave like a special Zigbee cluster, which confuses Home Assistant.
-
Setting identifiers are random and undocumented — so they have to be mapped manually.
In short: the TRVZB does not follow Zigbee standards, which is why the quirk has to fix the logic, data types, and operating modes so everything works normally in Home Assistant.
Updated TRVZB to 1.4.4, ZBBridge-P to 3.0.0 and no changes in TRVZB settings?
How did you manage to do it? For me it’s just a loop of strange steps. I can repeat the process many times, just like in the attached video, and nothing meaningful happens.
1 Like
TRVZB must be close to ZBBridge
Oh, it definitely is. It couldn’t be any closer unless I unscrewed it and hung it directly on the NSPanel Pro. And yes — the TRVZB is fully awake, sitting there like a good student in the front row, and it still doesn’t help.
You can keep it awake, poke it, wave at it… the update process just shrugs and pretends it doesn’t see the device.
At this point it’s pretty much a well‑known Sonoff tradition. Anyone who survived the recent AirGuard TH firmware gymnastics knows the routine: a bit of patience, a bit of luck, maybe a ritual dance around — and maybe the update will finally go through.
2 Likes
Exactly my experience..
I read that for the new features to be used I need the NSPanel Pro upcoming update, but this should not be a reason not to be able to update the TRVZBs, right?
2 Likes