Device adoption failed because the device does not respond to adopt commands.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Device adoption failed because the device does not respond to adopt commands.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Device adoption failed because the device does not respond to adopt commands.
Device adoption failed because the device does not respond to adopt commands.
2024-02-25 16:13:28
Hardware Version:
Firmware Version: 5.13.23

Hi,
I have a problem as in the title. 

 

Unfortunately the options in this link do not help: https://community.tp-link.com/en/business/forum/topic/260170

 

I have an ER707-M2 router and a controller on Docker version 5.13.23.

 

They are on the same subnet.

  0      
  0      
#1
Options
2 Reply
Re:Device adoption failed because the device does not respond to adopt commands.
2024-02-26 03:11:04
Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:Device adoption failed because the device does not respond to adopt commands.
2024-02-26 16:10:10

  @Jan_NET 

 

Alternatively, change your container network to 'host' instead of bridge, spin up a new container and retry.  If that works, you had issues with publishing all the needed ports in your previous docker compose or run file.  Are you using mbentley's docker image?

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#3
Options