Navigation
20.17. Connect UniFi Sites and Network Devices
Connect UniFi API keys, map sites to clients, sync adopted network devices as assets, and configure offline alert handling.
Connect UniFi so technicians can see a client's adopted gateways, switches, and access points as AlgaPSA assets. Map each site to the right client before syncing devices, then decide which offline alerts should become tickets.
Before you begin
UniFi requires Enterprise Edition with access to advanced assets. Use an internal account with system_settings:read to inspect settings and system_settings:update to manage the connection.
Prepare the AlgaPSA clients that will own the sites and the UniFi API keys that can reach them. Choose the appropriate connection mode:
| Connection | What to prepare |
|---|---|
| Site Manager | A key created under Independent reaches independent consoles; a key created under a fabric reaches that fabric. Add a key for each fabric you manage. |
| Local controller | An API key for the controller and a Controller URL reachable by the AlgaPSA server. |
The integration syncs adopted network devices. It is not a remote-control connection for running commands on those devices.
Connect and check API keys
- Open Settings > Integrations > RMM and select UniFi.
- In UniFi Connection, enter a Label, choose Connection mode, and enter the API key. Supply Controller URL for a local connection.
- Select Save Configuration for the first key. Use Add key for additional keys, with labels that help staff identify the fabric or controller they belong to.
- Select Re-check all keys. Review each key's Status, Consoles reached, Last error, and Last checked.
For a rejected key, use Replace key and re-check the connection. If a console is missing, check the key's scope before assuming that it has no devices. An Independent key does not also cover every fabric.
Map sites and sync devices
- In Sync & Site Mappings, choose Discover Sites.
- Review each UniFi Site and its Reached by information. Set Mapped Client to the client that owns the site and, where appropriate, choose a Default Contact.
- Review the site's Auto Sync status, then choose Run Device Sync.
- Check the processed, created, and updated counts and any reported error. Open the client's assets to confirm that the expected network devices belong to the correct client.
Devices in unmapped sites are skipped. For example, map the fictional GreenLeaf Downtown site to GreenLeaf Dental Group before syncing its access points. Avoid mapping an unfamiliar site just to clear the list; confirm ownership first.
Use the device-sync settings on the same page to maintain the sync schedule after a successful manual check.
Configure offline alerts
Once connected, Offline Alerting controls how long a device must remain continuously offline before an alert is raised.
- Set Offline grace period (minutes) to a whole number from 0 to 1440. Zero raises an alert immediately.
- Select Save Alerting Settings.
- Configure ticket creation, priorities, and auto-resolve in the alert rules below. An offline alert creates a ticket only when your rules call for one.
- Use Check Offline Devices Now to run a check and inspect the resulting alert or ticket where applicable.
The alert resolves when the device comes back online. Ticket handling follows your alert rules; check those rules before promising that every recovered device closes its ticket automatically. See RMM alert automation for the shared routing workflow.
Operational checks
- After changing keys, re-check which consoles remain reachable before running site discovery again.
- After changing a site mapping, verify device ownership in the client's asset list.
- If a sync reports an error, inspect the connection and per-key error details before retrying.
- Keep the grace period long enough for the interruptions you expect during routine network work, then review whether the resulting tickets are useful to dispatch.
