Controller Integrations

Bring controller fleets into one pane

A real ISP rarely runs one vendor's controller. There is a UniFi controller for the indoor APs, cnMaestro for the Cambium PtP and PtMP gear, UISP for the edge and airMAX fleet — and each one is its own login, its own model, and its own idea of what a device is. ISPAgents pulls devices, topology, and telemetry from those external controllers into a single tenant-scoped pane, mapped to canonical devices so the same router is not counted three times.

This is early access. The adapter framework is real and most vendors are proven against fixtures today, with live production evidence still being gathered. Read the boundaries below before planning a rollout — we would rather name the maturity than imply blanket production support.

A generic controller-device adapter

Under the hood is a generic controller-device adapter framework: it discovers devices from an external controller and normalizes what the controller exposes — topology, wireless, events, inventory, and metrics — into ISPAgents' own model. A resource-mapping service then maps external device IDs to canonical devices, so a device already known through TR-069, SNMP, or RouterOS is recognized as the same device rather than duplicated. The result lands in unified NMS tabs and runs under the platform's supervised collector framework.

• Discover devices from the controller, not by re-walking the network.
• Normalize topology, wireless, events, inventory, and metrics into one model.
• Map external IDs to canonical devices so there is no double-counting.
• Surface everything in the same unified NMS tabs as native sources.

Supported controllers

UISP already has its own deeper integration surface; the controller-adapter framework is the generic path that brings the others into the same pane on the same discipline.

Read-only and safe by design

The integration is one-way read from the controller into ISPAgents. It pulls device, topology, and telemetry data in for visibility — it does not push config back, change controller settings, or take control of devices the controller manages. That boundary is deliberate: the controller stays the system of record for its own fleet, and ISPAgents becomes the cross-vendor pane that maps every controller's devices to one canonical identity.

• One-way read: controller to ISPAgents, never the reverse.
• No config push and no bidirectional control of controller-managed devices.
• Tenant-scoped visibility, isolated per tenant like every other source.
• Canonical mapping so a controller device joins the timeline it already belongs to instead of creating a duplicate.

Coexist with the controllers you keep

Controller Integrations are built to coexist, not to replace. Keep UniFi, cnMaestro, and UISP running exactly as they are, and let ISPAgents read across them into one pane where the gear maps to canonical devices. Start with the deeper UISP integration, fold the rest into unified device management so controller devices sit beside TR-069, SNMP, and RouterOS sources, and rely on canonical subscriber and device identity so every controller device resolves to one subscriber, site, and device.