Skip to content

Roadmap

This roadmap is directional. It is organised around demonstrable vertical slices rather than a fixed release date. The project is currently proving the Phase 2 slice — Grow Core running end-to-end against a simulator and Home Assistant.

Publish concept and architecture, define terminology, create growrig-platform and growrig-firmware, choose licenses, and establish the contribution process.

An ESP32/XIAO breadboard controller with 2–4 PWM fan channels, RPM feedback, a temp/humidity sensor, local fallback behavior, an ESPHome package, and Home Assistant entities. Exit: safe fan control continues through a Hub restart.

A Go service with SQLite storage, a Home Assistant adapter, an environment and device-role model, fan controller logic, a live API, a minimal SvelteKit dashboard, and a simulator. Exit: users assign grow roles instead of editing HA automations.

The ESPHome native-API path through Home Assistant and a direct MQTT path, with one authoritative adapter per controller, controller health and presence, command timeout, and a versioned-policy prototype. Exit: the same controller works through either path.

HAOS add-on packaging, ESP Web Tools integration, supported board profiles, prebuilt firmware manifests, USB/BLE Wi-Fi provisioning, and a controller registration flow. Exit: a new user can flash and enroll a controller without editing YAML.

Polished web onboarding, a live dashboard, manual overrides, alerts, recipe basics, cycle history, and a Flutter mobile prototype with QR pairing. Exit: daily operation no longer requires the Home Assistant UI.

Documented router setup, a recommended OpenWrt configuration, a default firewall model, camera isolation, and Grow Hub discovery across the gateway. Exit: a reproducible isolated Grow Network on commodity hardware.

Stable Controller requirements, custom PCB feasibility, integrated power and protection, display expansion, and a hardware-in-the-loop test fixture. Exit: enough evidence to design Grow Controller X4 hardware.

Sensor Pod, Irrigation Controller, Grow Panel, a hardware compatibility catalog, a recipe repository, verified third-party equipment, and an optional official Grow Gateway.

These influence early interfaces even when implemented later: a semantic installation digital twin, signed versioned policies, secure per-device identity, rollback-safe OTA, simulator and recorded-data replay, explainable adaptive control, structured observability, trusted release provenance and SBOMs, and an open extension SDK.