I’m experiencing an issue with my Sonoff Smart Water Valve and Zigbee2MQTT (z2m) integration in Home Assistant.
When I manually operate the valve using its physical button (to turn it on or off), the device doesn’t automatically report its new state to z2m. This results in Home Assistant displaying an incorrect, outdated status for the valve. However, I want to clarify that controlling the valve (turning it on or off) directly from Home Assistant works perfectly, and its state updates as expected in that scenario.
Interestingly, the valve does report its state correctly for other changes, such as when water flow is detected or stops. The problem seems specific to manual on/off actions via the device’s button.
Has anyone else encountered this with their Sonoff Smart Water Valve? How does your valve behave in this scenario? Any insights or potential solutions would be greatly appreciated!
Thank you for the clarification! Yes i meant that “expected behavior” was indeed what I had expected, i.e. sending status even though the change happened by pushing the device button.
I actually reinterviewed the device and now the status is correctly reported, so problem solved! I didn’t know about the page you suggested looking, so thank you for the tip!
However I have some issues with the measure “flow” and others. Until yesterday flow was reported then suddenly it stopped at 7.20pm. before interviewing, it was just not present at all in the UI of z2m: next to the measure in the Expose menu, there was no number nor icon. Now I see it there but it’s as “null”. In the Logs I see the JSON file that is reported as containing “null” for several measures. However, Battery is correctly reported.
Same here - I ordered 2, the first one works as expected, but my second one has the same issue as you describe. I have tried deleting it and re-interviewing it to no success. Going to keep trying, and might write to support.
Interesting observation - I think it might be z2m not syncing the state properly. If i click the manual button, then sync, the state updates. Otherwise it goes to the de-synced state. After re-configuring the device, it works like normal - strange.