Early Access Hardware Controllers Omada SDN Controller 6.2.10 Pre-Release Firmware (Update on 21st Apr, 2026)
This Article Applies to
OC200(UN)_V1_1.40.x_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V2_2.25.x_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V3_3.2.x_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V1_1.5.x_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V2_2.4.x_pre-release (Built-in Omada SDN Controller 6.2.10)
OC300(UN)_V1_1.34.x_pre-release (Built-in Omada SDN Controller 6.2.10)
OC400(UN)_V1_1.12.x_pre-release (Built-in Omada SDN Controller 6.2.10)
Overview
We hope to offer you the opportunity to experience the new features added in Controller v6.2.10.x in advance, and to allow TP-Link to thoroughly test the firmware in your real network environment and across scenarios before the official release. All feedback is welcome, including reports of successful upgrades.
Release Notes
Version Info
This version of the Controller is fully compatible with the Omada App version 5.2.x.
Supported Device Models
For device models Omada Software Controller supports, refer to the Omada Cloud SDN Platform Compatibility List.
Added support for Access Points: Flex Bridge 5.
New Features
- Added support for Wi-Fi Calling, available at Site > Device Config > AP > Wi-Fi Calling, Site > Network Config > Network Setting > WLAN > Advanced Settings > Wi-Fi Calling. The transmission of voice and text messages over Wi-Fi networks is more stable, and a new accompanying Wi-Fi Calling statistics chart has been added. (Requires EAP firmware support)
- Added support for load balancing across access points, available at Site > Network Config > WLAN > SSID > Advanced Settings > Load Balance, balancing client distribution across access points and frequency bands to improve network performance. (Requires EAP firmware support)
- Added support for SSID Band Steering, available at Site > Network Config > WLAN > SSID > Advanced Settings > Band Steering, the SSID configuration takes precedence over the Site configuration. (Requires EAP firmware support)
- Added support for WLAN Optimization Schedule, available at Site > Network Config > Network Setting > WLAN > WLAN Optimization > Manual WLAN Optimization > Schedule. Configuration can be done by Day, Week, and Month.
- Added support for displaying the AFC acquisition status, available at Device > Device List > AFC. (Requires EAP firmware support)
- Added support for CCI and AP Density charts, available at Site > Dashboard > Wi-Fi > WLAN Optimization. Co-channel interference (CCI) indicates the degree of interference experienced by APs on the same channel, AP density reflecting the deployment status of APs.
- Updated SD-WAN access control logic, Users must have All Sites permissions to view the SD-WAN page. SD-WAN page can be modified by Modify, Viewer only allows viewing, and Block hides.
- Added support for PVST/PVST+/PRST/RPVST+, available at Devices > Device List > Manage Device > Config > Services. The addition of RPVST improves link utilization and fault recovery speed in multi-VLAN scenarios. CIST Priority and MaxHops are not supported in this mode. (Requires Switch firmware support)
- Added support for configuring stack port speed on L3 switches, devices with different stacking port speeds can now form a stack group. Available at Devices > Device Group > Stack Group. (Requires Switch firmware support)
- Update the configuration of SNMPv3, available at Network Config > General Settings > SNMP. Added Security Level, Authentication Mode, Authentication Password, Privacy Mode and Privacy Password configurations. (Requires firmware support, Gateway support will be available in a future firmware release)
- Added support for Cloud Owner Permission Migration, available at Account > User. Local Owner and Cloud Owner users are allowed to migrate Cloud Owner to an invited Cloud user. After a successful migration, the Cloud Access user becomes the new Cloud Owner, and the original Cloud Owner is downgraded to Admin.
Added support for Backup & Restore through Cloud Access, available at Settings > Maintenance.Added support for Manual Upgrade via Cloud Access, available at Settings > System Settings > Manual Upgrade.- Added Description field to Portal Access Control, available at Site > Network Config > Authentication > Portal > Access Config.
- Added support for PPSK configuration on the 6Ghz band, available at Site > Network Config > Network Settings > WLAN > SSID. (Requires EAP firmware support)
- Added support for viewing L3 switch dynamic resources, available at Devices > Device List > Manage Device > Config > General Config. Supports viewing the current device SDM template, current resource usage, total resource utilization, and remaining available resources.
- Added support for static routes in SD-WAN, allowing hubs to configure multiple non-local network routes to enable spoke devices to access hub resources for complex routing scenarios such as third-party devices or remote VPNs, available at Global > SD-WAN. (Requires Gateway firmware support)
Enhancements
- Optimized EAP topology identification for wired clients.
- Automatically modify the Legal DHCP server address and automatically fill in the server IP, available at Network Config > LAN.
- Optimized the entry points for Restore and Migration functions, available at Global View > Settings > Migration > Organization Migration. The Restore function can only restore backup files for the current Controller. Backup files for other Controllers can only be imported via migration.
- Optimized EAP batch configuration experience, available at Site > Devices > Batch Action > Batch Config. The display logic has been adjusted and the configuration result will now be displayed after configuration is complete.
- Optimized the display and sorting of Client and Device list.
- Optimized multiple interactions, now supports drag-and-drop selection of ports, available at Dashboard > Topology > Quick Config > Extend Mode, Port Reboot, Port Isolation and Network Wizard; Network Config > Switch ACL, Port Schedule and OUI Based VLAN.
- Optimized the Quick Setup process and simplify configuration steps.
- Optimized VLAN configuration by adding VLAN configuration to the Switch Port Profile, which in turn optimizes the Port page and VLAN page, improving configuration flexibility, available at Device Config > Switch Ports > Port Profile; Device > Manage Device > Ports; Network Config > LAN; Device Config > Switch Ports > Port Setting.
- Optimized Site Migration, an exit button has been added, the Skip button for the Export Site step has been changed to Next, and the Skip button for Migrate Site has been removed, available at Global View > Settings > Migration > Site Migration.
- Optimized Lock to EAP function, when the Lock AP configured by the Client is offline, the Client can connect to others under the Site.
- Other feature optimizations include improved Cloud Access connection speed, faster page load times, and enhanced Portal authentication page performance.
Notes
- Please note that Controllers on different platforms may vary in features, even if their first three digits of the version code are the same. For example, the Linux Controller currently supports Cluster Mode, but the Windows Controller doesn't support it yet.
- The Omada SDN Controller can only manage specific devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
- Since version 5.14.32, the Omada Software Controller no longer supports upgrading from Controller v4.
- To strengthen overall security, we recommend upgrading all devices to the latest firmware.
Firmware Download
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Pre-release firmware!
(2) For the sake of insurance, it's always recommended to save a copy of the controller Backup Config file before upgrading or downgrading.
(3) You may follow the following guide to upgrade your Omada Controller. How to Upgrade or Downgrade Omada SDN Controller.
Firmware Download Link
Direct Download
OC200(UN)_V1_1.40.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V2_2.25.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V3_3.2.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V1_1.5.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V2_2.4.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC300(UN)_V1_1.34.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC400(UN)_V1_1.12.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V1_1.40.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V2_2.25.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V3_3.2.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V1_1.5.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V2_2.4.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC300(UN)_V1_1.34.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC400(UN)_V1_1.12.11_pre-release (Built-in Omada SDN Controller 6.2.10)
Additional Information
If somehow you encounter an issue during or after the controller upgrade, it's suggested to contact us with the following info:
- Omada Controller version (previous and current)
- Device Model(s), Hardware and Firmware versions
- (if possible) A copy of the Log file and Backup Config file
If you decide to downgrade the controller before reporting the issue to TP-Link, it's recommended to save a copy of the current Log file and Backup Config file, which could help TP-Link investigate and address the problem quickly.
>> How to get the Log file and Backup Config file for Omada SDN Controller:
-
If your Windows software controller failed to launch, please locate the controller installation path for the Log file.
-
If it's not a launch issue, you can export the Log file and Backup Config file to the local network.
-
For Omada Controller v5.8 or later version,
In the Global View, go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. On the same page, scroll down to Export for Support, then click Export Running Logs to download the desensitized Log file.
-
For Omada Controller v5.6 or v5.7,
Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. On the same page, scroll down to Export for Support, then click Export Running Logs to download the desensitized Log file.
-
For Omada Controller v5.5 or a previous version,
Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. Go to Settings > Services > Export Data > Running Log to export the Log file.
-
Update Log
Apr 21st, 2026
Provide the following firmware:
OC200(UN)_V1_1.40.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V2_2.25.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V3_3.2.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V1_1.5.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V2_2.4.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC300(UN)_V1_1.34.15_pre-release (Built-in Omada SDN Controller 6.2.10)
OC400(UN)_V1_1.12.15_pre-release (Built-in Omada SDN Controller 6.2.10)
Update Note:
Fixed some known issues.
Apr 10th, 2026
Remove point 12&13 from the New Features section.
Apr 9th, 2026
Provide the following firmware:
OC200(UN)_V1_1.40.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V2_2.25.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC200(UN)_V3_3.2.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V1_1.5.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC220(UN)_V2_2.4.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC300(UN)_V1_1.34.11_pre-release (Built-in Omada SDN Controller 6.2.10)
OC400(UN)_V1_1.12.11_pre-release (Built-in Omada SDN Controller 6.2.10)
Recommended Threads
EAP7xx Fully Adapted to Omada 6.2 Pre-release Firmware (Released on 23rd Jan, 2026)
ER7206 V2 Pre-Release Firmware for SDN Controller 6.2.X.X (Released on February 12th, 2026)
ER707-M2 V1 Pre-Release Firmware for SDN Controller 6.2.X.X (Released on February 12th, 2026)
ER7406 V1 Pre-Release Firmware for SDN Controller 6.2.X.X (Released on February 12th, 2026)
Omada_Network_Application_V6.2.10.x Pre-Release Firmware (Updated on 3rd Apr, 2026)
Omada Switch Pre-Release FW Preview for SDN Controller 6.2.X.X (Update on Apr, 1st, 2026)
Wish you a happy life and smooth network usage! >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Vishlamba
Thanks for sharing.
Vishlamba wrote
@Vincent-TP Hi
Thanks for your reply I managed to solve the issue it was the puck switch and a tapo wifi camera thats was set to use tapo hub as a wifi fall back, I just removed the camera from the hub and the problem was solved. Thanks
- Copy Link
- Report Inappropriate Content
Thank you so much for the detailed info.
Does this issue persist? Did you upgrade the firmware successfully?
Please try to clear the cache of the web browser, or change the browser.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Thanks for the update, Installed the new upidate 6.2.10.15, all wokring fine for me, will soon update my OC200s and update soon. Thanks
- Copy Link
- Report Inappropriate Content
Hi, one old issue is back. Devices show offline when they are actually online. This was last faced in 5.xxx ver very long time back. And know seen in the latest beta. Noticed since last night. Has someone else faced this issue ?
ER7206
OC300
SG2824p
SG3428
- Copy Link
- Report Inappropriate Content
Hi @Vishlamba
Thanks for the feedback. To understand the situation better, please let us know:
1. How about the display on the controller's web interface? Are they also shown as offline?
2. Is this happening on all clients? Or are there still some clients showing as online?
3. What's the firmware version for the switches and EAPs? Is this happening both on wired and wireless clients?
Vishlamba wrote
Hi, one old issue is back. Devices show offline when they are actually online. This was last faced in 5.xxx ver very long time back. And know seen in the latest beta. Noticed since last night. Has someone else faced this issue ?
ER7206
OC300
SG2824p
SG3428
- Copy Link
- Report Inappropriate Content
@Vincent-TP Hi
Please me my answer:-
1. How about the display on the controller's web interface? Are they also shown as offline?: Yes they show offline in the web interface also.
2. Is this happening on all clients? Or are there still some clients showing as online? :- Its only happening to a few say 5 to 10. Rest all stay online.
3. What's the firmware version for the switches and EAPs? Is this happening both on wired and wireless clients? Attaching the complete list below, and yes it happens to both wired and wirless clients. Thanks
- Copy Link
- Report Inappropriate Content
Hello everyone,
Since the latest update (1.34.15) on my OC300, all sites have been offline.
The devices normally connect via routing to the static IP address of my OC300, which is managed by an ER7406.
All EAPs and routers at the various sites are offline.
BR Tim
EDIT: After I forwarded the DMZ via NAT, all the devices reappeared immediately. Could it be that there’s a new port again?
That’s really important to know!
- Copy Link
- Report Inappropriate Content
Hi @TW_EPC
Thanks for your feedback.
We don't add new port for this version. To find out the reason, I have created a support ticket for further follow-up, the case ID is TKID260453592.
Please check your email inbox. Thanks.
TW_EPC wrote
Hello everyone,
Since the latest update (1.34.15) on my OC300, all sites have been offline.
The devices normally connect via routing to the static IP address of my OC300, which is managed by an ER7406.
All EAPs and routers at the various sites are offline.
BR Tim
EDIT: After I forwarded the DMZ via NAT, all the devices reappeared immediately. Could it be that there’s a new port again?
That’s really important to know!
- Copy Link
- Report Inappropriate Content
The situation has taken a strange turn. After disabling and deleting the DMZ rule, all devices remained online.
It appears that the NAT rules were not correctly initialized or active after the update. Creating the new DMZ rule likely triggered a re-provisioning of the firewall's configuration, which re-applied the existing rules and states correctly.
Since everything is working now, I can no longer reproduce the issue. I described it that way in the ticket as well.
Vincent-TP wrote
Hi @TW_EPC
Thanks for your feedback.
We don't add new port for this version. To find out the reason, I have created a support ticket for further follow-up, the case ID is TKID260453592.
Please check your email inbox. Thanks.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2827
Replies: 30
Voters 0
No one has voted for it yet.