AX20 V1 Hardware Is Stronger Than AX10 V1– So Why No EasyMesh?

AX20 V1 Hardware Is Stronger Than AX10 V1– So Why No EasyMesh?

AX20 V1 Hardware Is Stronger Than AX10 V1– So Why No EasyMesh?
AX20 V1 Hardware Is Stronger Than AX10 V1– So Why No EasyMesh?
a week ago
Model: Archer AX20  
Hardware Version: V1
Firmware Version: 1.3.8 Build 20230830

Hello everyone,

 

I would like to open a constructive technical discussion regarding EasyMesh support for the Archer AX20 v1 (EU).

 

I recently contacted TP-Link support directly regarding this matter. While support confirmed that there is currently no confirmed information about future EasyMesh support for the AX20 v1, they also did not confirm any permanent hardware limitation preventing it.

 

From a hardware perspective, many users are struggling to understand why the Archer AX10 already received EasyMesh support while the Archer AX20 v1 (EU) still has not.

 

Based on publicly available specifications, the AX20 v1 (EU) appears to offer stronger hardware overall:

 

Archer AX20 v1 (EU):

 

- Broadcom BCM6755

- Quad-Core 1.5 GHz CPU

- 16 MB Flash

- 256 MB RAM

- High-Power FEM

- USB support

- Higher overall wireless throughput capability

 

Archer AX10:

 

- Broadcom BCM6750

- Triple-Core CPU

- 16 MB Flash

- 256 MB RAM

- Lower-tier positioning overall

 

Because of this, many AX20 v1 owners are wondering whether the absence of EasyMesh support is truly caused by hardware limitations, or if it is more related to firmware development priorities, SDK/software integration, certification process, or long-term product support strategy.

 

This topic is not intended as a complaint toward TP-Link. I simply hope to better understand the situation and also see how many AX20 v1 users are still interested in EasyMesh support for this platform.

 

If other users or moderators have additional technical insight regarding the AX20 v1 situation, I would genuinely appreciate hearing your thoughts.

 

Thank you.

1
1
#1
3 Reply
Re:AX20 V1 Hardware Is Stronger Than AX10 V1– So Why No EasyMesh?
a week ago - last edited a week ago

  @Constantin89 

 

Hi,

 

I can't give you a competent answer to the question why there is no EasyMesh support for the Archer AX20 V1 (and V2), but I do see that the BCM6755 SoC is not listed as an "Active" part anymore on Broadcom's website.
https://www.broadcom.com/products/wireless/wireless-lan-infrastructure
So, in case TP-Link required Broadcom to do some groundwork (in the chipset drivers) before being able to implement EasyMesh with the BCM6755, things might become difficult.

 

1
1
#2
Re:AX20 V1 Hardware Is Stronger Than AX10 V1– So Why No EasyMesh?
a week ago

  @Constantin89 

 

On top of everything mentioned already, the AX20 v1 v2 and v3 are EoL products for 2 years already, according to the EoL list - details.

Although, there is still a possibility to use the AX20 in an Easymesh setup if you're using this model as your main router and add an Easymesh satellite device.

A lot of users were able to do that by using the WPS method for building Easymesh, despite the fact that TP-Link is not officially supporting this setup.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue as a "Recommended Solution". BTC:149wubkkfoLmNDjDbiTxx4ZU8mpcMA5CJt
0
0
#3
Re:AX20 V1 Hardware Is Stronger Than AX10 V1– So Why No EasyMesh?
a week ago

  @terziyski 

 

Thanks for the additional information regarding the EoL status and the unofficial "EasyMesh" possibility.

 

I actually tested something very similar.

 

I temporarily used the AX10 as the main EasyMesh router just to configure the C80 as a satellite first.

 

After that, I disconnected the AX10 and connected the AX20 v1 instead, hoping it would detect and continue using the existing EasyMesh setup.

 

Interestingly, the AX20 could actually see the C80 satellite in the system, but every time I tried adding/adopting it, it failed with an error, anyway the whole setup, C80 and AX10 where unstable and didn't work properly...once the AX20 it did not seem capable of properly adopting or managing it.

 

So from my testing, it really feels like the AX20 v1 may have some partial EasyMesh-related (becouse of OneMesh) functionality internally, but not a complete or fully working implementation.

 

I still have not tested the WPS pairing method specifically, so maybe I will try that as well out of curiosity.

 

Still, the EoL information and the Broadcom explanation definitely make the whole situation make sense now....

0
0
#4