hub.

Adding a device registers it and grants its MQTT topic access. Then, with the board plugged in over USB (Chrome or Edge): 1. flash the shared firmware — Flash firmware via USB flashing needs Chrome or Edge — then 2. click 📶 Wi-Fi setup on the device's row to send it Wi-Fi credentials and its certificate over the same cable.

After adding, run this on the machine to enroll it (Linux / Raspberry Pi, as root — installs a bash agent, nothing else needed): Windows (PowerShell as Administrator, nothing to install): It starts reporting CPU / RAM / disk / temperature within a minute.

A recorder can’t run an agent, so a small always-on box on the NVR’s network polls it and forwards to the Hub. After adding, run this on that box (as root), filling in the recorder’s LAN IP and admin login: It reports up/down, HDD status and capacity within a minute or two.

A site gateway is the always-on home box that watches your whole LAN. After adding, run this on it (as root), listing hosts to watch as name=ip pairs: It reports host up/down, internet health, and new-device alerts.

Compiles the current ESP32 firmware source on the Hub and publishes it, so online boards on an older build are offered Update to … in their health panel. Bump FW_VERSION in the source first, or this republishes the same version.

Unofficial WhatsApp Web link — use a dedicated number, not your personal main line.

Threshold rules watch any telemetry field on any device. e.g. l1_v min 190 / max 250 · l1_w max 3000 · batt_val min 3.3.

Each automation is When (a trigger) → Do (an action). Fires are rate-limited by the cooldown.

A relay action targets an ESP32 (over MQTT) or a Pi/gateway pin (declared in its Relays panel) by name. New-device alerts are also a built-in toggle in the Alerts tab.

Gauge & tank use min–max as the scale; graph plots the last 24 h; stat shows the live number. Server fields include cpu_pct, ram_pct, disk_pct, speed_down_mbps, speed_up_mbps, and speed_ping_ms. Adding a speed field automatically enables a 30-minute test on computer/gateway agents.

Owner controls security. Administrator manages Hub. Operator can use assigned devices. Viewer has read-only assigned access. Every request is checked by the backend.

Leave both blank for a full read-only key. Pick devices and/or list sensors (telemetry fields) to limit exactly what this key can read.

Keys are read-only — telemetry + alerts via /api/v1 only. No device control, config, or user access. Shown once at creation, so copy it then. Your AI sends it as Authorization: Bearer <key>. Endpoints: /api/v1/devices, /api/v1/devices/:id/latest, /api/v1/devices/:id/history, /api/v1/alerts.