TP-Link Omada can still be installed on CasaOS through the maintained BigBearCasaOS store, but the package is community-maintained rather than an official TP-Link Docker image. As of 2026, BigBearCasaOS lists TP-Link Omada Controller 6.2 using mbentley/omada-controller.
That means you should treat TP-Link's controller requirements and release notes as the product source of truth, while using BigBear's manifest only as the CasaOS packaging layer.
Add the Current BigBearCasaOS Store
The current BigBearCasaOS app store lists its App Store ZIP and current Omada package.
Install the Omada Controller App
After adding the store, search for TP-Link Omada Controller, inspect the image/version, and install it. Record the mapped configuration/data folders before making later updates.
TP-Link Supports Linux, Not This Docker Image Directly
TP-Link's current Omada Software Controller requirements lists supported x64 Windows/Linux platforms. The Docker image used by BigBear is maintained separately.
Keep Controller Data Persistent
The controller database contains sites, adopted devices, settings, users, and history. Verify that BigBear maps the controller's data/log directories to persistent CasaOS storage before trusting it with your network.
Use a Stable LAN IP
Reserve the CasaOS server's IP in DHCP. Omada devices and administrators should not have to chase a changing controller address after router reboots.
Back Up Before Upgrading Controller Versions
Export an Omada controller backup and protect the persistent container data before a major upgrade. Network-controller schema changes can be harder to undo than a normal web app update.
Check Adoption and Discovery Ports
If the web UI opens but Omada devices are not discovered or adopted, the container's network mode and required Omada ports matter. Compare the BigBear manifest against the current TP-Link controller documentation rather than opening random ports.
Do Not Expose the Admin UI Directly
Use LAN access, VPN, or the controller's supported cloud access rather than raw internet port forwarding to the management interface.
The Docker app guide applies to CasaOS community packages too.
Check the Current Controller Version Before Adoption
Omada devices and controller releases need compatible firmware. Before adopting a new gateway, switch, or access point, compare its firmware requirements with the controller version packaged by BigBear.
Keep the Controller Host Reachable from Management VLANs
If your Omada devices live on another VLAN, routing and firewall policy must allow the required discovery/adoption traffic. A working web dashboard on the CasaOS LAN does not prove managed devices can reach the controller.
Export a Controller Backup After Major Changes
After adopting devices, changing WLANs, or rebuilding VLANs, export a fresh Omada backup. That gives you a recovery point after configuration changes, not just before software upgrades.
FAQ
Is the BigBear Omada image official TP-Link software?
It packages TP-Link's controller in a community Docker image; TP-Link itself documents native Linux/Windows controller support.
What version is in BigBearCasaOS now?
The current repository lists Omada Controller 6.2.
Should I back up before updating?
Yes. Export controller configuration and protect persistent data first.
Why does the UI work but devices do not adopt?
Check required Omada discovery/adoption ports, network mode, VLAN routing, and the device's controller discovery path.
