Automated irrigation in horticulture becomes useful only when measurements describe what is truly happening in the root zone and microclimate. In greenhouse or tunnel tomatoes, alternating dry–wet root conditions and unstable EC quickly show up as stress, weak uptake and variable fruit quality. That is why the first priority is not “how many irrigations,” but proving that sensors read correctly and comparably.
Precise monitoring does not mean watching a single value. Moisture without EC and pH can hide the real cause: you may have enough water volume while salinity rises, or pH drifts into a range that limits nutrient availability. Likewise, climate data without VPD can lead to wrong ventilation decisions: high night humidity, condensation and weak air exchange increase foliar disease pressure.
This article explains the technical fundamentals and a commissioning workflow: what each sensor actually measures, where to place it, how to calibrate it, and how to validate it in the first weeks. The examples are hypothetical and are meant to help you build farm-specific thresholds and routines—without “universal recipes.”
1) Understand the mechanism: what you are really controlling in tomato irrigation
In drip-irrigated, fertigated tomatoes, “irrigation” simultaneously controls water availability, oxygen in the root zone, and the movement/accumulation of salts. In substrate systems, the small volume amplifies mistakes: infrequent pulses can concentrate the solution and raise osmotic stress, while long irrigations can reduce aeration and lead to weak roots. In soil, inertia is higher, but uneven sector performance becomes critical.
What to observe: growth rhythm, turgor, uniformity of fruit set and sizing, and any recurring stress patterns that correlate with irrigation timing. What to verify independently: actual line flow and sector uniformity, leaks, and clogging—plus spot checks with separate tools (for example, pH/EC measured in the fertigation solution). Practical decision: define irrigation as a control process, not a calendar. Result check: aim for repeatable daily curves, not a single “good” reading.
2) Choose sensors correctly: measurement, medium, and units matter
In automation, measurement confusion becomes wrong automation. A temperature sensor does not measure EC or pH; those require dedicated probes. For EC, you must state the medium: EC of source water, EC of fertigation solution, EC from a substrate extract, and bulk-soil EC are different measurements and should not be compared directly. EC indicates total dissolved salts, not the concentration of individual nutrients.
What to observe: whether EC “jumps” at every irrigation or stays stuck, whether pH drifts slowly over time, and whether moisture swings are large. What to verify independently: periodic laboratory water analysis (pH, alkalinity, soluble salts) and on-site checks with a reference meter; on-site monitoring complements, not replaces, lab analysis. Practical decision: decide upfront which EC you are tracking and by what method. Result check: label records clearly (water, solution, extract) and confirm they remain internally consistent.
3) Place sensors by zones: three good points beat ten wrong ones
In greenhouses and tunnels, microclimate and irrigation are not uniform. A practical protocol is to manage the crop by zones: one point near a representative row, one in a hot/dry area, and one in a cool/wet area. For soil/substrate moisture, avoid placing every probe beside the same dripper pattern: right next to an emitter you will see sharp moisture peaks that do not represent the root-explored volume.
What to observe: differences at row ends, near doors, close to walls, under vents, or on long lines where pressure drops. What to verify independently: a manual check of wetting (for example, inspecting the soil profile or—on substrate—observing drainage behavior) and pressure/flow checks by sector. Practical decision: use placement for diagnosis rather than “averaging.” Result check: after changes (irrigation timing, segmentation), zone differences should shrink or become explainable.
4) Commission sensors: calibration, stabilization, and data freshness
Commissioning starts with data integrity: reporting interval, correct units, consistent timestamps, battery/status visibility, and no “frozen” values. Then comes calibration where needed: pH probes require routine calibration and maintenance, and some moisture probes need substrate/soil-specific corrections. Accept that “installed” does not mean “valid”—the first days are for stabilization, comparison, and troubleshooting before any automation relies on the numbers.
What to observe: delays, missing data, impossible jumps (for example, moisture increasing without irrigation/rain), or pH that never changes. What to verify independently: spot comparisons using a manual measurement in the same place and with the same method, plus physical inspection of installation (proper contact with the medium, cable protection, correct insertion depth). Practical decision: keep automation disabled until you have a few days of clean baseline data. Result check: after calibration/adjustment, sensor trends should clearly match real events (irrigation, ventilation changes).
5) Build the automated irrigation workflow: events, not only thresholds
Robust automation is built around verifiable events: irrigation start/stop, drainage where applicable, recipe changes, intense ventilation periods, and days with different radiation/temperature demand. Instead of triggering irrigation solely because “moisture is below X,” build a logic where sensors confirm that irrigation produced the expected response, and that the root zone returns to a stable regime without large oscillations that shock uptake.
What to observe: after irrigation, moisture rises and then declines gradually; a very fast decline can signal insufficient volume or high evapotranspiration demand, while a prolonged “high” can indicate excess water and limited aeration. What to verify independently: that irrigation truly starts when you think it does (valves, pressure) and that flows remain stable. Practical decision: adjust duration/frequency by zone rather than globally. Result check: compare similar days and look for reduced day-to-day variability in response curves.
6) Link irrigation to climate: use VPD as an indicator, but check leaf–air differences
VPD calculated from air temperature and relative humidity is a useful estimate of evaporative demand, but leaf temperature can differ from air temperature—especially under strong light or weak air movement. In tomatoes, imbalance between VPD, irrigation, and ventilation can create “unbalanced” plants: either limited transpiration and poor uptake, or excessive transpiration and water stress. At night, high humidity and condensation raise foliar disease risk.
What to observe: nights with sustained high humidity, condensation periods, vent opening patterns, and zone differences (cold/wet corners). What to verify independently: visible condensation, air movement, and local temperature variation; if possible, take spot leaf-temperature checks with an IR thermometer to understand deviations. Practical decision: use VPD to synchronize irrigation and ventilation, avoiding late irrigations that prolong high humidity. Result check: fewer condensation windows and a more uniform daily water-use pattern.
7) EC and pH in fertigation: validate at three points and avoid wrong conclusions
Useful fertigation control separates three things: source water, the solution in the tank/mixing line, and what actually reaches the root zone (using an explicit method, such as a substrate extract). pH is affected by alkalinity and substrate/soil reactions; EC is affected by concentration and accumulation. Neither pH nor EC alone identifies which nutrient is missing—EC is not a nutrient profile—but both can reveal conditions that restrict uptake or push salinity stress.
What to observe: EC creeping upward over days even though irrigation volume seems adequate, or pH shifting after a change in water source. What to verify independently: water analysis that includes alkalinity and spot checks with a reference probe under the same sampling conditions; remember that EC in fertigation solution is not the same measurement as EC in a substrate extract. Practical decision: adjust the recipe only after confirming the method and the measurement point. Result check: track trend stability for several days, not a reaction to a single reading.
8) Failure tests and operating routine: clogging, sensor drift, missing data
An automated system must be commissioned for faults as well as for normal operation. Clogged drippers, a valve not opening fully, or a low-pressure zone often appear as a sector that does not “respond” to irrigation: moisture does not rise after an event, or rises far less than in other zones. Separately, sensor drift (especially with pH) or imperfect installation can produce believable but wrong values that push you into unnecessary changes.
What to observe: persistent zone gaps, flat lines (unchanged values), spikes unrelated to events, or data gaps. What to verify independently: physical inspection (filters, line ends, pressure), a manual measurement right beside the probe, and checks of probe condition and maintenance history. Practical decision: define a weekly routine for data audit and a routine for interventions (filter cleaning, emitter replacement, pH recalibration). Result check: after intervention, the irrigation “event response” returns and zone differences reflect microclimate, not defects.
Conclusion
Automated irrigation and precise monitoring in horticulture are, fundamentally, a measurement protocol: choose the correct medium (water, solution, extract), confirm units and data freshness, place sensors by zones, and validate every conclusion with an independent check. In tomatoes, the balance among water, EC, pH, root-zone temperature, VPD, and ventilation is built through stable trends—not by reacting to isolated readings.
A hypothetical rollout can start simple: three soil/substrate points, one climate point, plus weekly checks of the fertigation solution, and automation enabled only after the “event response” becomes predictable. If you use GrowGuard to follow zone-based sensors and alerts, treat it as a control and documentation tool; for a farm-specific workflow, a short configuration discussion with your technical team or an integrator is a practical next step.