monitorMyLawn
Sign up

Features

Eight channels in. Eight decisions out.

One stake measures eight things. Everything else on the dashboard — the score, the run time, the forecast, the leak alert — is computed from those eight and nothing else. There is no second sensor to buy and no reading that comes from a weather station nine miles away.

Start monitoring Go deeper on the eight tools

$4.99 / device / monthEvery feature at both tiers Cancel any monthNo proprietary hub

FIG.01

What it measures

Eight channels, every uplink, from one stake.

Here is one ordinary summer day on all eight at once, including the thunderstorm that arrived at four in the afternoon. Watch how many channels notice it — and which two do not care in the slightest.

One device · 24 hours · all eight channels, shared clock
  • Water in the soil
  • Water in the air
  • Air temperature
  • Soil warmth & light
  • Housekeeping
Twenty-four hours of all eight sensor channels, stacked on one clock. Eight stacked traces share a midnight-to-midnight axis. Soil moisture dries steadily from 27.4 percent, then jumps to just under 32 when 15.7 millimetres of rain falls between 4 and 5 pm, and begins draining again. Soil temperature swings only about nine degrees Fahrenheit and peaks around 6 pm, roughly four hours after the air temperature peaks at 84 degrees around 3 pm. Humidity mirrors air temperature and spikes to 89 percent in the storm. Light rises from zero at 6 am to about 74,000 lux at solar noon, is cut sharply by the storm cloud, and returns to zero by 8:30 pm. Rainfall is flat at zero all day except the single afternoon burst. Battery voltage and signal strength are effectively flat: neither notices the storm at all. 00:00 03:00 06:00 09:00 12:00 15:00 18:00 21:00 4:00 PM — 0.62 in OF RAIN measured on this lawn, not forecast for the county AT MIDNIGHT Soil moisture %VWC 29.5% Soil temperature °F 67.7°F Air temperature °F 59.0°F Air humidity %RH 86% Light lux 0 lux Rainfall mm zero for sixteen hours, then all of it in one 15.7 mm Battery V 3.99 V Signal dBm -71 dBm
Battery and signal are the two that ignore the storm entirely — they are housekeeping, not agronomy. Soil temperature swings about nine degrees where the air swings nearly thirty, and it peaks at seven in the evening, four hours after the air did. That lag is exactly why a calendar is the wrong instrument for deciding when to seed.

Scroll the chart sideways

What each channel is actually for

Stored canonical — degrees Celsius, millimetres — and converted on the way out to whatever units you picked. Both forms are available on export.

The eight channels, as stored
ChannelKey Valid rangeWhat reads it
Soil moisture soil_moisture 0 to 100 %VWC Watering advisor · dry-down · health · leak scan · infiltration
Soil temperature soil_temperature -40 to 85 °C Mow, fertilize and seed readiness
Air temperature air_temperature -40 to 85 °C ET₀ (Tmax, Tmin, Tmean) · heat and frost alerts · health
Air humidity air_humidity 0 to 100 %RH Evaporative context
Light light 0 to 200,000 lux Health score, light sub-term
Rainfall rain 0 to 500 mm Cancels watering · suppresses false leak alerts
Battery voltage battery_voltage 0 to 6 V Low-battery alert · days-to-flat projection
Signal strength signal_strength -150 to 0 dBm Health score, freshness sub-term

Scroll the table sideways

Everything else is derived

The Lawn Health Score, the run time, the dry-down forecast, the leak finding — none of them is a ninth measurement. They are all arithmetic on the eight above, which is why the input list for every tool is published rather than described as proprietary.

Fig. 01 — A representative day, drawn from the model each tool actually uses; your own day will not look like this one. A reading arriving out of order or outside the ranges in the table is rejected at ingest rather than smoothed into the chart.

FIG.02

What it computes

Eight tools, in four jobs.

Grouped by what you are trying to do, not by what was easy to build. All eight are included at both price tiers — there is no plan where the agronomy is held back and no add-on to buy later.

Decide

When to water, and for how long. These two are the reason the product exists.

  1. 01

    Smart Watering Advisor

    A schedule is a guess you made in April. This computes today's actual demand, subtracts the rain that actually fell on your lawn, and either gives you a run time or tells you to stand down.

    ReadsFAO-56 Hargreaves ET₀ from your latitude and the day of year · a grass crop coefficient · your own rain gauge over the last 24 h · where your soil sits in its band Gives youwater or hold, a pre-dawn start time, and the minutes

  2. 02

    Dry-down Forecast

    Knowing you need water tonight is useful. Knowing you have until Thursday is what lets you plan around it — and it is the difference between watering before the stress and after it.

    Readsthe falling moisture segment since your last peak, regressed · the refill point for your soil type Gives youhours until the refill point, the daily dry-down rate, and the r² of the fit

