This Article Applies to

 

OC200(UN)_V1_1.41.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC200(UN)_V2_2.26.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC200(UN)_V3_3.3.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC220(UN)_V1_1.6.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC220(UN)_V2_2.5.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC300(UN)_V1_1.35.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC400(UN)_V1_1.13.6_pre-release (Built-in Omada SDN Controller 6.2.14)

 

Overview

 

We hope to offer you the opportunity to experience the new features added in Controller vv6.2.14.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 or above.

 

Supported Device Models

For device models Omada Software Controller supports, refer to the Omada Cloud SDN Platform Compatibility List.

 

New Features

 

There are no new feature updates compared to Omada Software Controller v6.2.10.

 

Enhancements

 

1. Optimized device authentication and security mechanisms, introduced device-level digital certificates (DAC) and a more secure authentication process (SPAKE2+), and enhanced the security and trustworthiness of device adoption. (Requires firmware support)
2. Optimized Label functionality, which supports adding labels to name the Gateway port under the Site view > Device List > Gateway > Manage Device > Ports.

 

Notes

 

1. 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.
2. The Omada SDN Controller can only manage specific devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
3. Since version 5.14.32, the Omada Software Controller no longer supports upgrading from Controller v4.
4. 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.41.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC200(UN)_V2_2.26.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC200(UN)_V3_3.3.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC220(UN)_V1_1.6.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC220(UN)_V2_2.5.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC300(UN)_V1_1.35.6_pre-release (Built-in Omada SDN Controller 6.2.14)

OC400(UN)_V1_1.13.6_pre-release (Built-in Omada SDN Controller 6.2.14)

 

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

 

June 18th, 2026

Release of this article.

 

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.14.x Pre-Release Firmware (Released on 18th June, 2026)