Before you start
- Confirm the UniFi console or controller owns the intended AP.
- Use a controller account or API credential with only the permissions required for the target site.
- Identify the exact UniFi site and customer SSID.
Procedure
Follow these steps in order
Bring the controller online
Open the UniFi console, confirm the AP is adopted and Online, and resolve firmware, inform, or adoption problems before adding K7abeer.
Prepare the customer network
Create or select the customer SSID, VLAN or network, DHCP path, security mode, and guest or captive-portal policy.
Add the controller connection
In K7abeer, choose UniFi and enter the approved controller URL and credentials or token. Select the exact site instead of relying on a duplicate display name.
Verify device identity
Run Check connection and compare the controller, site, AP model, MAC, and branch with the physical installation.
Apply only supported controls
K7abeer exposes voucher and captive-portal operations only when the connected controller and site report the required capability.
Test with a new client
Connect a fresh phone, confirm DHCP and DNS, open the portal when enabled, authenticate, and verify the intended time and speed policy.
Verify success
- The AP remains Online in the selected UniFi site.
- K7abeer shows the same controller site and AP identity.
- A new client reaches the intended network and portal.
- Unsupported controls remain unavailable instead of silently failing.
Troubleshooting
The AP is missing
Confirm it is adopted into the selected UniFi site, the API identity can read that site, and the controller URL is reachable from the configured connection mode.
Voucher or portal controls are unavailable
The active controller mode may not expose a validated enforcement API. Use the controller-supported portal path or the gateway that performs customer authentication.
Was this guide helpful?
Your response helps the system owner prioritize documentation updates.