For the curious: you do not need any of this to turn on a hose.
Back to devices.
At a glance
| Item | What we found |
|---|---|
| Valve | Sonoff SWV-NH, five in this house, one per hose bib |
| Radio | Zigbee, through Home Assistant’s own Zigbee integration and an SMLIGHT SLZB-MR5U coordinator |
| Flow | A turbine meter, reported in cubic metres an hour in steps of 0.1 |
| Position | Open or closed, as commanded, and a button on the valve |
| Moisture | None. The “water leak” and “water supply” entities are one status, not a probe |
| Battery | Reads exactly 100 percent on every valve |
| Auto-close on shortage | Reads unsupported on the firmware we have, so the switch is probably inert |
Every paired valve shows up in Home Assistant as a switch, not as a valve. That matters if you write automations against them.
Reading the entities honestly
- Leak and supply come from one attribute on the valve. They can only mean flow while shut and no flow while open.
- A valve opened for hours with nothing checking that it shut is the gap that the flow-while-closed watch closes. Adding a valve without its watch fails a check in our tests.
- Battery 100 proves nothing. Do not read a battery warning into silence.
Joining the mesh
The valves hang off the mesh like any other battery device: each end device attaches to a mains-powered router. If the router goes away, a valve has to find a new one, and it may not. The night this cost us a valve is in a post, and the layout is on the radio mesh page. At the time we found three of four working valves on a single router with no second parent, and a record of that is what we fixed first.
More on how they are used: watering.
Ask your assistant
Which valve used the most water last week, and was it over its own normal?
Your assistant compares each valve's gallons with its own four-week average, and says how many weeks it had.