[Help]: TP-Link ER605 v2.20 router does not adapt after ip change

[djwujek123]

Controller Version

5.15.20.12

Describe Your Issue or Question

Hello.

I have a problem with adapting the Tp-Link ER605 v2.20 router.

The situation is as follows.

The router on standard settings, i.e. 192.168.0.1/24, normally adapts and connects to the controller, but after changing the IP to any other and restarting the entire docker and the controller (the IP changes to the new network), the controller remains in the adopting status.

Expected Behavior

Please help me solve the problem

Steps to Reproduce

.

How You're Launching the Container

.

Container Logs

.

MongoDB Logs

No response

Additional Context

No response

[mbentley]

When you're saying "changing the IP to any other", are you talking about changing subnets? I'm assuming so because your screenshot shows 192.168.6.1. I'm assuming the problem is that the controller, which is now on an "orphaned" 192.168.0.1/24 subnet can't find the router on 192.168.6.1/24.

[mbentley]

Here is a forum post that talks about how to change the subnet: https://community.tp-link.com/en/business/forum/topic/245232

They posted a workaround that apparently worked for this person:

----------------------- update found a workaround to enable adoption -------------------------

So after a day or so of failed adoptions and trying different things I've managed to at last get the router adopted by Omada and on the subnet I want it to be on not the default. Hope this helps someone else:

1. Reset the router to factory, login and set password and user name, go into the router and set the controller settings to the URL of the controller I also enabled cloud control (not sure if that's needed though)

2. On the Host of the Omada controller - I disabled any services running high bandwidth services e.g. blue iris for CCTV, I also temporarily disabled the firewall,

3. on the host of the Omada controller change the IP address to something on the 192.168.0.1 address range and point the gateway to 192.168.0.1

4. Bring up the Omada and once the router is available click adopt and enter password and username... at this point you'll know if its going to work as it starts provisioning quite quickly.

5. Once provisioned and connected go into the Omada controller and select the router - on the right hand side navigate to the config menu/common settings.. settings/wired networks/LAN - edit the LAN address and change it to the address you want on your controllers original IP range (Mine is 192.168.1.x)

6. On the Host of the Omada software - reverse the IP address change you made on step 3

7. The Omada controller should now adopt all of your devices again including the router...