@Migo 

 

Hey Migo

 

Below (at bottom) is the list of the supported devices for V4 of the SDN

 

Looking at your list

EAP245(EU) 2x V1.0 - Dont think its supported in v4

EAP245(EU) 2x V3.0  -  If running firmware 2.20 or higher OK

EAP225(EU) 1x V3.0 - Mesh - EAP225-Outdoor(EU) 1x V1.0   -  Update the Firmware.. should be OK

 

Check the list yourself, but looks all except the 245 v1 is compatible after firmware updates.

 

--------------

EAP110_V4 3.20.0 Build 20200525 Rel. 36899 and above
EAP115_V4 3.20.0 Build 20200525 Rel.36931 and above
EAP225_V3 2.20.0 Build 20200422 Rel. 70513 and above
EAP245_V3 2.20.0 Build 20200423 Rel. 36779 and above
EAP115-Wall_V1 1.20.0 Build 20200509 Rel. 63986 and above
EAP225-Wall_V2 1.20.0 Build 20200422 Rel. 70504 and above
EAP110-Outdoor_V3 3.20.0 Build 20200511 Rel. 33388 and above
EAP225-Outdoor_V1 1.20.0 Build 20200422 Rel. 70543 and above
EAP265 HD_V1, EAP230-Wall_V1, EAP235-Wall_V1, EAP660 HD_V1, EAP620 HD_V1

 

https://www.tp-link.com/uk/support/download/omada-software-controller/#Controller_Software

@Migo im running Omada Software Controller V4.2.8 and can confirm that my EAP225 V3 (EU) devices are not compatible.

 

You will be presented with the following alert after adopting the device, "This device is not compatible with the current Controller. To manage the device, update the device first."

 

cheers,

@JRtech 

 

The EAP225 V3 is compatible. You have to update the firmware on the EAP to the latest firmware first. 

 

Then the controller will be able to adopt it.

 

I had to do this with 2 EAP245s and an EAP225 Outdoor, that I installed, before they could be adopted by the controller.

@rjow2021 Thanks man

 

I was pointed to this firmware version by another forum member, will give it a try over the weekend when im on site and provide feedback.

 

EAP225(EU)_V3_5.0.0.zip

 

Cheers!

@rjow2021 

 

Flashed the firmware this morning, worked like a charm! Thanks so much for your support!

 

Have a good weekend!

 

Cheers

@Migo 

after upgrading to v4, I was not able to adopt EAP (password problem) then I tried to change the site name and reload my config, and now I am happy !

@Philbert I am not out to "shoot the messenger", but this is INFURIATING! And not mentioned anywhere in the manual.

 

TP-Link should support ALL versions of Access Point hardware AND software on the latest controller release. If not, then provide software updates for the hardware back to V1. After all, they are 802.11ac!

 

I do not expect TP-Link to support .11b, or g, or maybe even n, but they should support all .11ac products.

 

I am trying to set up a SMB (Small to Medium Sized Business) office for a non-profit on 2 VLANs and two SSIDs, one for the staff & one for a large number of guests. For that I need a controller. Already have 2 Class C RFC-1918 LANs.

 

Was planning to start with two EAP620s plus 5 older TP-Link APs, and upgrade as finances permit. But the older APs I bought off eBay will NOT work with the controller & thus no VLANs.

 

As Harry Truman would say, this is Horse Manure.

 

TP-Link equipment is great for Home use, and possibly very small businesses, but it is, imo, NOT for SMBs.

 

Yes, I could reconfigure the LAN to a single Class B & use Guest mode on the APs, but that impacts others who have equipment on one of the LANs.

 

I will probably just send the new TP-Link equipment back to Amazon & NewEgg next week and buy used Cisco 2702i 802.11ac APs for $20 each off eBay plus a controller.

 

@ernieJohnston 

 

Afternoon

 

Hopefully should be able to address some your issues below

 

TP-Link should support ALL versions of Access Point hardware AND software on the latest controller release. If not, then provide software updates for the hardware back to V1. After all, they are 802.11ac!

 

That would be highly unfeasible for any company to do, even in one grade of WiFi standard (AC) as you say.   The AC standard was ratified in 2013 and was based on WPA2 with TKIP, this has since been revised for AES and now WPA3 SAE.   To support older AC hardware that may not be capable to AES (a lot was not) would mean everything on the SSID running TKIP, do you really want that old a cypher on your WiFi?  

To keep things current and secure we have to drop older hardware at some stage, this is usually during the SDN major upgrades (V3 to V4 for example)

 

Take the EAP225 v1 for example, it is an AC grade device that came out in late 2012 and therefore is nearly a decade old now.  It received updates through to 2020, 7 / 8 years in total before it was retired during v4 SDN.    How is that length of support not acceptable?   Consumer / home grade only get 2-4 years at best!   Its been replaced twice now with the v3 coming out in 2017 (I think) and still getting updates now.

I work in a large education sector with, honestly thousands of Meru, Cisco and Fortinet APs.. they are all dropped at one stage or another, TP SDN is no different to any other vendor.

 

In terms of older firmware for older devices.. the link is posted public and can be found below

https://community.tp-link.com/en/business/forum/topic/264504

 

 

I am trying to set up a SMB (Small to Medium Sized Business) office for a non-profit on 2 VLANs and two SSIDs, one for the staff & one for a large number of guests. For that I need a controller. Already have 2 Class C RFC-1918 LANs.

 

Was planning to start with two EAP620s plus 5 older TP-Link APs, and upgrade as finances permit. But the older APs I bought off eBay will NOT work with the controller & thus no VLANs.

 

As Harry Truman would say, this is Horse Manure.

 

TP-Link equipment is great for Home use, and possibly very small businesses, but it is, imo, NOT for SMBs.

 

Yes, I could reconfigure the LAN to a single Class B & use Guest mode on the APs, but that impacts others who have equipment on one of the LANs.

 

I will probably just send the new TP-Link equipment back to Amazon & NewEgg next week and buy used Cisco 2702i 802.11ac APs for $20 each off eBay plus a controller.

 

At the risk of being harsh, you clearly didn't do the necessary research before starting this project.   I have many customers that run Omada or Unifi on different versions of hardware, when I have to migrate control / take over an existing install checking firmware version support is the first thing anyone does.  This is standard practice for all vendors.

 

I do hope you get sorted ok, but honestly speaking every other vendor you will come across the exact same result if you don't take time to audit and review hardware versions.    I went to log an issue with Meru last month and they wouldn't even take the call as our controller wasn't running the latest version!   Their attitude was update and come back to me, I cant update as some of the APs don't support the new version.