Appearance
WiFi Access Points
Monitor every access point across your venues from one page: live status, connected client counts, and hardware details. The page refreshes automatically every minute.
The page lists access points for venues on CaptiFi devices, venues connected to a UniFi controller, and venues on a TP-Link Omada controller once Open API access has been added on the venue's card in My Venues (see Give CaptiFi Open API access). For Omada access points the table shows the name, model, status and last seen, which CaptiFi refreshes from the controller every 15 minutes. Offline alerts are not sent for Omada access points.
Where to Find It
- Log in to my.captifi.io
- Go to WiFi & venues → WiFi Access Points
What You See
Two summary cards up top, Access points online (e.g. "3 of 4") and Connected clients, then the full table:

| Column | Description |
|---|---|
| Name | The AP's name. An access point you added yourself says Added by MAC address under it |
| MAC address | Hardware identifier |
| Venue | Which of your venues it belongs to |
| Status | Online, Offline, or Not monitored for an access point you added that CaptiFi does not check |
| Down for | How long an offline AP has been down. Amber under 24 hours, red beyond that. Hover it to see the exact date and time the outage started. Shows - while the AP is online, and (unverified) in grey when we cannot currently check the AP |
| Last seen | When it last checked in |
| Clients | Devices connected right now |
Understanding AP Status
| Status | Meaning | Action |
|---|---|---|
| Online | Working and connected to CaptiFi | None |
| Offline | Lost connection to CaptiFi | Check power, Ethernet, and the venue's internet |
| Not monitored | You added this access point by its MAC address, and nothing reports its status to CaptiFi (Meraki, Aruba, Cisco, Ruckus and Fortinet access points, for example) | None. It still routes guests, and it is left out of the Access points online count |
A Down for figure marked (unverified) in grey means CaptiFi cannot currently reach the equipment that reports on that access point, usually because its controller is offline or its details have changed. The figure is our best estimate from the last successful check rather than something we are still measuring, so treat it as "offline as of then" and check the controller connection first. Reconnecting the controller replaces the estimate with a live figure.
Down for tells you whether you are looking at a reboot or a real outage. A few minutes usually means the AP is restarting. Hours means the venue has lost internet or power to that AP. Days or weeks in red means nobody has noticed it, and guests at that part of the venue have had no WiFi for that whole period.
Tip: If an AP shows offline but the venue's internet is working, power-cycle the device (unplug for 10 seconds). Most connectivity issues resolve within 2-3 minutes of a reboot.
Adding Access Points
- CaptiFi Plug & Play device: plug it in and enter the activation PIN from your kit on the device's setup page (see Device Setup)
- UniFi: APs are discovered automatically when you connect your controller (see the UniFi guide)
- TP-Link Omada: add Open API access on the venue's card in My Venues and the controller's access points are listed, with their status refreshed every 15 minutes: see Give CaptiFi Open API access
- Other hardware: Aruba, Ruckus, Fortinet FortiAP, Cisco Meraki, Cisco WLC, MikroTik, or BYOD. To list these access points here, or to use one portal address for several venues, add them by their MAC address (below)
Add an Access Point by Its MAC Address
- Click Add access point at the top right of the page
- Choose the Venue the access point is at
- Enter its MAC address. It is on the label on the access point and in your controller's device list. Colons, hyphens or no separators all work, for example
3C:22:FB:12:34:56 - Optionally give it a Name, such as "Front bar"
- Click Add access point

