Paste the dashboard token given to you when your farm was set up.
Paste the dashboard token given to you when your farm was set up.
—
—
—
—
It closes the valve when the time is up even if your phone loses signal, the app is closed, or the panel is unplugged. This screen asks — it never holds the valve open.
Each version is read from the thing that is running, never from a constant in this app.
These are on the radio network, not wired to the pod. Every command travels to the pod first and waits there for the node to wake up.
Every command carries a dead-man. The node closes its own actuator when the time is up even if the radio link drops, the pod reboots, or this app is closed. Nothing here can hold an actuator open.
The four tabs stay deliberately small. Everything that is setup rather than daily use lives here.
—
The pod names itself from its MAC address at boot and
prints device_id=… on the serial console. The ID is what the backend keys on.
The percentage is computed in this browser from raw counts — pct = 100 × (dry − raw) ÷ (dry − wet). Raw counts are what the pod sends and what the database stores, so changing these numbers never rewrites history. Measured on tp-7251c0 on 2026-08-20: dry 2810, wet 1400 (a glass of water, not field saturation). Per spec S10 stage 1.
Tick what is physically wired. A fitted-but-silent channel then reads no signal instead of vanishing, so a failed sensor is visible rather than absent. Saved in this browser only.
These four tabs show one moisture, air-temp and humidity channel — the reading that answers "is the soil wet enough". A pod with several probes fitted has more than that, and every configured channel with its own GPIO and an explicit no signal state lives on the operator dashboard.
For everything exactly as stored — raw ADC counts, unix
timestamps, verbatim event detail, the command audit, gaps, and the assembled
runs with their evidence — open the
raw page. Nothing on it is scaled or
interpreted, and it cannot change anything.