All the firmwares on Omada support download page seem to be older that the ones on the device or what i have updated from controller.

It seems that these older devices without Device Keys are going to need to be returned :/ unless someone has any suggestions?

@Vincent-TP i wonder if you could assist with this?

icepicknz wrote

Hi,

 

I have built a solution where i was expecting customers to adopt by device key (layer3) and this has worked well when stock has been new; but some devices appear to be missing the device key both EAP115 and 225

 

I have tried to get customers to set the infom IP manually but im not seeing any pending devices.

I tried this myself with some EAP115's, i ordered 5 and 1 had a device key and 4 did not.

 

I managed to build a layer2 trunk back to my test lab, adopt and upgrade the devices, then factory reset them and try go to SYSTEM >> Controller Settings and adding the L3 IP of the server. I even tried to open the controller fully to the internet all ports and still not adopting.

 

normally i just have ports TCP 8043,8088,29810-29814 and UDP 29815 

 

Any thoughts or assistance?

My test EAP115 is

5.0.9 Build 20240228 Rel. 53359(4555) 

Hardware version 4.0 (though label on the device says 4.2)

 

Omada controller is 5.15.24.19

 

Many thanks

  @icepicknz 

the ports you need to open are UDP 29810 and TCP 29811-29817

  @MR.S thanks, as per original post these ports are open, but for safe sake, i have just opened the range on UDP, so

TCP 8043,8088,29810-29814

UDP 29810-29815

I've also tried allowing * but makes no difference

  @Vincent-TP my build is 5.0.9 Build 20240228 Rel. 53359(4555)  which was updated from the controller (when controller was on same lan), then I factory reset and attempted to reconnect over layer3. 
 

tplink website is all old firmware's?

  @Vincent-TP thanks. So could you advise what load to use for eap115 and eap225 by providing a link, they are both hardware v4.2 as the tp link website shows me firmware from 2022

youe comment about the firmware did that relate to the controller updates being out of date?