The access point appears in the table straight away, marked Added by MAC address. To take one off, click the bin icon next to its name, then hold Hold to remove access point to confirm. You can add it again at any time.
A few addresses are refused because no access point can have them: all zeros, FF:FF:FF:FF:FF:FF, and any multicast address (one whose first pair of characters is odd, such as 11-22-33-44-55-AA). Each access point can belong to one venue only. If CaptiFi says a MAC address cannot be added, check it against the label; if it is right and the access point is yours, contact support@captifi.io.
Access points that CaptiFi lists for you (from a CaptiFi device, your UniFi controller, or your Omada controller's Open API access) cannot be removed here, because the controller would only list them again.
Only the account owner and team members with Manage devices can add or remove access points.
One Portal Address for Several Venues
Normally each venue has its own portal address, with its site ID in it. If you run several venues from one controller or hotspot profile (a partner or managed service provider, for example), you can give every venue the same address without a site ID instead. Your controller adds the access point's MAC address to every guest's redirect, and CaptiFi sends the guest to the venue you added that access point to.
- Add each venue's access points by their MAC address (see above)
- In your controller, use the shared address for your brand:
| Brand | Shared portal address | Where the access point's MAC is sent |
|---|---|---|
| Cisco Meraki | https://app.captifi.io/guest/meraki | node_mac |
| Aruba Instant On | https://app.captifi.io/guest/aruba/ (keep the trailing /) | apmac |
| Ruckus Unleashed | https://app.captifi.io/guest/ruckus | mac |
| TP-Link Omada | app.captifi.io/guest/omada (choose https:// in Omada's drop-down) | apMac |
| Fortinet FortiGate | app.captifi.io/guest/fortinet | apmac |
| UniFi | No change: keep the External Portal Server CaptiFi set | ap |
| Cisco WLC | No change: CaptiFi's RADIUS reply always names the venue |
The shared address only replaces the portal URL. The RADIUS servers, NAS ID, walled garden and redirect settings in each setup guide stay exactly as they are for each venue.
A few things to know:
- A portal address that names a venue always wins. CaptiFi only looks at the access point when the address has no site ID, or one that no longer exists
- An access point listed at two venues sends guests nowhere: they see what they would see if it were not listed at all, "Back in a moment" for about two minutes and then "WiFi sign-in isn't set up yet" (on UniFi, "WiFi Sign-In Temporarily Unavailable"). Remove it from the venue it is not at
- On UniFi, CaptiFi already finds the venue from the controller's site and its access points. A MAC address you add is only used when nothing else can place the guest, for example a console on the Default site that CaptiFi has no API access to
- On TP-Link Omada with Open API access, the access points CaptiFi lists for the venue work on the shared address without adding them
Renaming Access Points
Click the pencil next to an access point's name to give it a friendly display name, such as "Front Entrance" or "Garden". This name is only used inside CaptiFi (AP lists and the Popular access points analytics); it never changes anything on your UniFi console, and controller syncs never overwrite it. Leave the field empty to go back to the controller's name.
Multi-Venue AP Management
Each access point belongs to a venue. Use the Venue column, or the venue switcher in the top bar, to focus on one location.
Moving an AP between venues is automatic: adopt the AP at its new venue in your controller and CaptiFi updates its venue, splash page routing, and guest authorisation within about 15 minutes. If a moved AP still shows its old venue after that, contact support at hello@captifi.io.
The page lists access points only. Switches, gateways, and routers from your controller are managed elsewhere and do not appear here.
Related Features
- Connected Guests: the live per-guest view behind the client counts
- Guest Analytics: offline APs mean missed guest data
- Offline alerts: choose who is emailed, texted or notified when an AP at a venue goes offline
- Device Status Guide: what the CaptiFi device's LED and statuses mean
- Common Issues: general connectivity troubleshooting
Troubleshooting
| Issue | Possible Cause | Solution |
|---|---|---|
| AP showing offline | Power or network issue | Check power and Ethernet; verify the venue's internet is working |
| AP online but no splash page | Captive portal not configured | Check the relevant setup guide for your hardware |
| New CaptiFi device not appearing | Not yet activated | Enter the activation PIN on the device's setup page (see Device Setup) |
| New UniFi AP not appearing | Controller connection issue | Verify the controller connection under My Venues; see the UniFi guide |
| Omada access points not listed | Open API access not added for the venue, or the app's Site Privilege is not limited to the venue's site | Open the venue's card on My Venues and click Add Open API access (or Update); see the TP-Link Omada guide |
| "This MAC address cannot be added" | The access point is already listed at another venue, or the address was mistyped | Check the address against the label on the access point. If it is right and yours, contact support@captifi.io |
| Guests on the shared portal address see "Back in a moment" for about two minutes, then "WiFi sign-in isn't set up yet" ("WiFi Sign-In Temporarily Unavailable" on UniFi), and never reach the sign-in page | The access point they joined is not added, is added at two venues, or the controller is not sending its MAC | Add the access point by its MAC address; check the table in One Portal Address for Several Venues for the parameter your controller must send |
| Intermittent offline status | Unstable internet at the venue | Check connection stability; use a wired backhaul where possible |
| Client count seems low | Placement or signal issues | Place the AP centrally and high; see Hardware FAQs |