Reviews
Part of Reading smart yard technology with a sceptical eye, 2027 edition
Smart Yard Technology: WaterSense S627 vs. S633
Compare WaterSense S627 and S633 for smart yard technology: which controller family each covers, the criteria they test, and what a label cannot prove.
When irrigation-controller spec sheets point to different test routes, compare the standard before comparing feature counts. This guide maps WaterSense’s weather-based path to ANSI/ASABE S627 and its soil-moisture path to ANSI/ASABE S633, names the criteria documented for each, and separates a verified label from model-specific claims such as zone capacity or offline behavior.
The two paths ask different questions; they are not interchangeable scores. For smart yard technology, that distinction keeps a spec-sheet comparison focused on the evidence each controller actually offers.
What S627 and S633 test
WaterSense covers two controller families: weather-based and soil-moisture-based. Weather-based controllers adjust run times using local conditions. The EPA’s weather-based controller criteria include irrigation adequacy (meeting plant water needs), irrigation excess (avoiding overwatering), and supplemental capability, including accommodating watering restrictions.
ANSI/ASABE S627, Weather-Based Landscape Irrigation Control Systems, was published in December 2020. EPA says it is consistent with the performance test method in Version 1.0 of the WaterSense weather-based specification. The original specification information also identifies Version 1.1, dated September 2021; keep a standard’s publication date distinct from a specification’s version date.
Certified criteria for weather-based controllers
- Irrigation adequacymeets plant water needs
- Irrigation excessavoids overwatering
- Supplemental capabilityaccommodates watering restrictions
- StandardANSI/ASABE S627, version 1.1, Sept 2021
Soil-moisture-based controllers measure the ground and block unneeded irrigation. Their WaterSense test path uses ANSI/ASABE S633, and the specification was finalized in February 2021. The documented criteria include a freeze-and-thaw criterion, a detail that matters when interpreting the test for cold-region use. This path evaluates a different control method from S627, so its results should not be read as a higher or lower score against weather-based models.
Soil moisture controller test criteria
- Function across moisture depletion levels
- Precision at preset threshold
- Response to soil moisture change
- Function after freeze and thaw
- StandardANSI/ASABE S633, Feb 2021
Match the certification to the controller’s inputs
Use the controller’s data method to identify which WaterSense path is relevant. A weather-data claim points to the weather-based family; a soil-moisture claim points to the soil-moisture family. Then check whether the exact model carries the WaterSense label, rather than treating a mention of a standard or test method on a spec sheet as proof of certification. The EPA WaterSense labeled-controller page is the reference for checking labeled controllers.
Some products use weather and soil-moisture data concurrently. Those must be certified under both specifications to carry the WaterSense label. In a comparison table, record the model, the label status, the controller family, and the named standard separately. If documentation names a specification version, record that too; do not assume that a standard number and a specification version mean the same thing.
Keep tested criteria separate from product features
A WaterSense result speaks to the applicable family’s test criteria. It does not establish that every model with that label suits your irrigation system or that it will behave identically on a particular property. Keep other spec-sheet details in separate columns so they do not look like certified results.
| Spec-sheet detail | What to record | What it tells you |
|---|---|---|
| Zones or stations | Count available now and any stated expansion limit | Whether the model fits the system’s zone needs |
| Sensor inputs | Rain, freeze, and flow inputs; note included versus optional | Which sensors the controller can use, according to its documentation |
| Network or app dependency | Stated behavior when the network is unavailable | What the manufacturer says about offline operation |
| Flow handling | Whether it reads flow and what action it states for high flow | A documented feature, not proof of a WaterSense test result |
| Enclosure and temperature | Outdoor rating and stated temperature range | Installation and operating details to verify for the site |
Use the same model configuration for each column. A product that supports a flow sensor is not necessarily sold with one, and a broad compatibility statement is not the same as a tested performance claim. Mark an absent detail as not stated rather than filling the gap with an assumption.
Build a comparison you can explain
A useful side-by-side record has two sections. In the first, compare the WaterSense family, exact label status, applicable standard, and criteria named for that path. In the second, compare the product’s stated zones, inputs, offline behavior, flow handling, and enclosure details. This prevents a long feature list from outweighing the more specific question of what the label covers.
Treat the two paths’ annual-savings estimates, if shown on a sheet or in supporting material, as estimates—not as a direct S627-versus-S633 score or a prediction for your property. For a performance claim with no clear test reference, use these questions about third-party testing to frame a follow-up. After installation, home irrigation checks can help you assess how the system actually operates.
