PhloMetricData Matters
One Node. One month of readings. A single irrigation controller, quietly metered minute by minute. What that data showed was not just confirmation of a schedule anyone could have read off the controller. It was a discovery: watering cycles nobody planned, roughly 2,400 extra gallons a week, entirely invisible inside a monthly utility bill.
This is a real analysis of Node 1's meter, collected by the PhloMetric system across the first eight nights of July 2026. It shows both sides of what continuous metering buys you: a stable baseline that proves the equipment is healthy, and the sensitivity to catch the thing you were not looking for.
The known schedule
Node 1 meters an irrigation controller running a six-valve program that starts at 11:00 PM. The valve cadence is fixed: 15, 15, 15, 10, 10, 15 minutes for V1 through V6, which is 15/15/15/10/10/15 = 80 minutes end to end. Nothing exotic; a controller anyone could program.
What the per-minute data adds is proof that the program actually runs the way it is written, night after night, without drift. It is metronomic. Every watering night the cycle starts at 22:57, ends at 00:17, runs a contiguous 80 minutes, and lands somewhere between 2,302 and 2,332 gallons. That is a spread of just 30 gallons, about 1.3%, across 7/1, 7/4, 7/6, and 7/8.
A controller can tell you what it was told to do. Only a meter can tell you what actually flowed through the pipe. Here they agree to within a rounding error, which is exactly what you want to see.
Per-valve fingerprints
From the flow data alone, each valve has a stable signature: a characteristic volume and an average flow rate. Because the program is so steady, those signatures become a fingerprint you can compare night over night. Below is 7/6 against 7/8, valve by valve, for the 23:00 program.
| Valve | Min | 7/6 gal | 7/8 gal | Δ gal | Δ % | 7/6 gpm | 7/8 gpm |
|---|---|---|---|---|---|---|---|
| V1 | 15 | 446 | 460 | +13 | +3.0% | 29.7 | 30.6 |
| V2 | 15 | 382 | 387 | +6 | +1.5% | 25.4 | 25.8 |
| V3 | 15 | 317 | 320 | +3 | +1.0% | 21.1 | 21.4 |
| V4 | 10 | 319 | 321 | +2 | +0.7% | 31.9 | 32.1 |
| V5 | 10 | 364 | 366 | +1 | +0.3% | 36.4 | 36.5 |
| V6 | 15 | 472 | 478 | +6 | +1.2% | 31.4 | 31.8 |
| TOTAL | 80 | 2302 | 2331 | +29 | +1.3% |
Every valve lands within 0.3 to 3.0% night to night (+1.3% overall), well inside the normal noise of pulse timing and line pressure. The per-valve shape is unchanged: V5 is the biggest drinker at roughly 36 gpm, V3 the smallest at roughly 21 gpm, exactly as the night before.
That stability is the health-monitoring value. No valve shows the drop you would expect from a clog or a partial close. None shows the jump you would expect from a broken head or a stuck-open valve. A changed fingerprint, a zone that suddenly runs 40% higher or a third of its usual volume, is an early warning you would otherwise get only when someone noticed a soggy lawn or a spiked bill weeks later.
The discovery: volunteer irrigation events
The valves were the reassuring part. The data also surfaced something nobody scheduled. Pulling a multi-night range and grouping each night into cycles (dropping the zero-gallon idle blocks) produced this log for the eight nights:
| Night | Cycles | Earlier cycle | 23:00 program | Total |
|---|---|---|---|---|
| Wed 7/1 | 2 | 22:00 to 22:38, 38m, 801g | 22:57 to 00:17, 80m, 2332g | 3133g |
| Thu 7/2 | 0 | no watering | none | 0 |
| Fri 7/3 | 0 | off night | off night | 0 |
| Sat 7/4 | 1 | none | 22:57 to 00:17, 80m, 2330g | 2330g |
| Sun 7/5 | 0 | off night | off night | 0 |
| Mon 7/6 | 1 | none | 22:57 to 00:17, 80m, 2302g | 2302g |
| Tue 7/7 | 0 | off night | off night | 0 |
| Wed 7/8 | 2 | 21:27 to 22:37, 69m, 1613g | 22:57 to 00:17, 80m, 2331g | 3944g |
The 23:00 program is the same rock-steady 80-minute run every watering night. The earlier cycles are the story: they are the two copper bars in the chart at the top of this page. They are recurring but irregular: 7/1 started at 22:00 and ran 38 minutes for 801 gallons; 7/8 started at 21:27 and ran 69 minutes for 1,613 gallons. Different start times, different durations, and roughly double the volume the second time. That variability is the exact opposite of the metronomic scheduled program, which is what makes them stand out.
On 7/8 the early run also carried its own tells. It terminated abruptly, with V6 getting only about 5 of its usual 15 minutes, and its later valves ran at noticeably lower pressure: roughly 21 gpm on V4 and V5, versus roughly 32 and 36 gpm for those same valves in the 23:00 cycle. That is consistent with a hand-started run, and possibly with a supply or pressure interaction when two cycles fire close together on the same line.
The arithmetic is the point. That single early cycle on 7/8 added 1,613 gallons. Node 1 used 3,944 gallons that night against 2,302 on a normal night: about +71% in one evening, from one unscheduled run.
We call these volunteer irrigation events, in the sense of a volunteer plant: nobody planted it, it showed up anyway. The explanations are worth laying out even-handedly. It could be someone manually starting the controller to give a dry patch of greenspace extra water; a forgotten supplemental or soak program still enabled from earlier in the season; or tampering with the controller. The point is not to accuse anyone. The point is that without per-minute metering, roughly 2,400 extra gallons in a single week would sit invisible inside a monthly utility bill, indistinguishable from ordinary use.
Why data matters
The value of continuous metering is not only confirming what you scheduled. It is discovering what you did not. And the two halves reinforce each other: it is precisely because the scheduled program is so stable, 30 gallons of spread across four nights, that the anomalies pop out at all. A steady baseline is what turns an extra 1,613 gallons from noise into a signal.
None of this took special effort. It took one Node quietly metering a controller, a month of readings flowing through the Gateway into the database, and a few straightforward queries. The hardware sat on a wall and did its job; the data did the rest.
If you want that kind of visibility on your own irrigation or utility water, the next step is putting a Node on the meter. See Installation for what a real field deployment looks like.