New: AI-powered Google Review automation is liveLearn more →
VoqadoWiFi
Log inStart free
Free Tool

Is my access point compatible?

Pick your vendor and your controller. You get a straight answer, the reason behind it, and the exact settings the setup depends on. No form, no sales call, no waiting.

VoqadoWiFi supports TP-Link Omada and Ubiquiti UniFi. If you run anything else, this tool tells you so instead of routing you to a salesperson.

1Your WiFi vendor

Your verdict appears here

Answer the questions on the left. Every verdict comes with the reason behind it and the settings the setup actually depends on, so you can check the claim yourself.

Verdicts here reflect what the VoqadoWiFi integration documentation states. Where a specific model or firmware build is not named, confirm the external portal settings against your own controller documentation rather than treating silence as a yes.

Compatibility is a yes or no, so check it before anything else

Most decisions about guest WiFi software are trade offs you can revisit later. This one is not. A captive portal platform either speaks to your controller or it does not, and no amount of budget, feature depth, or goodwill changes that. Everything else you might compare is downstream of the handshake working.

The controller is the integration, not the access point

The portal is configured on the controller and the authorisation call goes to the controller. Which access point model a guest happens to associate with barely matters, which is why a model by model table would tell you less than the question this tool asks.

The handshake has two halves

The redirect sends the guest to the portal, and the callback tells the controller to let that device online. Both have to work. A portal that loads beautifully and never authorises anyone is the most common way a setup fails.

The blocker is usually reachability

Controllers that live inside the venue are invisible from outside by default. That is fine for running the network and fatal for an external portal, until you publish the controller through a firewall rule, a reverse proxy, or an outbound tunnel.

Finding out late is expensive

Discovering an incompatibility after signing a contract means either replacing hardware or abandoning the platform. Ten seconds with a checker beats a sales call that ends in a maybe.

What you need before you start

A compatible controller is the first requirement. These four are the rest of them, and every one of them is a setting you already control.

Controller admin access

You need to sign in to the controller and change guest network settings. Create a dedicated account for the integration rather than handing over your own administrator login.

Portal type set to external

The guest SSID has to be configured to send guests to an external portal, with the VoqadoWiFi portal URL entered exactly as the dashboard shows it.

A walled garden entry

The VoqadoWiFi domain has to be permitted for unauthenticated devices. Without it the guest is redirected to a page they are not yet allowed to load.

A phone that has never joined

A device the controller already authorised goes straight online without touching the portal, which makes it useless as a test. Use a fresh device or clear the authorised client first.

Compatibility questions, answered

If your access points are adopted by a TP-Link Omada controller or a Ubiquiti UniFi controller, yes. Those are the two controller platforms VoqadoWiFi integrates with. The access point model matters far less than the controller, because the portal is configured on the controller and the authorisation call goes to the controller, not to individual access points.

The OC200 and OC300 hardware controllers, the Omada Software Controller from version 5 onward, and the cloud based controller are all supported. There is deliberately no model by model table, because the thing that decides the answer is whether your controller exposes external portal configuration on the guest SSID, not which box it runs on.

Both work. UniFi OS consoles such as the Dream Machine and UDM Pro authenticate at /api/auth/login and address the network API under a /proxy/network prefix, while the self hosted Network application uses /api/login with no prefix and usually listens on 8443. VoqadoWiFi detects which one it is talking to and adapts, so you do not have to declare it up front.

No. If your Omada or UniFi deployment already runs a guest SSID with a portal, everything the integration needs is already in place. The change is a portal URL in the controller and a set of credentials in your VoqadoWiFi dashboard.

Yes, and it is the most common blocker. After a guest submits the form, VoqadoWiFi calls the controller to authorise that device. If the controller cannot be reached from outside the venue, the call never lands and the guest stays stuck on the portal. Publish the controller through your firewall, a reverse proxy, or an outbound tunnel before you go live.

No. Omada and UniFi controllers ship with self signed certificates and most operators never replace them. The integration tolerates that rather than requiring a publicly trusted certificate before guest login will work.

Then the integration does not exist today. VoqadoWiFi supports TP-Link Omada and Ubiquiti UniFi, and we would rather tell you that plainly than imply broader support. Talk to us before you sign up if you run something else.

Yes. The network vendor is a per location setting, so a mixed estate runs under a single account with one shared guest database.

Check the external portal settings in your own controller documentation rather than assuming a verdict. If the controller can point a guest SSID at an external portal and expose an API the platform can call to authorise a device, it has what the integration needs. Test Connection in the dashboard will tell you the rest before any guest is involved.

Compatible? Then the setup is a settings change

No new access points, no rip and replace. Point the guest SSID at an external portal, add the controller details, and run Test Connection before a guest ever sees the page.