@Emitplink I am not sure as I received my router more than a month ago, I also had trouble with adopting the device.

What made it work for me is, If I am correct:

Factory reset the device then logged into the device, set a password and changed the ipadress of the device as my network is not 192.168.0.X. (but only those two things).

Changed the production router with the TL-R605 rebooted the device.and then tried to adopt the device in Omada (on prem). It took a couple of minutes before it came up.
 

Edit: spelling.

These steps occur when trying to adopt the router:

After entering the credentials, the adoption starts again in the same order as above (except for Pending).

Daniel

P.s. Chris, sorry that I misuse your thread for this problem right now...

So far, I didn't succeed to adopt the router to the Omada Controller (OC200). Everytime I try to adapt the router, it somehow returns to its default IP-address of 192.168.0.1. That's not the network range I configured in the Controller. The adoption terminates with an error, stating that the adoption has failed. So I used the reset button to set it to factory default and did some basic configuration using the Standalone Mode interface, so I have Internet access and all my devices receive an IP-address using the router's DHCP function. But this is of course not the way of configuring the router in a centrally managed environment.

@ChrisAT 

I have ordered a TL-R605 but have not received it yet, but I see there is a LAN interface that it is not possible to edit. I'm guessing that this interface overrides when the TL-R605 adopts. this is probably a bug but probably creates big problems for us with another ip network. when I get my TL-R605 I will create an interface with ip 192.168.0.2/24 on my existing firewall and create a route to my omada controller from this network and then change when the router is adopted in the controller.

This is a bit of a guess because as I said I do not have a TL-R605 myself yet :-)

Have the same issue...adoption fails over and over again. The closest I got was with the following setting and steps

Context: 

Network 192.168.1.x, with active router Archer 1200 v2

Omada Controller v4.1.5 (on MS Hypr-V)

With 4 AP's connected & working

TL-R605

Connected to above 192.168.1.x LAN Network (port5)

Out of the box : ipadress=192.168.0.1 (no user,nopassword)

Laptop connected to port4 (192.168.0.x address)

created user/pasw (-> afterwards used duringthe adoption process, after failing the first time).

Changed the TL-R605 to 192.168.1.x and DHCP server disabled

Enabled Cloude-Based Controller management

Added controller inform ipaddress 192.168.1.x

Started the adoption process: adopting -> Provisioning -> Configuring -> Adopting -> Adopt Failed 

Somewhere between provisioning and configuring the IP-address changed back to 192.168.0.1

(including user/pasword) and therefor the adoption fails again.

Shame ...

@XC90 That's about the same what happens here. 

Last night I was 'clicking around' through the router's web management page. I noticed that the time and time zone were incorrect. Timezone was set to -8, but I live in timezone +1. So I changed that. And saved the router's config to a back-up file.I hoped the time zone might be of any influence on the failing adoption process. So tested it this morning. But before I started to adopt the router, I opened a DOS box and ran a continuous ping to the router (ping -t 192.168.36.2, which is the current IP address for the router in my network). Like you said, somewhere in the adoption process the ping showed packed loss.

After that, connected my laptop to the router, started it. The router's LAN IP was reset to 192.168.0.1, which is factory default. My admin credentials were erased as well. So I had to use the reset button to restore the factory settings. After that, I was able to create new admin credentials again. Did so and restored the config using the back-up file.

Daniel

@ChrisAT Strange things happen, but everutyhng has it's own logic ... I managed to get it connected and using the correct IP-address (192.168.1.x).

As often with fiddling around it's difficult to backtrace my steps to know what fixed it. In my case I noticed that there was a continous ping on 192.168.0.1, even with the TL-R605 powered-off. Obviously as my old router was using that exact same address. Powered off that one and restarted the TLR605. At that moment strange things started to happen ... suddenly the TL-R605 was listed with ipaddress 192.168.1.x , adoptation started and finished with the device having ip-address 192.168.0.1, Status: connected and ... manageable! NOTE that the old router is still powered-off! - Very important. 

Through the omada controller I changed the IPaddress to 192.168.1.x et voila , also disalbed the dhcp-server function, done. Suddenly all devices in the omada controller started to disconnect, adopt process ... after a short period of slight panic , I realized several devices couldn't get an ipaddress and also impacting the hyperv setup. Powered-up my old router as I have to migrate reservations etc. Everything stabilized, problem solved.  and hopefully it stays that way.

@Fae 

Why is edit of lan interface disabled before adoption? if controller have 192.168.30.2 and router get 192.168.0.1 after adopt the router wil lose connection to controller.

whay not enable edit of lan interface before adopt?

@shberge Default LAN IP of R605 is 192.168.0.1, you cannot change it until the router is adopted. The discovery process is done with Layer-2 communication, but the adoption process must be done with Layer-3 communication.

For example, if Controller PC has an IP address as 192.168.0.2, it will know that the router is directly connected, both L2 and L3 communication is working well.

If controller PC has an IP as 192.168.30.2, in the different subnet as 192.168.0.1, though controller will find a router with L2 broadcast, but it cannot directly communicate with the router, there must be a meaningful route, that is the default gateway of controller have route to communicate with the router.