SONOFF SWV real_time_irrigation_volume does not reset between irrigation cycles
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
The real_time_irrigation_volume sensor for the SONOFF SWV (and SWV-BSP) does not reset to 0 when a new irrigation cycle starts or ends.
Instead of reporting the water volume delivered during the single/current session, the value keeps accumulating across multiple runs, behaving like an ongoing cumulative counter rather than a real-time session volume.
What did you expect to happen?
real_time_irrigation_volume should either reset to 0 at the beginning of each irrigation session or report only the total volume delivered during the last completed cycle.
How to reproduce it (minimal and precise)
- Run an irrigation cycle on SONOFF SWV and observe
real_time_irrigation_volume. - Stop the irrigation.
- Run a second irrigation cycle.
- Observe that
real_time_irrigation_volumeresumes from the previous value instead of resetting to0.
Device details
- Device Model: SONOFF SWV / SWV-BSP
- IEEE Address: 0xf4b3b1fffe4df5e4
- Firmware Version: 1.0.4 (4100)
- Zigbee2MQTT Version: 2.13.0
Zigbee2MQTT version
2.13.0
Adapter firmware version
7.4.3 [GA]
Adapter
ZBDongle-E
Setup
Zigbee2mqtt on docker container
Device database.db entry
No response
Debug log
No response
Notes
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the SONOFF SWV/SWV-BSP device definition and the handling of real_time_irrigation_volume in the TypeScript source. Reproduce two irrigation cycles using the reported device setup, then verify that the sensor resets at the start or end of a cycle, with regression coverage for the observed accumulation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100