@Virgo 

I left all access points active at the beginning until I had the right positions and frequencies. Then I set up the POE schedule and the first day as a result already had this problem. A reboot of the switch and physical disconnect / reconnect fixed it, then the status is correct.

For readjustment just select any time window for the POE schedule, looks like this:

If this is rather untypical behavior, could the switch possibly have a defect or more the network cable?

I changed the switch port and recreate the POE schedule without success.

Don't see any problems on the interface ...

Is there a way to get the same information on the AP EAP610 by commandline?

This is very annoying, it works sometimes 3 days then again not.
It happens now that it does not activate the port at all.
The event is then "PoE schedule WLAN_OG_WEEK executed on 0 ports of 1 switches."

But I can't find any error in the log, it looks like it should:

No one has an idea what this can be?

  @Virgo 

Virgo wrote

  @4Bob 

 

As I known, you can not use CLI to login the EAP.

I am confused by your post, sure you can ssh to eap's, if managed by omada, you have to use credentials set in omada which are the same for all devices.

When you login, its quite a mess, if your bins do not work, use busybox for it, There are also missing folders like proc which results in few applications not working, like system monitor. At least iperf and few other commands work, use help and busybox help for further info.

More than that is possible, you can copy any binary to ram and run it, but be aware that bins are gone after reboot and if you need it, you have to run a script which recognizes reboots and restores binaries/settings in ram on device's boot. You can also run curl and other nice apllications which tplink refuses to add as feature to omada. 

@mbentley

Can this problem come from using your docker image?
Maybe I did something wrong with the docker cli:

docker run -d  --name omada-controller --restart always -e TZ=Europe/Berlin
-p 127.0.0.1:8088:8088             
-p 127.0.0.1:8843:8843             
-p 8043:8043                      
-p 29811:29811                     
-p 29812:29812                     
-p 29813:29813                     
-p 29814:29814                     
-p 29810:29810/udp                 
-e MANAGE_HTTP_PORT=8088           
-e MANAGE_HTTPS_PORT=8043          
-e PORTAL_HTTP_PORT=8088           
-e PORTAL_HTTPS_PORT=8843          
-e SHOW_SERVER_LOGS=true           
-e SHOW_MONGODB_LOGS=false         
-e PGID="508"                      
-e PUID="508"                      
-e SSL_CERT_NAME="fullchain.pem"       
-e SSL_KEY_NAME="privkey.pem"          
-v /data/omada-cert/domain:/cert             
-v /data/omada-data:/opt/tplink/EAPController/data     
-v /data/omada-logs:/opt/tplink/EAPController/logs     
-v /data/omada-dbdump:/dbdump                          
mbentley/omada-controller