# TRVZB F4/F5 Error not reported via eWeLink

**URL:** https://forum.ewelink.cc/t/trvzb-f4-f5-error-not-reported-via-ewelink/207449
**Category:** eWeLink App
**Created:** [January 28, 2026, 5:29pm UTC](https://forum.ewelink.cc/t/trvzb-f4-f5-error-not-reported-via-ewelink/207449 "2026-01-28T17:29:52Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![p.silhan](https://avatars.discourse-cdn.com/v4/letter/p/ec9cab/32.png) [@p.silhan](https://forum.ewelink.cc/u/p.silhan)
#### Post date: [January 28, 2026, 5:29pm UTC](https://forum.ewelink.cc/t/trvzb-f4-f5-error-not-reported-via-ewelink/207449/1 "2026-01-28T17:29:52Z")

</div>

Recently I run to problem with one of my TRVZB valves.

Behaviour - app reported valve as “Heating”, but it did not - temperature stayed cold in the room. Battery status was 32%.

On site I found it shows error F5 - valve not detected. I pressed middle button on the valve, calibration run again (Ad) and everything was fine - for a while. Then TRVZB reported F4 - battery runs out on the valve itself, not in the app.

What should be changed:

- report correct valve state, even if it is stuck and cannot be operated
- report error codes (F4/F5) to the app, so we can remotely see there is a problem
- report correct battery level - 32% looks fine, until it died one hour later
- in case of F5, let us press middle button remotely to check if it helps

Hope somebody from eWeLink/Sonoff staff reads this forum, as in case of NSPanel.