@R1D2 - hi just checked your link, will double check in the morning and repost.. I will see if my OC-200 hardware controller software is the issue, as I did update its firmware cleanly.along with the EAPs no issue there. I am 99% sure I updated both the OC-200 firmware, directly after the EAP-225 outdoor.  Are all in the "compatible" hardware list for the SDN anyway, so that's not really an out for "disappearing client list bug".

MY current OC-200 says = 

Cloud Controller Firmware

Current Version:

1.2.3 Build 20200430 Rel.52621"

=

@R1D2 - oh I was editing my reply posted my updated firmware version above...

But basically, I can't upgrade my EAP's to the SDN build (1.20.0)  - which my Ring.com cameras performed noticeably better on.. latency wise in "rapid ring" app for pulling up cams - until there's an upgrade for the OC200 controller firmware - to get it on the SDN?  So there won't be any interim build (I made up build 19 example) that is pre-SDN but has most of the performance fixes up to build 20, later than build 7?

So, that's why the AP's work a bit better on build 20, but I lose visibility of their clients/userson OC-200, until I rolled back the firmware on the EAPs?  Wierdly, I can still see, control, reboot, up/downgrade them via OC200 just fine even with build 20.  Well I lose the "channel" information of the links too, aside from users.

@R1D2 do you know when approximately OC-200 will get the SDN enabled firmware update so I can keep it lock step with EAP firmware update to SDN?

Seems like these should have been released together.  That would be like Ubiquiti UniFi updating theri mesh access points, but blinding their "cloudkey controller" from seeing mesh points, which is similar product line and concept (sure TP link mesh is based on UniFi, it seems very similar).

In fact, I run both OC-200 controller with TP link mesh for HOA + Ubiquiti cloudkey controller and their Unifi mesh for my house network, to keep them separated to my EdgeRouter/firewall.

Anyway want to get my Ring.com cams with the 1.20.0 build ASAP, they work much better lag time wise than 1.7.0.  just need them to release the OC-200 update for SDN it seems..  argh.

@R1D2 - okay that's handy - will give it a shot tonight after getthe kiddos to sleep.  upgrade OC200 and EAP-225 network to new SDN.

@R1D2 - should retitle the thread "Major FIX" for Ring.com security cameras, Access point mesh-performance (load-balance, latency) all improved BIG TIME.

Now that OC-200 and EAP-225 are all updated to SDN and latest firmware builds - all my HOA's Ring.com security cameras are a.) on the access point that makes the most sense b.) lower latency and faster pull up speed on "Rapid ring" app = way improved.

I upgraded the EAP-225's first wired/wireless ones, then the OC-200 controller after. 

However, I tried it the other way for one EAP, and I could upgrade the OC-200 and then the EAP-225 (even those in wireless mode).  I have 5x of these EAP's "hardwired" via Ubiquiti Nanostation "bridge" connections (around my HOA detached garage perimeter, with hub-spoke D-ring perimeter) that are stable PtMTP virtual ethernet links and appear as such in my Edgerouter/firewall.  Upgrading those EAPs was easy as they show as "hardwired" like a regular ethernet connected one, but the wireless-mode ones also came online, after upgrade/reprovision.  Nice - so, so glad they didn't get "isolated".

This is what I experienced, major Ring.com cams performance improvement, in previous build 1.7.0 they would even choose wrong access points that didn't always make sense based signal/distance.  Now EAPs with 1.20.0 build the ring.com cams connect to the APs that make the most sense.. very nice.

So for anyone looking for a Ubiquiti Unifi alternative, as of the SDN upgrade and performance boost I'm seeing across my security camera system - Tp Link Omada is viable 2/3 cost alternative to Unifi from Ubiquiti.

If Omada firmware/SDN  continues to improve, I'll move more systems over in time.  Also, its clear the upgraded app is a Unifi clone, but ir's pretty good :).