Scheduling AI WLAN Optimization in Omada SDN – Possible Workarounds?

Scheduling AI WLAN Optimization in Omada SDN – Possible Workarounds?

Scheduling AI WLAN Optimization in Omada SDN – Possible Workarounds?
Scheduling AI WLAN Optimization in Omada SDN – Possible Workarounds?
a week ago - last edited 11 hours ago
Model: EAP773  
Hardware Version: V1
Firmware Version: 1.0.13 Build 20240417 Rel. 57733

Issue

The Omada SDN management interface currently lacks an option to schedule AI WLAN Optimization, requiring it to be triggered manually. I’m looking for a way to automate this process to ensure regular Wi-Fi optimization without manual intervention.

 

Potential Workarounds I’m Researching

  1. Omada API (If Available)

    • Does the Omada API provide an endpoint to trigger AI WLAN Optimization?
    • If so, has anyone successfully automated this using cron jobs, Python scripts, or Task Scheduler?
  2. Browser Automation (Selenium or Similar)

    • Has anyone used Selenium or Puppeteer to script logging into the Omada web interface and clicking the AI WLAN Optimization button?
    • Are there any known UI elements that change and break this automation?
  3. SSH/CLI Commands (If Available)

    • Does the OC200 controller allow SSH access to execute commands for AI WLAN Optimization?
    • If so, what commands or scripts can be used to trigger it?
  4. Webhooks or External Automation (Home Assistant, Node-RED, Zapier)

    • Has anyone integrated Omada SDN with Home Assistant or Node-RED to automate WLAN Optimization?
    • Are there any webhooks or API endpoints that can be leveraged for this?
  5. Rebooting the Controller as a Workaround

    • In the absence of direct automation, does restarting the OC200 Cloud Controller trigger an AI WLAN Optimization automatically?
    • Has anyone tested if rebooting the EAP access points forces an AI optimization?

 

Equipment & Firmware Details

I’m currently managing a TP-Link Omada SDN network with the following hardware and firmware versions:

 

  • Omada Cloud Controller: OC200, Model v2.0, Firmware 2.19.2 Build 20250110 Rel.75724
  • Omada Gateway: ER605, Model v2.0, Firmware 2.2.6 Build 20240718 Rel.82712
  • Omada 8-port PoE Switch: SG2008P, Model v3.20, Firmware 3.20.4 Build 20241205 Rel.64944
  • Omada 8-port Switch: SG2008, Model v4.20, Firmware 4.20.4 Build 20241205 Rel.64944
  • Omada Wi-Fi 6 WAPs:
    • EAP670, Model v1.0, Firmware 1.1.0 Build 20240412 Rel.59256
    • EAP683 LR, Model v1.0, Firmware 1.1.0 Build 20240412 Rel.59256
  • Omada Wi-Fi 7 WAP:
    • EAP773, Model v1.0, Firmware 1.0.13 Build 20240417 Rel.57733

 

Final Thoughts

If anyone has successfully scheduled AI WLAN Optimization using any of these or other methods, I’d appreciate any guidance, scripts, or step-by-step instructions! Also, if this feature is on TP-Link’s roadmap, any insights into future firmware support would be helpful.

 

Thanks in advance!

 

Veiðimaður

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Scheduling AI WLAN Optimization in Omada SDN – Possible Workarounds?-Solution
a week ago - last edited 11 hours ago

  @Veidimadur 

 

Hello,

 

In COntroller's version 5.15.8.2 I have found such info:

 

So it looks like the Scheduled Optimization has been disabled for now due to it's inefficiency. Looks like once they fix it, they will bring it back. I don't know when tho...

 

I guess we have to wait for now. Haven't seen this feature being mentioned in 5.15.20 release so it may take a little bit more time.

 

Cheers

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:Scheduling AI WLAN Optimization in Omada SDN – Possible Workarounds?-Solution
a week ago - last edited 11 hours ago

  @Veidimadur 

 

Hello,

 

In COntroller's version 5.15.8.2 I have found such info:

 

So it looks like the Scheduled Optimization has been disabled for now due to it's inefficiency. Looks like once they fix it, they will bring it back. I don't know when tho...

 

I guess we have to wait for now. Haven't seen this feature being mentioned in 5.15.20 release so it may take a little bit more time.

 

Cheers

Recommended Solution
  0  
  0  
#2
Options