Verify

Whether the water you applied did anything. Almost nothing in irrigation is measured after the valve closes.

  1. 03

    Infiltration Efficiency

    A controller reports a completed cycle whether the water soaked in or ran down the driveway. This measures the moisture the root zone actually gained per inch applied.

    Readsmoisture immediately before and after each logged cycle · the depth applied Gives you%VWC gained per inch, per cycle, and whether that is trending down

  2. 04

    Water Savings

    Arithmetic on your own numbers rather than a promise on ours — including the fact that it is floored at zero when you were already thriftier than the baseline.

    Readslogged cycles and their applied depth · your zone area · the rate off your own water bill Gives yougallons and dollars against a set-and-forget baseline, week by week

Diagnose

What is wrong, and what has physically broken. Both run continuously, without you asking.

  1. 05

    Lawn Health Score

    One number is a poor instrument, so the number is not the point. The point is the limiting factor printed next to it: the one weighted input dragging the score down, so you fix that instead of guessing.

    Readsmoisture in band (35%) · moisture stability (15%) · heat and cold stress (20%) · light (15%) · data freshness and signal (15%) Gives you0 to 100, five sub-scores, and the name of the limiting factor

  2. 06

    Anomaly & leak detection

    Moisture climbing when no rain fell and no cycle ran is a stuck valve or a burst line. It also catches probes frozen on one value, gaps in the uplink, dying batteries and physically implausible readings.

    Readsthe moisture slope · rainfall summed across the whole window · reading cadence · battery voltage · air-temperature z-scores Gives youopen findings, each with the evidence that raised it

Time the rest

The jobs that are not watering, and the zones that are not this one.

  1. 07

    Mow, fertilize & seed readiness

    Growth is driven by soil temperature and water, not by the month. Seed sown into soil that is four degrees too cold does not come up, whatever the bag says.

    Readsmean soil temperature at root depth · mean air temperature · current moisture band · recent rain total Gives youa 0 to 100 readiness for each of the three jobs, and the reason for each

  2. 08

    Multi-device Compare

    Averaging two zones hides the exact problem you bought the sensor to find. This puts them side by side, aligned, and ranks them.

    Readsany two or more sensors on the account, or one sensor across two periods Gives youaligned curves, a health ranking, and the gap between them

What each one needs, and where each one fails

Fig. 02 — The eight tools and the job each belongs to. Every “reads” line above is the tool’s full input list rather than a summary of it; the thresholds those inputs are measured against, and the minimum history each tool needs before it will answer at all, are printed in full on the tools page.

FIG.03

How it tells you

An alert worth having is one that knows how to shut up.

The failure mode of every threshold alert ever built is a reading that sits on the line and flaps. Ours raises at one number and clears at a different, higher one — so the same dry afternoon produces one notification, not six.

Low soil moisture · 36 hours · raise at 15%, clear at 20% Root-zone moisture Raise line Clear line
How hysteresis stops a threshold alert from flapping. Root-zone moisture falls through the 15 percent raise line at about hour 9, which sends one alert. It then wobbles either side of 15 percent for roughly twelve hours — six crossings that a single-threshold system would have emailed about individually. Because the alert only clears once moisture is back above a separate 20 percent line, none of those crossings sends anything. Watering at hour 26 lifts moisture through 15 and then through 20, at which point the alert resolves. Two messages in total. 10% 15% 20% 25% RAISE AT 15% CLEAR AT 20% six crossings of the 15% line — zero extra emails 1 — RAISED one email, one dashboard card 2 — RESOLVED only once it is properly back in band you water here
On top of the two thresholds there is a cooldown — 60 minutes by default — before the same alert type can raise again on the same sensor, and any rule you write yourself can require the condition to hold for a duration you set. That duration is checked against your actual reading history, not merely displayed.

The four rules you get without configuring anything

Built-in alert rules
RuleRaises when Clears whenSeverity
Low soil moisture
soil_moisture		 below 15% back above 20% Warning
Low sensor battery
battery_voltage		 below 3.3 V back above 3.5 V Warning
Frost risk
air_temperature		 at or below 0°C back above 2°C Critical
Heat stress
air_temperature		 above 32.2°C back below 29.5°C Warning
Sensor offline Nothing has arrived for three hours. A reading buffered on the device and delivered late is accepted and will not rewind your last-seen time.

