UniFi Fleet Dashboard

Devices (filtered)

—

Offline (high confidence)

—

Offline (no heartbeat)

—

Suspect

—

Links: site + device

Alert thresholds:

How “links” work: If a site exists in SITE_CONSOLE_MAP, links go to that UDM/controller (local). Otherwise, links go to UniFi Cloud search for the MAC.

Tip: set SITE_CONSOLE_MAP["PSFC Ramsey"] = "https://192.168.2.1" (or hostname) for one-click local console access.

Offline Devices (high confidence)

These are considered truly offline (based on heartbeat/last-seen where available and your Worker’s “offlineHigh” bucket).

Host	Name	Type	Model	MAC	IP	Status	Why
Loading…

Offline (no heartbeat)

These are “offline” but without a reliable heartbeat/last-seen signal (common with server-hosted controllers / API gaps). Treat as “needs verification”.

Host	Name	Type	Model	MAC	IP	Status	Why
Loading…

Suspect Devices

Within grace window or ambiguous signals (your Worker “suspect” bucket).

Host	Name	Type	Model	MAC	IP	Status	Why
Loading…

Notes

If you still see “online” in UniFi but this shows Offline/Suspect: that’s usually because the API feed lacks a lastSeen/heartbeat for server-hosted controllers, or because the “snapshot” status in /v1/devices is stale. Your Worker’s newer logic is already preventing “lastSeen === null ⇒ offline”.

If you want per-site trust rules (e.g., “PSFC Ramsey always trust state from controller X”), we can add a simple config object in the Worker and surface it here.