Replies: 15 comments 21 replies
-
|
Same for me with 4 TRVZBs, upgraded to 1.2.1 and all displaying F5 now. No reboot of home assistant during the process and the update appears to have completed successfully. Any joy in resolving? |
Beta Was this translation helpful? Give feedback.
-
|
Nope the problem still persists. Good to know that it is not due to the HA reboot though. |
Beta Was this translation helpful? Give feedback.
-
|
Yesterday I updated one of my 12 TRVZBs to version 1.2.1. Took almost an hour to complete. Afterwards I had to remove the batteries and restart the thermostat, but now it works perfectly. So it doesn't seem to be a general problem. |
Beta Was this translation helpful? Give feedback.
-
|
Same problem for me with 2 TRVZBs, upgraded to 1.2.1 and all displaying F5 now. |
Beta Was this translation helpful? Give feedback.
-
|
That's interesting - why didn't that happen to my TRVZB? Any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
I have 7 TRVZBs in total. 3 bought earlier in the year and 4 this month. All updated to 1.2.1 but only the 4 bought this month are showing the F5 issue. The 3 earlier ones are working fine on 1.2.1. Can't recall what the original firmware was on any of the TRVZBs. |
Beta Was this translation helpful? Give feedback.
-
|
I have 12 of them, all purchased in March of this year. They all previously had firmware version 4357 (1.1.5). Now I have updated all of them, but I only rebooted two of them after the firmware update by removing the batteries (they just stopped responding after the update - waited an hour and then rebooted). Now all thermostats are on version 1.2.1 (4609) and work perfectly. None of them showed any error in the entire process. |
Beta Was this translation helpful? Give feedback.
-
|
I have two of them and updated one so far, successfully. Both of them had 1.1.1 or whatever the older firmware from 2023 was. I already updated them to 1.1.5 a while ago, and one of them for some reason was still reported as having 1.1.1 on it after the update, but at the same time, there was no update-button next to it, so this might have been an issue with z2m entirely. Now it's updated to 1.2.1 and reports as such, the other one I didn't do yet. |
Beta Was this translation helpful? Give feedback.
-
|
Updated 11 TRVZB to 1.2.1 using Z2M OTA and all went fine with no need to reset or reboot. All were bought last year. Maybe it is a different hardware in new ones? |
Beta Was this translation helpful? Give feedback.
-
|
Had the same issue. What I found was that it is resolved when I push the TRVZB towards the valve while it adjusts. No idea why but that helped to solve the error. The TRVZBs were installed for about half a year, purchased at rhe end of 2023 and only showed the error after the upgrade. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing this, it worked for me too! I had to remove all fully, put back on the radiators and then push gently while they adjusted. I'm using the adaptors so not sure if that had anything to do with it but all working on 1.2.1 now. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately no permanent solution as the decalcification process re-calibrates and then it is again F5... |
Beta Was this translation helpful? Give feedback.
-
|
If I had read this before... It' annoying.. is there a possibility to revoke the update? I think it's running with Open valve then, right? |
Beta Was this translation helpful? Give feedback.
-
|
I updated 8 TRVs. All from v1.1.5 to v1.2.1. 2 were bought when the TRVs were first released and the other 6 were bought last month. 5 of them now work fine and 3 are stuck showing F5. One of my original ones and 2 from the new batch. So there isn't any consistency with how old the device is, or the starting firmware. All devices showing F5 weren't touched during the update. And I've tried the suggestions to get the error to go away but nothings worked yet. |
Beta Was this translation helpful? Give feedback.
-
|
My 12 TRVZBs are also mounted directly without an adapter. As mentioned above, all are now error-free on 1.2.1, only some had to be restarted after the update. So no hint either. |
Beta Was this translation helpful? Give feedback.
-
|
I did some testing. Swapping my TRV to a valve which doesn't give an error on a different TRVZB removed the error. It seems Sonoff altered the lowest point of the TRVZB so it doesn't bottom out on some of my valves. I suspected this when others reported fixing the issue by pushing down on it as it calibrates. I fixed the issue on all 3 of by TRVZBs showing F5 by sticking a small metal disk (1-2mm thick) to the plunger and reinstalling. The error went away on all |
Beta Was this translation helpful? Give feedback.
-
Hah, I used a two cent coin like that ages ago when a plain old "dumb" TRV didn't fully close the valve. :-) |
Beta Was this translation helpful? Give feedback.
-
|
Same for me, the coin worked it out straightforward. Strange is that only one over 5 valves had this issue after the update... |
Beta Was this translation helpful? Give feedback.
-
I had the same problem but I leaned the valve against a wall with a metal object on the black part. And it's fine. |
Beta Was this translation helpful? Give feedback.
-
|
Same problem. On one heater the updated valve showed F5. changed with a valve with previous firmware and this worked. Updated this new valve and it does not work again. Changed with another old valve and this time I’m not going to update anything anymore. This Chinese are really not able to write the firmware at all. |
Beta Was this translation helpful? Give feedback.
-
|
Instead of resorting to racism, maybe take the time to read the suggested solutions here and confirm you tried them all. |
Beta Was this translation helpful? Give feedback.
-
|
@superfrobo how did you downgrade? Thanks in advance! |
Beta Was this translation helpful? Give feedback.
-
No way to downgrade. I bought another valve with old firmware on it … |
Beta Was this translation helpful? Give feedback.
-
|
The best solution would be test the firmware with european standards before selling devices to european countries. But Chinese dont' like to comply. We buy any kind of rubbish from this country indeed. The above solutions are ridicolous... putting metal rings, pushing the valve while pressing the button. I payed hundred of Euro for these devices. If you would read the answers the gave me to my suggestion to improve their software you would creepy. |
Beta Was this translation helpful? Give feedback.
-
|
Just here to throw in a 'me too' just after I have ordered a stack more.. my current one breaks most firmware update. |
Beta Was this translation helpful? Give feedback.
-
Further to my quick 'me too' and after having changed batteries, left empty, removed and readded nothing seemed to work. I reached out to sonoff who were very responsive (which was reassuring as I have just ordered 5 more of these!) They confirmed it is a calibration error and apparently they know there is an issue post update. Asked me to ensure my adapter was as tight as possible. So I tightened up and then got some monkey grips and tightened up a small amount further.. and it worked! My trv is now functional again. Not sure what benefits the update has given me to be worth the extra faff/risk of damaging the fixings or value tho. |
Beta Was this translation helpful? Give feedback.
-
|
I also opened up a ticket to sonoff now as this is a annoying behaviour. It worked before 1.2.1 and still works on those were i stopped the upgrade. But all upgraded ones are useless and are currently replaced by the "old & dumb" thermostats to actually get my heating back to work. The tightening of the adapter is in my case impossible as the Danfoss RAVL adapter simply starts slipping when you go too far. |
Beta Was this translation helpful? Give feedback.
-
|
I did open one as well now. The more, the merrier ;) I just updated one thermostat and got it working by gluing a small piece of plastic onto the cylinder to make it reach the pin on the valve before displaying F5. Not a long term solution, but it does indeed seem like the reach of the cylinder has been decreased by the firmware update. I described this in the ticket, so I expect the firmware fix should be pretty straight forward ;) |
Beta Was this translation helpful? Give feedback.
-
|
I don't know if this can help any of you. I had the same problem and I fixed understanding that as I was missing a piece on my side: when I installed (without a proper doc from Sonoff) and because it was working with the previous firmware after the installation, I didn't take care to the little pin delivered with the adapter. |
Beta Was this translation helpful? Give feedback.
-
|
I think all of mine is doing this as well... would be much less of an issue if I could automatically detect it, but I can't find the zigbee specification for the TRVZB, which I know I've read before. Does anyone have an idea of where I could find it, or of a way to monitor the FS error code? |
Beta Was this translation helpful? Give feedback.
-
|
I have 8 trvs that were all working perfectly fine but have now all faulted to F5. The zigbee bridge is working fine so the issue has to relate to the firmware update!! |
Beta Was this translation helpful? Give feedback.
-
|
I ordered two new TRVZBs that had a newer firmware, it seems - same F5 error when installing, older ones (old fw, I guess...) work fine. |
Beta Was this translation helpful? Give feedback.
-
|
We apologize for the inconvenience caused. Our team is working on a new firmware update to address the issue with the TRVZB. To ensure the update resolves the problem without affecting a wider user base, we’re looking for volunteers to participate in a trial test for the new firmware to fix the F5 calibration issue. If you're willing to work with us, please let me know and send me an email. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately my home assistant was rebooted while a firmware update of SONOFF TRVZB Thermostat (from 4357 to 4609) was running.
Now the Thermostat seems to be broken and is not responding.
It switches between "CA" and "20°" several times before showing "F5". F5 means that no valve is detected, but it is installed the same way it was when it worked correctly.
A factory reset of the Thermostat (by removing the batteries and inserting them again while pushing the button) does not change anything.
Is there any way to reinstall or reset the firmware?
Beta Was this translation helpful? Give feedback.
All reactions