What you'll need
- Admin access to your Omada Controller (Cloud or on-premises)
- Omada Software/Hardware Controller v5.12+ or Omada Pro, if you want MyWiFi to manage sites/SSIDs directly through Omada's Open API — the free Cloud-Based Controller (CBC) doesn't support this
- A dedicated Hotspot Operator account (not your controller admin login)
Steps
- In Omada Controller, go to Settings > Hotspot Manager > Add Operator and create a dedicated Hotspot Operator account scoped to the relevant site. MyWiFi needs this operator account, not your admin login — Omada rejects admin credentials for the guest-authorize calls MyWiFi makes.
- Go to your guest SSID settings, enable the captive portal, set the portal type to External Web Portal, and paste the MyWiFi splash page URL into the Custom Portal Server field.
- Add the MyWiFi portal domain (and any CDN hostnames it uses) to the Walled Garden list so the splash page loads before guests authenticate.
- If you want MyWiFi to provision sites or manage SSIDs directly (optional): go to Global View > Settings > Platform Integration > Open API, create a Client Mode app, and note the Client ID and Client Secret. This step requires Omada Software/Hardware Controller v5.12+ or Omada Pro — skip it if you're on the free CBC controller.
- In the MyWiFi dashboard, go to Devices and click Add Device.
- Select the Location, name the device, and under Select Your Hardware choose TP-Link Omada.
- Enter your Omada connection details as prompted — your controller's URL, the Controller ID (visible in your controller's URL bar), and the Hotspot Operator username/password from step 1 — and save.
Best practice: the controller's HTTP portal will only redirect to an HTTPS splash URL, and it will only accept a portal login from the Operator role you created in step 1 — using the admin account here is the most common setup mistake and will silently fail guest logins.
Comments
Please sign in to leave a comment.