Overview
What's happening with your machines right now.
Devices online
0/ 2
Commands sent
0this session
MQTT uptime
—
Avg. reply latency
—
Recent activity
Devices
Full control and per-device diagnostics.
Topology
Live system map — nodes glow with real state, links pulse on real MQTT traffic.
This reflects the real topology from
esp8266.ino — the browser never talks to the ESP8266 directly, only to the broker, which the ESP8266 and desktop_client.py also connect to independently. Node glow = live device state. Link pulses = actual publish/message events, not decorative.Automation
Schedule wake / sleep / shutdown at a time of day.
Rules fire from this browser tab — they only run while this page stays open on a device that's on. For a schedule that runs even when nothing has this page open, use a Cloudflare Worker Cron Trigger publishing to the same MQTT topics (see
gateway/ in the README) instead. This is a real limitation, not a bug — flagging it so a scheduled shutdown doesn't silently not happen.New rule
Scheduled rules
Diagnostics
Raw MQTT traffic and connection health.
Connection
State—
Broker—
Connected since—
Reconnect count0
Messages received0
Messages published0
Last errorNone
Quick test publish
Message trace
Activity
Everything that's happened, searchable.
Settings
Behavior, notifications, and appearance.
Appearance
Theme
Both stay monochrome
Reduce motion
Turns off pulses and transitions
Behavior
Confirm destructive actions
Shutdown, sleep, hibernate
Sound
Soft tick on state changes
Desktop notifications
Wake complete, unexpected offline
About
Firmware protocolv1 (unchanged)
Desktop wake timeout60s
Server wake timeout180s
Session started—