Cannot move EAP245 access point to site after adoption
After having manged my three EAP245 access points using the Omada software controller for a year I finally decided to purchase a OC200 hardware controller. However, I am having trouble moving the access points from the software controller to the hardware controller.
I am "forgetting" the access point on the software controller, and then "adopting" it on the hardware controller. That much works, but there is a red "i" in a circle next to my device name in the list that says "This device is not compatible with the current controller. To manage the device, update the device first." when you hover over it. When I try to move it to my default site it fails with the message "[Failed]Cloud Main-Administrator dlherrin@xxxx.com failed to move 50-D4-F7-9C-29-00 to Site POP Campus."
Can anyone please tell me what is going on and how to fix it? (I do not think my EAP245s are really incompatible with the OC200 controller.)
My list of equipment is as follows:
• TP-Link OC200 v1.6 (firmware 1.8.0 Build 20210406 Rel.58757)
• TP-Link EAP245 v3.8 (firmware 2.4.0 Build 20200117 Rel. 39932)
• TP-Link TL-SG1005P v1.8 (5-port Gigabit Desktope Switch)
Many thanks!
Dave