Skip to content
← All project notes

HARDWARE + SOFTWARE + GARDEN / FIELD NOTES 03

grgaGrow

In development Cloud app online · Hardware integration next

A small lawn. A closer look beneath the surface.

What started as an idea for watering my 49 m² lawn is becoming grgaGrow — a garden app that brings soil history, weather, light and everyday care into one place. The cloud app is online, with public views and a private owner workspace. Two wired probes and an ESP32 controller will connect it to the soil.

Live: public readings, regional weather and sun/shade · Demo: simulated readings. Live and Demo need no account. Owner sign-in opens your private workspace.

grgaGrow Demo showing two visual soil sensor cards with grass and root illustrations, simulated moisture and temperature readings, and a Visual or Compact switch
THE VISUAL INTERFACE / grgaGrow, 30 October 2026. Demo readings are simulated; grass and roots are illustrative.

01 / SOFTWARE YOU CAN EXPLORE

One garden. Three ways to explore it.

Demo follows the published garden setup with simulated soil readings and example activities. Public Live shows the measurements and garden context the owner chooses to share. Both are read-only and open without an account. The private owner workspace adds settings, longer history, the care diary, alerts and sensor setup.

Switch between Visual sensor cards with grass and roots and a Compact view of the readings in both Demo and public Live. The illustration adds context; it does not measure root growth or indicate soil conditions when readings are unavailable.

HISTORY & WEEKLY REPORTS

A week beneath the surface.

Follow seven days of moisture history and a report of hourly averages, temperature and missing intervals. The private workspace adds up to 30 days of history, metric and sensor filters, and CSV export.

REGIONAL WEATHER

Weather above. Soil below.

Open-Meteo forecasts put air temperature, expected rainfall and precipitation chance beside the soil data. Forecasts use an approximate public location and remain clearly separate from measured soil conditions.

SUN PATH & BUILDING SHADE

Follow the light.

A compact sun path and daylight playback move together with the garden model. Explore sun direction, elevation and estimated building shade. Trees, clouds and surrounding obstacles are not fully represented.

PRIVATE / GARDEN & CARE

A diary beside the graph.

Save garden zones and sensor positions, then log watering, observed rain and completed mowing alongside moisture changes. Scheduled mowing stays separate until completion is recorded. Demo uses fictional events; the owner’s diary stays private.

PRIVATE / ALERTS & HISTORY

From an alert to the evidence.

An alert explains what happened, which probe was involved and when it was detected. Open sensor history takes the owner to the matching chart and highlights that time. The cloud alert log is available; phone push delivery still needs physical confirmation.

PRIVATE / SENSOR SETUP

Ready for the first probes.

A guide records installation checks and an estimated field-capacity reference for each sensor. System status separates controller contact from received readings. Saving a soil reference does not automatically validate calibration or watering thresholds.

React · TypeScript · Vite · Supabase / PostgreSQL · Open-Meteo · SunCalc

02 / THE ENGINEERING BEHIND THE SCREEN

What if a reading never arrives?

A reassuring number is only useful if it can be trusted. The app checks freshness and time quality, preserves gaps in the history, and withholds watering suggestions when readings are unreliable. A dry trend must remain valid for an uninterrupted 30-minute window before the current logic suggests watering.

DEVELOPMENT EXAMPLE / A LOST ACKNOWLEDGEMENT

Send again. Keep one reading.

A measurement can reach the database even when its acknowledgement never reaches the device. The local queue model and ingestion code are tested together: resend that measurement, keep a single database record, then remove only the readings that have been acknowledged.

This verifies the software model locally. ESP32 firmware and real flash power-loss testing still come next.

The cloud workspace uses Supabase authentication and owner-scoped database access. A separate public projection exposes only the selected garden data; exact coordinates, private diary entries, alerts and calibration notes stay outside it. The owner can disable publication. Demo values never become real sensor records, and Live shows waiting for data until physical readings arrive.

Supabase / PostgreSQL · Access rules · Idempotent ingestion · Local automated checks

The app and cloud services are online. Physical ingestion, soil calibration, ESP32 firmware and real flash power-loss recovery still require hardware validation. Watering thresholds remain preliminary; automatic irrigation is not active.

03 / HARDWARE — THE ORDERED BUILD

Two probes. One path to the dashboard.

The first build now includes the two soil probes, ESP32 controller, garden cable, power supply and cabinet components. The aim is a wired installation that can be inspected and serviced, with readings sent over Wi-Fi to grgaGrow. The parts are ordered; assembly, calibration and testing in the lawn are still ahead.