Scroll the table sideways

  • Rules you write Any metric, above or below a number you choose, with a severity and an optional sustained-for duration — so one odd reading never triggers anything.
  • Smart rules Leak detection and sensor-fault detection are rule types rather than thresholds: they watch a shape in the data instead of a single value.
  • Where they land The dashboard and email. You choose which categories may email you, per account.
  • Quiet hours Nothing wakes you at three in the morning unless you have said it may.
  • Weekly digest Optional, on whichever day of the week you pick, instead of a stream of individual messages.
  • Per device or account-wide Write a rule once for everything, or tighten it for the one zone that behaves differently.

Fig. 03 — Hysteresis on the built-in low-moisture rule. The raise and clear numbers above are the ones the alert engine enforces, not illustrative ones.

FIG.04

Getting your data out

A door marked exit, and no lock on it.

Export is not a retention lever here. Every reading is downloadable from the first one onward, in the units you read or the raw canonical ones, and a sensor that has stopped being paid for keeps its history exportable.

How long a reading lives

Nothing in the system grows without a bound, and nothing useful is thrown away either. Full-resolution samples are the expensive ones, so they age into averages rather than into deletion. Year-on-year comparison still works a decade in.

  • Every sample90 days
  • Hourly averages13 months
  • Daily averagesindefinitely
  • CSV per downloadup to 2 years · 400,000 rows
  • CSV unitsyour display units, or raw canonical
  • Account exportJSON · devices, alerts, settings
EVERY SAMPLE 0 – 90 days full resolution HOURLY AVERAGES 90 days – 13 months ~24 rows a day DAILY AVERAGES 13 months – forever 1 row a day WIDTH IS ROWS STORED, NOT TIME
  • Share without sharing yourself Each sensor can mint a read-only public report link that carries no personal information — send it to a landscaper, a groundskeeper or an HOA. Revoke it instantly and the link is dead.
  • Stop paying, keep the history An unpaid sensor stops being able to send new readings. Everything it already sent stays visible and stays exportable. Nothing is deleted because an invoice failed.
  • Nobody is watching you No third-party analytics, no advertising pixels, no cross-site trackers. The only cookie is the one that keeps you signed in, and deleting your account is a real deletion.

Fig. 04 — Retention tiers. Bar width is roughly the number of rows kept, which is why the daily tier can run forever and the full-resolution tier cannot.

FIG.05

More than one lawn

Two zones averaged is one zone you cannot see.

The shady strip that stays damp for days and the sunny corner by the driveway are not one lawn with one answer. Put a stake in each and the difference stops being an argument.

Two zones · same account · same week · same weather Front — full sun Back — shaded The average of the two
Two zones diverging over one week, and why their average is misleading. The front lawn in full sun dries from 30 percent to about 16 percent over seven days, crossing the 22 percent refill point on day four. The shaded back lawn barely moves, drifting from 31 to 28 percent. The average of the two never crosses the refill line at all, so a single sensor reporting the mean would never have told you the front lawn was in trouble. REFILL POINT 22% — LOAM 16% 22% 28% 34% DAY 1 DAY 2 DAY 3 DAY 4 DAY 5 DAY 6 DAY 7 FRONT 16.1% BACK 28.1% AVERAGE 22.1% never crosses the line FRONT NEEDS WATER, DAY 4
Comparing across zones is also where soil type earns its keep: sand is in band between 12 and 28 per cent, loam between 22 and 38, clay between 28 and 45. Two zones can read the same number and only one of them be thirsty, which is why the score compares against each zone's own band.
  • One per behaviour One sprinkler zone, one sensor. A front and back on separate zones want one each. A shady strip that stays damp for days wants its own.
  • Billed per sensor One account, one subscription, whose quantity simply tracks how many sensors are active. Add one and it goes up; deactivate one and it drops on the next invoice.
  • Mixed fleets are fine Connection type is chosen per device. Wi-Fi at the house and LoRaWAN at the far paddock, on the same account and the same dashboard.

Fig. 05 — A modelled divergence between a sunny and a shaded zone. The point is not the exact rates, which are yours to discover; it is that their mean is a number describing neither lawn.

Put one in the ground

Every feature, at both prices.

There is no tier where the agronomy is held back, no add-on for the leak detector, and no per-export fee. $4.99 per device per month or $49 a year, and the hardware is a separate one-time purchase.

Start monitoring See how it gets installed
  • Named methodsFAO-56 Hargreaves ET₀ with a grass crop coefficient. Published so an agronomist can check our work.
  • Published limitsEvery tool's inputs and every alert's thresholds are on this site, including the ones that are unflattering.
  • Three radios, no hubWi-Fi over signed HTTPS, MQTT to your own broker, or LoRaWAN. Chosen per device, changeable later.
  • Your data, portableCSV and JSON from the first reading, and a revocable read-only link for whoever mows it.