Hi All, I have a few TRVZBs, sometimes the running state is not correct, so says heating when it’s closed or idle when it’s open. The running state is fairly important to my automations and is normally fixed by flicking it to heat or off where the change is picked up. Today, it’s not changing from idle though, any ideas?
1 Like
Same problem
Same for me.
From my observation, I think it comes from changing the setpoint.
While the valve is opening or closing as needed by the setpoint change, the running state is not updated. For example, you are heating, then change the setpoint where current room-temperature lies in the hysterisis interval. The TRV closes as expected but still reports heat as running state.
That’s really a problem, as Sonoff TRVs don’t expose their current valve position, and so the running state in combination with the open/close limits is the only way to actually guess what it’s doing.
Really hope that gets fixed soon, as internally the information should be present. Of course, exposure of pi_heating_demand would be even better.
1 Like
same here