See also attached images with the current status:
We do a weekly scheduled reboot of all Omada devices.
After the reboot of last night the router ends with the status "pending".
After a click on pending, the adoption process starts.
Shortly after, this stops with an error message stating that the username/password is not correct.
If I click retry and enter the (correct!) username and password, the adoption then ends with the error stating that the device is not compatible with the controller.
The controller is the Linux software edition 4.4.6 => tried re-installing the controller => no improvements.
Noticed several Java exceptions in the server.log (located in folder /opt/tplink/EAPController/logs).
Also tried rebooting the router and the controller a few times => no improvements.
Username and password is validated by logging into the router itself.
The router states it is not(!) connected to the TP-Link cloud.
Within the router, the cloud switch is turned off and the url-field below is empty.
Turning this switch to on and providing the URL doesn't make it any better.
The Internet connection and all applications (on-prem and cloud) are working as expected.
Meaning the router seems to be processing traffic? And this more like a cosmetic glitch in the portal?
Please advise - where to go from here?
Kind regards - Will