Irrigation Controller with a Soil Moisture Sensor: Better Than a Timer?

Your vegetable bed gets twenty minutes of water every morning at six. In May the soil stays soggy for days afterward; in July the tomatoes still wilt by mid-afternoon. That gap is exactly what an irrigation controller with a soil moisture sensor is built to close: before every cycle, it checks whether the soil around the roots actually needs water. So the short answer to the question in the title is yes, whenever your plants’ water demand shifts from week to week and you don’t want to keep adjusting a schedule by hand.

Better does not automatically mean cheaper to run or safer, though. A sensor only measures the spot where it sits, and a radio link can drop out. A well-planned automatic watering system therefore combines both ideas: a fixed time window as the frame and the sensor reading as the permission to water. Below you’ll see how that works with a Milesight UC511 as the valve controller and a Milesight EM500-SMTC as the soil sensor, which thresholds make sense, and where the honest limits are.

How does an automatic irrigation controller work?

Every automatic irrigation controller setup has three parts: a valve that opens and closes the water path, a controller that switches the valve, and logic that decides when to switch. With a classic hose-bib irrigation timer, all three live in one housing and the logic is simply a clock. In a networked setup the parts are separate and talk to each other over radio.

The Milesight UC511 is that kind of networked controller. It has two outputs for two-wire 12 V DC latching solenoid valves. A latching valve receives a short pulse to open and a reverse-polarity pulse to close, and it holds its position without power in between. That is why the controller can run on its built-in solar panel and two rechargeable batteries, with no mains cable in the yard. According to the manufacturer, it stores up to 16 schedule events and can control watering by time or by soil moisture.

The logic can live in two places. You can store schedules and rules on the controller itself, in which case they keep running without a network connection. Or a platform behind a LoRaWAN network evaluates the sensor data and sends commands to the valve. In practice a mix works best: safety limits such as the maximum run time belong on the controller, while convenience features such as charts and notifications can live on the platform.

Timer vs sensor irrigation: when is a fixed schedule enough?

Honestly, a fixed schedule is often good enough. When water demand is steady, a sensor adds little. Typical examples are new plantings that need water every day for their first few weeks, containers and planters with little soil volume, and greenhouse beds whose conditions barely change over the summer. In those cases a simple irrigation timer delivers water reliably, and there is no reading that can be misinterpreted.

Things get harder once evaporation changes noticeably. A run time that is just enough in midsummer is usually too much in spring or fall. Water then lingers in the soil, roots get less oxygen and nutrients wash out. The opposite happens too: a zone set on the lean side dries out during the first heat wave, before you get around to changing the schedule. If you rely on a fixed schedule, you have to revisit it several times per season.

The most common mistake is setting the run time once in spring and then forgetting about it. A close second is giving several zones with different sun exposure the same duration because it’s easier. If you want watering to run on its own without constant fine-tuning, that is exactly where a soil sensor earns its place.

How does a soil moisture irrigation controller decide when to water?

The sensor should not open and close the valve directly. A more robust approach is permission-based: the schedule defines a watering window, say between 5 and 7 a.m. At the start of the window, the logic looks at the latest valid reading. If it is below the start threshold, the zone runs one limited cycle of fixed length. If it is above, the cycle is skipped. The sensor becomes a gatekeeper rather than a switch.

The reason is lag. Water takes time to soak down from the surface to the probe, anywhere from half an hour to several hours depending on soil and depth. If the controller kept the valve open until the reading rose, far too much water would already be on the ground by then. So the rule is short, fixed cycles, then a soak period, then a fresh decision.

The Milesight EM500-SMTC measures soil moisture, soil temperature and electrical conductivity with a probe whose pins are 50 mm (about 2 inches) long. The manufacturer specifies moisture accuracy of ±2 percentage points up to 50 percent and ±3 points above that. The radio unit sits on a 2-meter cable and, according to the datasheet, runs for up to ten years on a large lithium battery at a ten-minute reporting interval. Milesight explicitly describes the pairing with the UC511: when the sensor reports dry soil, the controller starts the stored irrigation plan.

What soil moisture level should trigger irrigation?

There is no universal number, because your soil sets the scale. Sensors of this type report water content as a share of soil volume. Two reference points matter: field capacity, the level the soil holds after a thorough soaking and draining, and the wilting point, below which plants can no longer pull water out. The range in between is plant-available water. A well-established rule of thumb is to water once roughly half of that reserve has been used.

The table below gives rough reference values for three soil types. It compares how far apart field capacity and wilting point sit, and where a sensible start threshold falls as a result.

The striking part is how narrow the buffer is in sandy soil. A few points of drift are enough to go from “well watered” to “dry,” so sand needs shorter, more frequent cycles. Clay holds far more water but releases it to the roots more slowly. A reading of 25 percent means soaked in sand and already stressed in clay.

So don’t rely on the table alone. It’s better to measure your own soil: water the zone thoroughly, wait one to two days and note the reading. That is your practical field capacity at that spot. Set the start threshold a few points below it and watch whether the plants still look fresh at that level. Also add a spacing rule: after a cycle, the zone only starts again at the next scheduled window. That keeps small fluctuations around the threshold from toggling the valve on and off.

How many valves and zones does your irrigation controller need?

