ZosteraGrids field node

2026-03-21

Code and docs

v1 ESP32 + SIM7000G firmware for bench and homelab E2E: deep sleep, batched uplinks, SD store-and-forward. Edge half of ZosteraGrids. Uplink JSON is still RAUA Platform's ingest contract reference—not production field deployment.

embedded · esp32 · iot · telemetry · platformio

Repository

This firmware targets the LilyGO T-SIM7000G: ESP32-class hardware with cellular (NB-IoT / LTE-M) and optional GNSS. The board is meant for battery and small solar while measuring water-quality-relevant signals.

It is the edge half of ZosteraGrids (v1) — bench and homelab E2E, not a production field fleet. The homelab backend is ZosteraGrids backend. The successor platform is RAUA Platform. This repo’s uplink JSON shape is still the ingest contract reference. Production firmware moves to Nordic LTE on a separate track.

What is built today

  • PlatformIO firmware for LilyGO T-SIM7000G: ESP32 + SIM7000G modem, optional GNSS (off by default)
  • Power-aware architecture: deep sleep duty cycles, SD store-and-forward, batched uplink design (30 s sample / hourly batch defaults in docs)
  • Sensor channels defined: turbidity, dissolved oxygen, temperature, two analog inputs
  • Modem bring-up documented: RAT lock, APN, short sends, power-down discipline from bench modem bring-up and lab integration
  • NVS-backed configuration, serial monitor workflows, compile-db ergonomics for IDE navigation
  • Wi-Fi lab path retired (v0.1.0-wifi-lab tag); cellular HTTP uplink and time sync are the active integration target — HTTP time sync still stubbed until the modem path is fully wired
  • Uplink JSON shape is the ingest contract carried into RAUA Platform

Multi-month solar field runtime is the design target, not a validated deployment outcome. No production cloud path. No Nordic LTE ingest client here.

Power is the product requirement

The constraint is energy. Sample every second on USB and you kill a field node. The project embraces deep sleep, batched uplinks, modem power modes, and conservative GNSS because the success metric is months, not a bench demo.

That shows up as SD store-and-forward, careful wake sequencing, and notes on what is still stubbed (HTTP time sync until the modem path is fully integrated). I would rather ship a partial integration with a written plan than pretend the stack is finished.

Cellular bring-up

RF, operator APNs, SIM quirks, PSM/eDRX acceptance — cellular IoT is where embedded work meets distributed systems with attitude. The README modem quick start is condensed bench and lab notes, not filler.

On the sensing side, turbidity, dissolved oxygen, temperature, and analog channels become calibration and cabling work long before they become plots.

Observability without a desktop attached

Once the device is sealed in a box on a pontoon, the debugger is serial traces, NVS-backed configuration, and eventual OTA discipline. The repo documents PlatformIO workflows, compile databases for IDE navigation, and the serial monitor because that is how the board comes up.

Pair with the backend

The field node emits telemetry shaped for ingest into the homelab backend. Read the v1 pages together: this one is joules and retries on the bench; the other is API contracts and dashboards on a home network. Where the stack went next is RAUA Platform.