Continuing the discussion from TPLink Omada SDN new API offered:
Hi @TravisHolland and @PecosKidd,
I noticed that you both mentioned using an OC200 hardware controller, so I’m hoping you might be able to help with some testing.
I recently contributed a new Omada Controller device and firmware update entity to the official Home Assistant TP-Link Omada integration, and it has just been released in Home Assistant 2026.10.0b0.
I’ve tested the actual beta release with my Software Controller, and everything is working as expected.
What I haven’t been able to test yet is the hardware controller path — OC200, OC220 or OC300. In particular, I’d like to confirm that:
- the Omada Controller is correctly created as a device;
- the controller status is reported correctly;
- available firmware updates are detected correctly;
- and, most importantly, the firmware Install action is available and behaves correctly on hardware controllers.
If either of you still has an OC200 and would be willing to test Home Assistant 2026.10 beta, even screenshots of the Controller device page and the firmware update dialog would be extremely helpful.
Of course, if your Controller is already running the latest firmware, the update/install part of the test won’t be visible. But it would still be very helpful to confirm that the Controller device is created with the proper name and that its status, firmware version and device information are displayed correctly.
And of course, if anyone else here has an OC200, OC220 or OC300, I’d really appreciate your help testing it as well.
Also, if there is a newer or more appropriate place in the Home Assistant Community for discussing development and testing of the native Omada integration, please let me know and I’ll be happy to continue the discussion there.
Thanks!
Rubem (@rubempoli on GitHub)