System What is being built and explored

SystemPROTOTYPE

MicroGrow

A local-first growing environment project exploring understandable ways to monitor and control a single growing node.

Project
MicroGrow
State
PROTOTYPE
Scope
Single-node V1
Operation
Local-first
Current physical MicroGrow prototype hardware and connected development components.
Current MicroGrow single-node prototype; public-safe derivative for owner review.

How it works at a high level

This explanatory flow shows the project’s role without presenting an internal architecture diagram or claiming capabilities beyond the current evidence.

  1. Climate sensorMeasures the growing environment.
  2. ESP32 local controllerReceives local inputs and coordinates the node.
  3. Bounded control logicApplies the documented control rules.
  4. Relay outputsProvides the controlled output path.
  5. Flutter local interfaceSupports monitoring, control and diagnostics.

Why it exists

Indoor growing depends on paying attention to environmental conditions and responding consistently. MicroGrow explores how local monitoring and bounded control can support that work without making a cloud service the centre of the system.

What it is

The current V1 is a single-node system built around an ESP32 controller, a local Wi-Fi and HTTP path, a climate-sensor input, relay outputs and a Flutter application for monitoring, control and diagnostics.

Current state: The project is at a prototype and controlled validation stage. The software spine and documented host checks are present, while physical validation gates remain partial and require further evidence.

What exists today

The repository records a single ESP32 node path, an SHTC3 climate-sensor integration, four relay outputs with safe-start behaviour, local HTTP communication and a Flutter client with monitoring, control and diagnostics workflows.

Documented

Repository evidence

Current product and architecture records describe the single-node V1 scope.

Implemented

Source-controlled implementation

The firmware, local HTTP path and Flutter application are represented in the current source record.

Validated

Evidence exists, not all gates closed

Firmware host checks, Flutter verification and prior bench records are present.

Still open

Owner and evidence review pending

Further physical validation is required before wider publication or readiness claims.

Visual evidence

These captures show selected current project surfaces. They do not establish production readiness.

MicroGrow dashboardCurrent Flutter interface used for monitoring, control and project status; public-safe derivative for owner review.
MicroGrow diagnostics viewA current diagnostics and status view; this public-safe derivative does not establish complete fault handling or production readiness.

How it fits into New Earth

MicroGrow is one practical project within the wider New Earth ecosystem. It explores local capability, maintainability and direct understanding while remaining compatible with wider cooperation. It is not the whole New Earth food strategy or proof that the wider model is complete.

Evidence and current progress

Public-safe evidence includes documented architecture, source-controlled implementation, firmware host checks and Flutter verification records.

The current evidence record also includes prior bench and node-validation material, but it does not establish production readiness or a finished physical product.

Current limitations

The current V1 scope is a single node; multi-node coordination and cloud services remain future work.

Physical load, calibration, enclosure, thermal, end-of-line and pilot-user evidence are not all closed in the current record.

MicroGrow is not presented as commercially available, production-ready, autonomous or a guarantee of growing outcomes.

Next controlled step

What comes next

Complete the next controlled physical validation checkpoint, including the current hardware and evidence gaps, before considering a wider rollout.

Related systems