No controller connected yet
Power the ESP32-S3 controller and join its PumpController-… setup access point. Open http://192.168.4.1, then enter this server's URL, the device token and the device ID.
Telemetry appears here within a few seconds of the first successful upload.
Waiting for telemetry
The autonomous controller keeps running when this cloud link is down.
- Last contact
- —
- Address
- —
- Pending commands
- 0
History
Telemetry stored on the Hetzner server. Local pump protection does not depend on this history.
Waiting for history…
Operating mode
Changes are queued and applied by the controller within one upload interval.
AUTO starts Pump 1 only above the configured SoC and PV thresholds, with a healthy level sensor and no irrigation interlock.
Manual overrides
Only available in MANUAL mode. Safety limits still apply locally.
A manual Pump 1 run is always stopped by low water level, a stale sensor, the irrigation interlock, or the runtime limit.
Autonomous thresholds
Applied live and persisted in the controller's NVS. Local safety rules remain in force.
Command history
Queued commands are delivered on the controller's next upload and expire after 24 hours.
| # | Command | Payload | Status | Created | Result |
|---|---|---|---|---|---|
| Sign in to see command history. | |||||
Local safety, remote visibility
The ESP32-S3 runs the pump decision loop, dry-run protection and irrigation interlock on-device. This dashboard is an outbound HTTPS client view of the controller; losing the cloud link never stops local protection. The ESP32 local portal is for setup and diagnostics only.