Here are some screenshots:

https://www.dropbox.com/scl/fi/qloofqkq8lnamjkryea6o/Omada.paper?dl=0&rlkey=50nlzqjyoh66fds62ba6eo4zn

  @FlashWeave 

Do you run in a docker? you need to open TCP 29814 or if you have controller in another VLAN or port NATed in to controller from remote site

they have change two ports without it being documented very well.
TCP 29814 for adoption
Software controller TCP 8043 and TCP 443 OC200 / OC300 For firmware update

  @shberge yes, I use https://github.com/mbentley/docker-omada-controller

It exposes port 29814: https://github.com/mbentley/docker-omada-controller/blob/master/Dockerfile.v5.3.x

  @FlashWeave 

Ok, try to telnet from windows command prompt from network where the device is, use this command 

telnet ip to controller 29814 eg. telnet 192.168.1.2 29814

if there answer on this port all ok

  @shberge thank you for trying to help me.  This is my result: the test succeeded: https://www.dropbox.com/s/35udiil8m42m7nc/rJZzIYOSXA.png?dl=0

  @FlashWeave 

Ok, and you still have problem with adoption?

  @shberge yes, the exact same 2 devices are still "provisioning" or "adopting" all the time. 

  @FlashWeave 

Strange!! And your controller ip is 192.168.0.101?

Yes 192.168.0.101 is the IP adress of the physical device the Omada controller is on (=a Raspberry Pi).