@Contina 

Hi,

Given that the Archer A7 is not even listed as "Planned" in TP-Link's EasyMesh product list, I guess the chance of EasyMesh support being added is pretty much zero.

https://www.tp-link.com/en/easymesh/product-list/#wi-fi-routers

hi  @Kevin_Z 

I have AX55 V1 and MR505 V1 with the latest firmwares. 

My main router is AX55 and I'm trying to put MR505 as a satellite EasyMesh, but I couldn't figure it out. Do these two devices not support each other?

I can easily change AX55 EasyMesh mode to main router or satellite, but MR505 has no option.

  @flowski 

Hi,

Here is a link to a video of someone operating the MR505 via the Tether app and there seems to be a "Mode" option in the "EasyMesh" menu. Although, the person doesn't attempt to change that option, so I can't tell what it does.

https://www.youtube.com/watch?v=09RQiESIb9o&t=538s

Kevin_Z wrote

 

flowski wrote

hi  @Kevin_Z 

 

I have AX55 V1 and MR505 V1 with the latest firmwares. 

My main router is AX55 and I'm trying to put MR505 as a satellite EasyMesh, but I couldn't figure it out. Do these two devices not support each other?

I can easily change AX55 EasyMesh mode to main router or satellite, but MR505 has no option.

 

@flowski , as confirmed with the engineering team, the Archer MR505 V1 does support EasyMesh. However, it can only work as an EasyMesh controller. In other words, it can only be used as the main router, but not the satellite node.

 

You can configure the MR505 V1 as the main EasyMesh router and connect the AX55 to the mesh network as a satellite.

 

Let me know how it works for you. Thank you.

  @Kevin_Z 

 

Thanks @Kevin_Z, so it’s actually false advertising then. I can’t change my main router. I was planning to use the MR505 as a satellite EasyMesh node, but it turns out it only supports controller/main router mode — and that’s nowhere clearly stated.
 

Where can I find a page listing which models support only controller mode? Also, do the Archer MX700 and MR515 support satellite EasyMesh or they're same with MR505 as well?

Hello, @Kevin_Z, TP-Link development team and community,

I am writing from Brazil to commend you on the continuous improvements to the EasyMesh technology, especially the Ethernet Backhaul feature, which is extremely useful. I would like to report a specific behavior I have observed and suggest an improvement for future firmware versions.

Background and Scenario:

In Brazil, local regulations permit the use of channel 13 on the 2.4 GHz frequency. In the area where I live, there is a large number of neighboring Wi-Fi networks, and the vast majority operate on channels 1, 6, and 11. Channel 13 is rarely used, making it ideal for obtaining a cleaner, interference-free signal. 

With this in mind, I have configured my main router, an Archer C80, to operate on channel 13.

The Identified Issue:

I have observed that when using the EasyMesh network with Ethernet Backhaul, the satellite routers (three Archer C64 units) do not follow the main router's configuration. While the Archer C80 correctly broadcasts on channel 13, the Archer C64s, which are connected via wired backhaul, automatically operate on channel 11.

Interestingly, I ran a test: when I disable the Ethernet Backhaul and create a purely Wi-Fi-based EasyMesh network, the satellite routers and extenders respect the main router's setting and all operate correctly on channel 13, as expected. The issue seems to be specific to the wired backhaul implementation.

My Setup:

• Main Router: 1x Archer C80 (Hardware Version V2.20)
• Satellite Routers (via Ethernet Backhaul): 3x Archer C64 (Hardware Version V1)
• Extenders (via Wi-Fi): 2x RE200 (Hardware Version V5)
• Firmware: All devices are updated to the latest firmware version available on the official TP-Link website.
• Compatibility: All devices are EasyMesh compatible.

Request to the Developers:

I kindly request that the TP-Link development team investigate this issue. The ability to set a specific channel on the main router and have all network nodes—especially those connected via Ethernet Backhaul—adhere to that setting is crucial for optimizing network performance in environments with high Wi-Fi density.

Fixing this behavior would allow users in regions like mine to take full advantage of less congested channels, such as channel 13, resulting in a more stable and robust connection for the entire mesh system.

Thank you very much for your attention and for your excellent work in developing these products. I am confident that this improvement would benefit many users of the EasyMesh platform.

Sincerely,
Fernando Cardoso

  @АлександрП2 

Hello! I want to inform everyone who wants to repeat my actions to create a home network 2.5 Gbit\s that it works great in this configuration. Good luck!

AleksandrP2 wrote

  @Кевин_З Hello! I have read all the pages of the conference and I have a question for you: I use Archer AX72 Pro v1.0 1.3.1 Build 20240426 rel.40133(4555) as the main router, I use the WAN/LAN 2.5 Gb/c port to connect the slave router, the slave router is Archer C80 v.1 1.13.15 Build 240812 Rel.53634n(4555), the network operates in EasyMesh with ethernet backhaul mode. The routers are connected by a 10 m long category 6 cable. I am going to buy and install a SWITCH TP-LINK TL-SG105-M2 next to the slave router, connect the network cable from the main router to the switch (it provides connections at a speed of 2.5 Gbps), and connect the slave router Archer C80 to one of the ports of the SWITCH TP-LINK TL-SG105-M2. Do you think that connecting the SWITCH TP-LINK TL-SG105-M2 will not disrupt the operation of EasyMesh with ethernet backhaul? Best regards, Alexander