@wuppi 

Hey

The controller is designed to be online 24/7 and therefore after a reboot the APs will be re-adopted.  This will result in the APs wiping their current configuration and pulling a fresh new version from the controller and results in downtime on the AP during this re-configuration.

This is not specific to Omada or TP Link, other vendor solutions also do this also.   Ideally the controller should be left online perminantly, it might be worth considering an OC200 controller if the device you are using for the controller is not dedicated to this task (a home PC or desktop for example).

@Philbert 

I assumed something like this - however it is a server which is online 24/7. But every server needs an update / reboot once in a while and I wondered if the WiFi-status should be tied to this. 

But thank you for the quick response. From my point of view, there should be a way to "re-connect" the controller without "resetting" the AP. Btw, does this happen to Omada managed switches / gateways / routers too?? 

br,

Andre

@wuppi 

Usually, if you just configure basic wireless settings, you don't need to keep running the controller. I have the whole set of Omada devices(gateway, switch and EAP), I don't have this issue. Do you also have the Omada gateway?

But I try to configure mesh before, if I shut down the controller, mesh AP won't reconnect if it disconnects from the root AP.