@Dillius I have a hack for this which I posted on a different thread too:

@Dillius 

i just experiencing same problem, restore complete SDN network (really su**)

set local IP of your R605 as same range of your OC-200 or any controller

set same password as your controller

do adopt => working fine (take a while)

=============

FYI: if as me, you backup complete controller (OC-200)  before reset all devices,

it just recover your neworks, device must be re-adopt because "managed by other" state
all ip settings are lost,
all device name are lost
fixed IP are lost,

static routes are lost (i have dual wan)
switch vlan settings are lost
wan settings are lost
NAT settings are lost

i'm really angry
 

@Jeanphi_blc Yea I think the trick really is you can start to configure Wired Networks after you have begun the process of adding the TL-R605 but before it is finished being added. So you have to make sure it all matches up even before it is fully adopted.

@Dillius what I did to adopt the tl-605 was to set the controller ip to 192.168.0.x the same subnet when you newly install tl-r605. it adopts well then you can change the ip from there. I hope they  make an update to fix this

@Dillius 

This is a serious problem. I can't edit the default 192.168.0.1/24 of the controller depite me having OC200 and AP's working on a different subnet 172.16.127.1/24.

Not being able to edit the controller IP is a big let down, and to be frank a rookie mistake for TP-Link. Hopefully they will fix this soon in firmware to allo option to edit the default VLAN.

I cant adopt my router either, and it is really becoming extremely frustrating, and to see trying for 2 hours until it works as recommended solution is taking the **** out of me...

Dillius wrote

Finally got my TL-R605, but my Omada controller fails to adopt every time I try.

 

I have tried powering off/on, resetting, a multitude of things, but it always simply says it failed to respond to adoption commands. It always does this the first time immediately, but then prompts me for a user/pass the second time, then fails again and again regardless. I can log into it directly with no issues, and configure it with no issues.

 

Also it frequently isn't even detected by my local Omada Controller... and I have to go through a cycle of resets before it shows up again, only to fail again.

 

Any suggestions?

@pcsurgeon Yea I had to start over from scratch over and over until I could just get everything to work out.

There is a new FAQ stickied that is supposed to help, but I think long term they really should just allow for LAN to be configured even without a gateway detected so everything can be pre-staged before adopting the Gateway.

Workaround (and save yourself hours of troubleshooting):

Configure using the default standalone method (eg. Laptop/PC/Mac on autodiscover IP connecting it to the LANPort of the Router).

Then go to LAN settings and configure the IP address of the router. Router will reboot - then release > renew IP adres (or reboot PC)

Reconnect Router to Omada infrastructure and try adopting it...

Well that did not succeed either.

So I will probably dump this and stick to my original gateway and send this one packing