A zone is an area watered together through one valve. A zone only makes sense if the area shares similar conditions: the same soil, similar sun, similar plants and the same type of emitters. A lawn in full sun and a shady perennial bed don’t belong on the same valve, even if the pipe happens to run past both.

The UC511 switches two valves, so two zones per controller. For more zones you add more controllers, which can be managed together over LoRaWAN; Milesight also supports multicast to push settings to a group of devices at once. Plan the cable runs as well: the valve cables are 1.5 meters long by default, so the controller needs to sit close to the valve box.

For sensors the rule is simple: every sensor-controlled zone needs its own measuring point. A sensor that has to decide for two different zones gives the wrong answer for at least one of them. Place the probe where the roots actually take up water, typically about 4 to 8 inches deep in beds and shallower under turf. Keep it away from directly under an emitter, where it reads wet while the rest of the zone is dry, and away from the edge, where soil dries faster. Make sure it has firm soil contact with no air gaps; poor contact is one of the most common causes of implausible readings.

What happens when the irrigation moisture sensor stops reporting?

This is the most important question for any wireless irrigation setup, and it usually gets asked only after it has happened. A sensor can go quiet for many reasons: a dead battery, a newly planted shrub that blocks the signal, a gateway outage or a cable nicked by the mower. To the controller, all of these look the same: no new reading arrives.

The ground rule is that missing data is not proof of dry soil. Define a maximum data age. If the sensor reports every ten minutes, you might treat any reading older than three intervals as invalid. For that case you need a deliberate fallback. Either the zone keeps running on a shortened fixed schedule, which is often the safer choice for sensitive plants, or it pauses and you get an alert. Both are reasonable, as long as you decided in advance.

The hardware helps here. According to the manufacturer, the EM500-SMTC stores up to 1,000 records and can resend them after a radio gap, so holes in the history get filled. The UC511 executes stored commands on its own even without a network connection. What matters most is the maximum run time per cycle, set directly on the controller: if a close command from the platform never arrives, the controller still ends the cycle. Because a latching valve stays where it is without a pulse, the system should also have an easy-to-reach manual shutoff so you can step in if something goes wrong.

Can a smart irrigation controller work without Wi-Fi?

Yes, and for gardens, fields or landscaped grounds it’s often the more practical route. Home Wi-Fi rarely reaches the far end of a large property, and a Wi-Fi device needs far more power than a LoRaWAN sensor. LoRaWAN sends small amounts of data over long distances on very little energy. Milesight lists a range of up to 2 km (about 1.2 miles) in urban areas and up to 15 km (about 9 miles) in rural areas for both devices; those are best-case figures, and buildings and vegetation shorten them noticeably.

For standard LoRaWAN irrigation you need a LoRaWAN gateway within range and a network server that manages the sensor and controller. The gateway can sit indoors with an Ethernet or cellular uplink, and the devices out in the yard never touch Wi-Fi. Both devices are configured over NFC with Milesight’s smartphone app; you just hold the phone against the housing.

There is a second option: Milesight D2D. It lets the EM500-SMTC talk directly to the UC511 with no gateway at all, with a response time under one second according to the manufacturer. The catch is that the UC511 has to listen continuously in LoRaWAN Class C. Per the datasheet, it lasts only about 26 days in that mode on full batteries without recharging, versus several years in Class A. The solar panel tops it up, but in a shady mounting spot that may not be enough. For a small, remote plot without a gateway, D2D is still a real option, provided the controller gets enough sun.

How do you test a sensor-based irrigation system?

Test the mechanics first. Trigger each output manually and check that the right valve opens and also closes again. With latching valves, polarity determines open and close; if the wires are swapped, the valve does the opposite of what the controller reports. You’ll only notice if you look at the valve or the emitters themselves.

Next, run the automation in observation mode for one to two weeks: the schedule waters as before, and the sensor rule is only logged. That shows you how quickly the reading rises after a cycle, how long it takes to fall back to the start threshold and whether the planned permission logic fits the plants. Only then do you switch the sensor gate on for real.

After that, test the failure case on purpose. Switch the sensor off temporarily and check that, once the allowed data age has passed, the zone falls back to the behavior you defined and the alert actually arrives. Also simulate a missing close command by setting a short maximum run time and watching whether the controller ends the cycle on its own. Log every maintenance step, such as moving the probe, in the history. Otherwise a sudden jump in the reading will later look like a real change in the soil.

Where can you buy a LoRaWAN irrigation controller?

Before you choose, check the points that decide between a system that just works and one that causes headaches. First, the valves: the controller has to match the valve type and voltage. The UC511 is designed for two-wire 12 V DC latching solenoid valves, not for continuously powered AC valves. Second, the zones: count how many areas have genuinely different conditions, and plan on two valves per controller plus one sensor per sensor-controlled zone.

Third, connectivity: find out whether a LoRaWAN gateway covers the yard, or whether a small plot calls for direct D2D operation with its higher power draw. Fourth, the fallback: choose devices that run schedules and limits locally, so a radio outage neither dries out the zone nor leaves a valve open. Fifth, the sensor: it should measure water content in the root zone and buffer enough data to fill gaps after an outage.

If you’re putting together an irrigation controller with a soil moisture sensor, you’ll find the controllers in our valve controllers category.