Hi all,

For various reasons my Omada controller is running in a container on a computer connected via Wifi, I know it's not an ideal situation but until the cabling situation is sorted it is what it is.

It's a very basic setup with a simple stupid non-Omada switch/router, software Omada Controller (v6.2 now) and a couple of EAPs. Everything on a single network.

This all worked brilliantly as long as it was connected to an old EAP225 AP (v3 ver 5.2.3).  Plugging in a new device in the network worked fine, just wait until the device showed in the Omada controller device list and adopt it.

However, when changing the AP serving the controller computer to an EAP653 (v1 ver 1.3.7) new devices suddenly doesn't show up in the device list. Old devices are still managed OK, I have connectivity to the new device (I can ping it and access it's web interface) but it simply doesn't show up in the device list allowing me to click adopt!

Changing the AP back to the EAP225 it shows up and can be adopted fine.

Do any of you know if this might be  due to some setting I've done in my Omada WLAN setup that only takes effect with newer EAPs, or some hidden security feature in the newer EAPs to avoid having rogue Wifi clients adopting devices?

I'd really prefer not having to use the old EAP until I've got the cabling situation sorted, so if there's a setting for this I'd be happy to know about it.