Procurement
Main components ordered
Next milestone
First bench assembly
Field status
Not yet installed

Reference photos below show component types and assembly accessories. Models, dimensions and pictured quantities may differ from the ordered parts.

Click a photo to enlarge. Each image links to its source. Assembly and specification checks are still ahead.

What each part brings to the build

01 / HARDWARE Ordered

ESP32-S3 controller

One ESP32-S3-RS485-CAN controller will bridge the wired probes and Wi-Fi. USB-C provides the programming connection. The delivered board variant, pin mapping and power requirements will be checked before assembly.

02 / HARDWARE Ordered

Two wired soil probes

One moisture / temperature probe and one combined moisture / temperature / pH probe. Both are intended for RS485 / Modbus RTU. Their actual register maps, addresses and calibration will be verified individually; pH remains experimental.

03 / HARDWARE Ordered

The garden cable

BITNER BiTsensor LP0170: two twisted pairs with a foil shield, 0.34 mm² conductors and a 6.5 mm outer diameter. One pair is planned for RS485 data and the other for sensor power. Cable-entry fit and communication over the final route still need testing.

04 / HARDWARE Ordered

Power & protection

The supply is ordered for the planned 12 V DC system, alongside five inline holders with 1 A fuses and 5.5 × 2.1 mm DC adapters. The supply model, output rating and compatibility still need checking; the final fuse value follows measured demand.

05 / HARDWARE Ordered

Distribution & termination

A UK2.5B terminal-block kit will organise power and signal connections on the DIN rail. Ordered 120 Ω / 0.5 W metal-film resistors provide termination parts for the RS485 bus. Placement depends on the final route and any termination already built into the devices.

06 / HARDWARE Ordered

A serviceable enclosure

A 230 × 150 × 85 mm box, two 10 cm DIN rails, 2 m of 4 × 0.5 mm² internal cable and five PG7 glands form the assembly kit. The layout will keep connections accessible; gland fit, strain relief and sealing will be checked before outdoor use.

BEFORE THE FIRST OUTDOOR READING

Build on the bench. Then move into the garden.

Start with one probe, confirm its power and protocol, then give the second probe its own Modbus address before testing them together. The final cable route, termination and sealed joints will be checked as one assembly.

Connection preparation includes gel-filled cable-joint boxes, crimped wire-end ferrules and wire labels. The PG7 glands must fit the 6.5 mm garden cable, and the delivered probes must explicitly support the intended buried installation. Automatic watering comes after reliable monitoring.

Probe 01
Moisture + temperature
Probe 02
Moisture + temperature + pH*

↓ RS485 / Modbus RTU · BITNER LP0170 cable

ESP32-S3 controller

↓ Wi-Fi / HTTPS

Ingestion → PostgreSQL

↓ Authenticated access

grgaGrow / My Garden

Planned hardware connection · Real readings pending · *pH is experimental

Hardware snapshot: 30 October 2026 · Ordered components, with delivery and bench checks ahead.

04 / THE REAL GARDEN

A practical question, close to home.

I still water the lawn manually. Sun, shade and soil conditions can make nearby areas behave differently. I want to compare how quickly they dry, how the soil temperature changes, and how long water takes to reach a probe.

My 50 square metre lawn with a robotic mower, the future test site for the two soil probes
THE TEST SITE / My 50 m² lawn. Monitoring is not installed yet; placement and cable routes must also suit the robotic mower.

This is the part I enjoy: connecting the interface to something physical, making the measurements understandable, and checking the whole path from a sensor in the ground to a decision on the screen.

05 / CURRENT STATE & NEXT STEPS

Measure first. Automate later.

  1. Online now

    Public Demo and Live views, a private cloud workspace, history, weekly reports, a garden diary, alerts, weather and sun/shade. Software behaviour is covered by local automated checks.

  2. Hardware integration next

    Verify the delivered board and probe documentation, implement the firmware, then test communication, calibration and recovery on the bench.

  3. Connect and observe

    Verify device-to-cloud ingestion, collect real readings and compare both locations through ordinary watering and weather changes. Use those observations to review soil references and thresholds.

  4. Consider irrigation

    Only after reliable monitoring: test a valve, shut-off behaviour and watering limits. Weather and notifications are available in the app; automatic irrigation remains future work.

Take a look beneath the surface.

View the public garden, or explore the simulated demo.

Project snapshot: 30 October 2026 · Live measurements pending hardware connection · Demo uses simulated data