Irrigation and Fertigation
Verdify now treats irrigation as an equipment-observed control path, not a hand-entered log. The canonical schedule comes from the active plan and ESP32-observed configuration, while actual runs are reconstructed from relay state: fertilizer relay on, fertilizer master overlap, clean-water flush, and water-meter delta.
The wall drip is one shared path serving south and west. South and west also have separate wall mister fertigation relays, but the schedule is one wall-path schedule, not two independent south_wall and west_wall drip schedules.
Live Schedule
Run Health
The master-overlap card should stay near 100 percent during fertilizer delivery. A flagged run means the equipment-derived view found a missing flush, low fertilizer-master overlap, sparse meter data, or a zero meter delta.
Latest Runs
Daily Accounting
Daily runtime now includes clean drip/mister relays, fertigation relays, and the fertilizer master valve. Water accounting prefers the equipment-derived irrigation meter delta when the run window has enough meter samples.
Relay Trace
This trace shows the physical sequence: fert relay and fertilizer master open together, then the clean relay flushes the line. water_flowing should overlap the wet parts of the sequence.
Root-Zone Feedback
Feedback Gaps
South probe 1 is currently not a trustworthy moisture input and needs physical repair or replacement. Center root-zone and runoff feedback are still instrumentation gaps; until those sensors exist, center fertigation validation depends on relay state, water meter movement, and crop observation rather than closed-loop root-zone response.