# A point-in-time review of the garden sensor and pump, followed by the calibration, stopping rules, and verification needed before automatic watering.
A moisture value on a dashboard and a pump button can make automatic watering look finished.
There is still a large gap between that demo and a system that can safely care for a plant.
On July 21, 2026, the live API returned the state of one soil-moisture sensor and one pump.
Automatic watering was disabled, no trigger threshold was configured, and the recorded watering count was zero.
This is a point-in-time record of the running system, not evidence of long-term unattended operation.
Connection details, wiring identifiers, and credentials are not published.
What we verified
The status API reports one soil-moisture sensor and one pump.
There is also a pump-control path, but this review did not verify physical pump operation or water delivery.
The status API exposes the sensor reading, pump state, automation state, watering duration, observation interval, cooldown, and watering count.
The reviewed state was as follows.
Item
State on July 21, 2026
What it means
Sensor
A value was available
The reading path responded
Pump
Reported as off by the API
Physical stopping and absence of water flow were not independently verified
Automation
Disabled
Automatic watering will not run, and no dry-soil threshold is configured
Threshold
Not configured
The dry-soil decision was not calibrated
Watering record
Zero
This record cannot establish operational history
Photo: a grow bed with plants, lights, and wiring. It records the physical arrangement but does not demonstrate pump operation or a history of automatic watering.
This is not necessarily a fault report.
It may be a deliberately safe initial state, but the API response alone does not prove that intent.
A raw sensor value is not a percentage
A soil-moisture probe's raw output changes with the sensor, soil, insertion depth, power, and temperature.
A raw sensor value cannot be interpreted directly as a moisture percentage.
Before choosing a threshold, measure at least two reference conditions in the actual planter.
The dry side: just before the plant would normally be watered.
The wet side: after watering thoroughly and allowing excess water to drain.
Collect a range over several days rather than one sample.
Recalibrate after moving or replacing the probe.
The controller also needs a cooldown and a new reading after watering so it does not chatter around the threshold.
The complete cycle is not “dry means pump.”
It is “validate, water briefly, wait, and measure again.”
Design one safe cycle
Before enabling automatic watering, fix the order of operations.
Read the sensor and reject missing readings or values with implausible sudden jumps.
Compare the result with a calibrated threshold.
If it is dry, run the pump briefly with a hard upper limit.
Stop the pump unconditionally and enter a cooldown.
Wait for water to spread through the soil, then measure again.
If the value does not move, alert instead of adding more water.
The final step prevents a serious class of failures.
With an empty reservoir, detached tube, or displaced sensor, repeated pump runs can damage the floor or the pump before they help the plant.
Software should enforce maximum runtime, daily limits, no rapid repeats, and a manual stop.
The physical setup needs a low-voltage pump supply, backflow protection, a catch tray, and secure tubing.
Before unattended use, observe several complete cycles in person, from dry-soil detection through watering, stopping, and remeasurement.
The two-planter idea is a separate future design
A previous design discussion considered an M5Stack or ESP32-class controller, two moisture sensors, and two pump channels for independent planters.
That plan must not be confused with the live system reviewed here.
The verified live path has one sensor and one pump.
The two-channel version remains a proposal; purchasing, wiring, calibration, and sustained operation have not all been verified.
Two planters dry at different rates.
A two-channel design therefore needs separate sensors, pumps, thresholds, run times, cooldowns, and records for each planter.
Even if both channels share a reservoir, one failure must not consume the other planter's full water budget.
The next verification sequence
The safe next step is not to flip automation on immediately.
• Measure dry and wet references for the actual soil and planter.
• Run the pump manually for a short period, then verify the delivered water volume and that the pump stops.
• Record how the sensor changes after watering.
• Simulate an empty reservoir non-destructively with mocked input or a level sensor, and verify that the system does not add watering cycles.
• Do not intentionally run an unspecified pump dry; keep physical tests supervised with an immediate stop available.
• Run an observation-only mode that alerts without watering.
• Enable short daytime automation windows only after those checks pass.
Plants do not dry at the same rate every day, which is why a sensor can outperform a fixed timer.
But attaching a sensor does not make the system intelligent by itself.
Only a design that measures, stops, and verifies again is ready to look after a planter while nobody is watching.
