@t3knoid 

It would be better to publish this on our Business Product community.  The customer base and official reps that managed that community are far better equipped to help you with a concern like this than we are.  You can post on https://community.tp-link.com/en/business/forum/1

  @t3knoid I am trying to figure this very same thing out with an EAP655

  @d0ugmac1 I've reset the box several times. I can only see the unit in Omada if I look in standalone mode. It never shows up otherwise.

d0ugmac1 wrote

  @t3knoid 

 

Absolutely.  I have EAP615-walls under controller management.  You'll probably need to default them before the controller will offer to adopt thought.

  @d0ugmac1 

I "defaulted" as suggested in that video...several times. I can see that the box is reset to default each time. Quite frankly, I didn't see a difference with using the hard reset or soft reset. I am using the latest version of the controller:

Version:5.12.9
Build:1.26.3 Build 20230906 Rel.36269

I also tried enabling the following. I made sure that the inform URL is set to the controller IP and that the omadacId value matches the one that my controller's. 

None of these helped. 

  @d0ugmac1 The only reason I mentioned it is because I am unable to configure out of the box. So basically I am grasping at straws at this point. 

My network is a typical home network (e.g. 192.168.0.x). I am not using any fancy networking at this point. I tried using a soft Omada Controller and also using my OC200. Also note that I have adopted other Omada devices on my network. The last one that I adopted was a EAP235-WALL (very similar to the EAP615-WALL).

d0ugmac1 wrote

  @t3knoid 

 

There is something missing from this story.. 

 

If you unplug your working, managed 235wall and plug the freshly defaulted 615wall to that same cable does it:

 

1. Show as a Client with IP assigned

2. Show as Adopt in the controller Devices

 

If the 615wall has an Ip can you reach the eap login screen with a browser?

 

 

  @d0ugmac1 

I unplugged the EAP235-WALL and replacedwith the the defaulted EAP615-WALL. There is no change in behavior. The EAP615 only shows up in standlone. It does not show up in the controller to be adopted. As I mentioned previously, the EAP615 has no issues as standalone. I am able to login to its GUI and configure it (with browser and with Omada mobile app).

I went further than this. I have another EAP615-WALL, unopened. I plugged it into the switch in the same manner as I did the other. It doesnt show up in the controller. I can get to its GUI and configure it as a standalone access point. 

I dont think there is anything on my set up that is out of the ordinary. I've obviously managed to connect other Omada devices into the controller. Not sure why these EAP615's arent being recognized.