j’ai eu du mal à faire la mise à jour moi aussi .
En désactivant toute les scènes / nodered …. ,les mises à jour se passe sans problème même à grande distance
Z2M shows a new firmware update for the TRVZB:
Stack: 1.4 build 1.
Has anybody tried it?
Where is the changelog?
I allready have version 1.4 and no problems:
installed version 5120
new version 5121
2 Likes
Here’s the changelog for 1.4.1:
1.4.1 is it worth updating? does it anything good?
I still have two TRVZB with 1.4.0 and one with 1.3.0 and no update available…
1 Like
I’ve installed v1.4 on three TRVs.
I only use them in Home Assistant.
With the previous version (1.3), trying to adjust ‘valve open %’, ‘valve close %’, or trying to select ‘External temperature sensor’ resulted in a message, or ‘valve did not respond to command’ message. (Or something similar).
With v1.4, these all work when used in HA.
With open and close both set to 100%, the valve responds as expected.
If these are both set to 0%, the valve actually operates in an opposite manner.
IE. If there is a request for heat, (setpoint > measured) the plunger extends and closes the valve.
When measured > setpoint, the plunger retracts, which would open the valve.
They can be set anywhere inbetween.
‘External temperature sensor’ can be selected, but the external temperature value, (from a SNZB-02D for example), needs to be passed using an Automation in HA.
So v1.4 seems to work fine.
However:
I don’t use boost or window open.
I don’t use the app.
I don’t know what v1.41 provides.
I have 6x, half of them shows 1.4.1 update but when I try, it prompts “Success” and thats all. Can’t update from v1.3.0
As per my preivious post:
I updated three TRV’s to v1.4, it took around 30mins each to complete.
I use the ‘External Temperature Sensor’ selection to provide room temperatures from SNZB-02D’s for two units.
However, one of those yesterday and the other today, randomly switched from using External sensor to the internal measurement.
The switch did not appear to have changed in HA, but switching it off and on again, enabled the External temperature value again.
Does v1.41 address that issue?
I’ve updated one TRV to v1.41 to see if its any different.
Thanks.
Well, the TRV I updated to v1.41 has switched again from External to Internal temperature sensor.
Didn’t take long!
These TRV devices are just too flaky to work reliably in any system.
I’ll have to ditch them and go back to Drayton Wiser again.
They are more expensive, but at least reliable.
I’ve had thought.
Is there any mechanism in the TRV that would switch from External to the Internal temperature sensor, if a value wasn’t received within a specific time frame? The way my update works at the moment, is only when the SNZB-02D sends a value, it gets sent to the TRV.
I’ll try adding a timebased update and see if it has any effect.
It would be nice to use these devices.
Good morning, I updated to version 1.4.1, but I can’t find the boost mode or the new features when I log into the trvzb, as shown in the images released. Why? Furthermore, only 2 out of 5 valves found the update. Why?
1 Like
Hi, I was struggling with the same issue for a long time, but then found on some forum that these TRVZBs has inner logic which can’t be disabled, that in case if there were no temparature updates from external sensor for 2 hours, they are switching back to internal sensor. I fixed this issue with very simple automation in HA, which sends current temparature every 2 hours, and since that it works quite smoothly.
2 Likes
Thank you for this information and pretty much confirming, my suspicions.
I have added a timed update now and will continue to montior them.
It’s unfortunate, info like this isn’t generally published by the manufacturer. It would save a lot of hassle and subsequent criticism which is not really appropriate.
I really would prefer to use these TRVs to provide a ‘passive’ temperature control. I can set a simple schedule with two or three max temperatures at times during the day, so these radiators use heat in the system when it’s called for elsewhere.
It’s far less aggressive than the Wiser system. That is either maintaining a setpoint or just shuts the radiator off. I feel that it is necessary for one room, but doesn’t work well as a system if all rooms are controlled like that.
So, really good news.
Thanks.
2 Likes
I’m in the same situation, three valves show me the new functions, but all the rest don’t! Anyone know what to do?
Bonjour
impossible d’effectuer la mise à jour de la version 1.4.0. à 1.4.1 sans devoir ré appairer les vannes.
Hi, I’m testing version 1.4.2. The app still doesn’t show the boost mode or the percentage of the TRV head that’s open or closed. It’s a Sonoff-Pro gateway, the current version. You can only hear it open or close gently, which means the PID is working.
Updated one TRV to 1.4.0 and I lost Temp Calibration. 
Wait for iOS eWeLink update, if it helps (5.20). But this is a mess. Also other TRV does work well if controled via scene. It sets new temperature, but does not open valve until I change temperature manualy.
Hi,
I would like to report that an issue already mentioned by several users is still present on the latest firmware of the Sonoff TRVZB (tested on versions 1.4.0 and 1.4.2).
When configuring the device to use an external temperature sensor, the valve does not properly switch to the “external” slot.
Instead, it forces the parameter to external_2, and it is impossible to revert to “external” again.
I have tried the following without success:
-
changing the “temperature_sensor” option from Home Assistant
-
changing the option from Zigbee2MQTT
-
removing the device from Zigbee2MQTT
-
deleting its entry from devices.yaml
-
re-pairing the device
-
full device reset and calibration reset
The valve always falls back to external_2.
There is currently no known way to clear this internal slot assignment.
Functionally the device still works, but the behaviour is inconsistent and confusing, and prevents some integrations from detecting the correct external temperature slot.
Could you please confirm whether this is a known firmware limitation, and whether a fix is planned so that users can set the temperature sensor to “external” reliably?
Thank you for your support.
FYI.
I have three TRVZB units, v1.4.1, with External Temperature selected in HA on a RPi4.
Core 2025.12.1 - Supervisor 2025.12.2 -OS 16.3
I don’t use Zigbee2MQTT.
I was using a Sonoff Zigbee Dongle-P and they were working, but have just switched that out for a ZBT-2. They’re still working.
I added a timed function to ensure a value was being sent from a SNZB-02D to the TRVZB, at least every 30mins and that seems to have cured the ‘apparent’ random switching back to the Internal Temp. sensor, that I was experiencing. My control is fairly simple with two Automations, set to run at different times of the day, which send different temperature set point values to them.
So for now, they seem to be stable and working.
What is the ‘External_2’ parameter you refer to?
I only see one selection available in the GUI.
What/where is v1.4.2 ?
I don’t see any reference to a later version than v1.4.1
Check out the Z2M documentation. Unfortunately, that’s all I know.
Ok.
If you don’t use Z2M for other things, it may be worth dropping it and just use native ZHA then.
That seems to work.