Topology (nothing non-omada involved):

1. Omada Software Controller: 5.14.30.7 
2. Router (including DHCP Server): ER707-M2 v1.0 running 1.2.2 Build 20240324 Rel.42799
3. Switch 1: SG2008P v3.20 running 3.20.1 Build 20240115 Rel.72847
4. Switch 2: SG2005P-PD v1.0 running 1.0.3 Build 20240807 Rel.60731
5. EAP: EAP683 LR(US) v1.0 running 1.1.0 Build 20240412 Rel. 59256 (replaced EAP653(US) v1.0 running 1.0.14 Build 20240415 Rel. 70264)

After swapping out an EAP653 for an EAP683-LR, the Clients view shows most wireless clients now as wired with no stats (even if the client was not involved with either EAP). This seemingly simple swap seems to have caused a bunch of errors in topology understanding for Omada...

I've posted about similar issues with this and the map previously, but wanted to separate this out, as the "solution" recommended to test previously has been a specific sequence of rebooting all omada hardware that would incur non-trivial downtime... If I cannot "hot swap" something as simple as an EAP without fully rebooting the system in order to view wireless stats (e.g. see how that new EAP is doing for previously weak clients) there must be something seriously wrong - so this topic is focused on other ways to get Omada SDN to recognize dozens (>50) wirless devices as actually wireless, making their wireless stats available - without causing a major full-network outage.