Early Access Enhanced EasyMesh Support with Extended Guest/IoT/MLO Networking and Advanced Features for BE550 V2
We are pleased to announce the latest pre-release firmware update for the Archer BE550 V2, delivering significant enhancements to EasyMesh™ capabilities, wireless performance, and network management flexibility. This release introduces comprehensive support for extended guest and IoT networks, MLO backhaul, and a suite of advanced EasyMesh features designed to improve security, stability, and user experience.
We strongly recommend all Archer BE550 V2 users upgrade to this new firmware version to unlock these powerful capabilities. Your feedback remains invaluable - please share your experience to help us continue refining our products.
Key New Features & Enhancements
1. Enhanced EasyMesh Network Management
The EasyMesh topology view has been redesigned for improved clarity, offering an intuitive visualization of your mesh network structure. On the Device Info page, you can now view detailed information for each satellite unit, including assigned IP address, number of connected clients, current connection speed.
The Management page enables essential administrative actions directly from the main router, such as controlling LED status, rebooting individual satellites, removing devices from the mesh network.
Additionally, a new Connection Preference setting allows you to manually specify which upstream node a satellite should connect to (e.g., directing an AX55 to associate with either the BE550 or BE805).
2. EasyMesh Traffic Separation: Extended Guest & Multi-Networks
Leveraging the EasyMesh R3 specification, this update introduces Traffic Separation, enabling seamless extension of the main router’s Guest Network and dedicated Multi-Network SSIDs to all compatible satellite units. This ensures logical isolation between primary, guest, and Multi-network traffic - enhancing overall network security and segmentation.
3. Synchronized Advanced Settings Across the Mesh
Critical wireless and security configurations from the main router can now be automatically synchronized to supported satellite units, ensuring consistent policy enforcement and simplified management.
(a) Wireless Network Configuration Sync
- IoT Network settings
- MLO network profiles
(b) Advanced Feature Sync
- ECO Mode
- Hidden SSID configuration
- Reboot Schedule
- Access Control rules
- Device Isolation
4. EasyMesh DPP (Device Provisioning Protocol) – QR Code Setup
Adding new satellites is now faster and more intuitive via EasyMesh DPP. Within the Tether app, simply scan the QR code on a compatible satellite device to securely and automatically configure it into your mesh network - eliminating manual entry and reducing setup errors.
5. MLO Backhaul
This firmware introduces MLO Backhaul, allowing simultaneous use of multiple frequency bands (e.g., 5 GHz + 6 GHz) for inter-node communication. This significantly boosts backhaul throughput and resilience, especially in high-demand environments.
6. One-Click EasyMesh Network Reset & Reboot
Troubleshoot mesh instability with a single action: the main router now offers “Reset EasyMesh Network” and “Reboot All Nodes” options. These tools provide a quick way to refresh the entire mesh topology without physical access to individual units.
7. Fast Roaming with 802.11r Support
Seamless client roaming is enhanced through native support for the IEEE 802.11r (Fast BSS Transition) protocol across the EasyMesh network. Compatible devices will experience near-instantaneous handoffs between nodes - ideal for real-time applications like VoIP and video streaming.
8. Roaming Bindings for Client Affinity
Gain granular control over client mobility with Roaming Bindings. You can now pin specific devices (e.g., smart TVs or IoT sensors) to a designated EasyMesh node, preventing unnecessary roaming and improving connection stability for latency-sensitive or stationary clients.
9. Additional EasyMesh Improvements
- IPTV Support: LAN ports on satellite units now support IPTV traffic pass-through.
- Password Synchronization: The main router’s admin password can be synced to compatible satellites for unified access control.
- UI/UX Refinements: Streamlined interface for all EasyMesh-related functions, improving navigation and readability.
10. Optimized Parental Controls Interface
The parental control dashboard has been visually and functionally refined, offering clearer scheduling options, device grouping, and usage insights - making family-friendly network management more intuitive than ever.
Upgrade today to transform your home network into a smarter, faster, and more secure ecosystem with the power of next-generation EasyMesh.
Firmware Download:
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the pre-release firmware!
(2) For the sake of insurance, it's always recommended to save a copy of the router's Backup Config file before upgrading or downgrading.
(3) This pre-release firmware for Archer BE550 V2 can be applied to all versions (EU/US/AU/CA/etc).
(4) You may follow the guide to upgrade the firmware of your router. How to Upgrade the Firmware on the TP-Link Wi-Fi Routers.
(5) The screenshots in this article are taken from the web GUI of Archer BE550 V2 for reference only.
(6) This version of software can't be degraded to the previous official version.
Direct Firmware Download Link
| Archer BE550_V2 | Archer BE550_V2_1.3.1 Build 20260303 (Pre-release firmware) |
Additional Information
As always, we value your feedback. If somehow you encounter an issue during or after the router firmware upgrade, please comment below with the following info. Your input helps us continue to improve and provide the best products and support.
- Provide a detailed network layout, including how the devices are connected, especially if there are EasyMesh satellite devices.
- Detailed issue description, and provide more information on the specific conditions that seem to trigger the problem.
Thank you for your continued support and for being part of our community.
Apr 15, 2026
Updated to provide a new version of pre-release firmware, which fixed the reported client list display issue.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
WARNING to all:
Do not get tempted to install this firmware!
I have installed it over 2 months ago on a mesh of 3 BE550 V2.6 routers with severe issues! The router factory resets on it's own whenever there's a log issue and you will find yourself restoring it all for hours each time.
Support worked with me asking me to allow debug data. I provided them will all data over a month ago and they confirmed they found the root cause.
Since then they simply ghosted me for weeks, leaving me with this unstable beta.
Being a 30+ years developer I know well enough that if you work on a bug and already found the root cause, it should takes a few days top to patch it.
I suspect they simply moved on to other things and left this to dry on the backlog.
I pinged them weekly asking for a patched firmware only to get generic responses such as "soon", "it takes time" etc...
Meanwhile I suffer the factory resets from time to time. Funny that the customer is the one that needs to follow up with the service provider and not the other way around as you would expect.
I finally gave up and I've spent 2+ hours Today manually putting back the old 1.25 version on the routers and painfully restoring all settings manually (recovery from 1.3 is not working well).
I will NEVER try any of this company's Beta NOR will I personally buy any of TPLInk's hardware ever again.
The service for the products is not acceptable (for me).
To summarize my experience:
TPLink used me a test subject for this unfinished firmware and once they found the issues they just ghosted me and left me to hang.
I recommend you keep clear of these beta releases until a stable tested release come out.
- Copy Link
- Report Inappropriate Content
@Kevin_Z
Any news on this new firmware? Would this be a final or beta again?
- Copy Link
- Report Inappropriate Content
@Gilad-A there's another post that says it's due to smb being enabled? Is that the case for you too, or does it happen without smb.
To TP LInk: One thing i've noticed is that the channel width i set for my main router, doesn't apply to the satelite router, i live in the uk and near an airport so concerned about overlapping with DFS channels, is this something that's being worked on.
Also for people wondering, after applying the update, mlo accross 2.4/5/6 all work as expected, and my pixel 10 pro swaps between the main router and the satellite, fast enough that i can't notice the difference without staring at wifiman. I have two be550 v2's.
I've taken a backup of my config in case the issues with reboots and losing configuration happen.
- Copy Link
- Report Inappropriate Content
@Naebun I indeed had SMB enabled as I have a shared drive on my main router. I didn't try turning it off as I need it.
I since then reverted to V1.2.5 which is rock solid. I do hope that someday, the tp-link team releases a stabled and TESTED version of the firmware (a release version). I'll return to try it only once it is publicly released and people report it as stable as I had a really rough experience and lost a lot of work hours around this only to get mostly brushed off by the team for helping to test it.
- Copy Link
- Report Inappropriate Content
@Naebun So far I have been running quite stable with 2 units, one main and one wired satellite. SMB is enabled on the main only but I am not utilizing it currently. No issues when rebooting. I have everything on UPS so hoping to not deal with power outage issues.
I have noticed some funky stuff when playing around and adding additional satellites that currently do not support the traffic separation. I had tested out adding a non BE500 version of the Archer BE9300 v2.6 (Download for Archer BE9300 | TP-Link) as well as an older AX73 v1 with wired connections. Eventually the clients would slowly dissapear from the menus and then alltogether completely. After that I could no longer login to the web UI. Oddly enough, all traffic continued to work flawlessly so if I didn't ever check on the network I would never know. Resetting the Main BE550 would reset all of this behavior and I could set everything back up. Not a huge deal since the 2 550s cover the area fairly well but I was hoping to be able to extend even just the main ssid a bit with the random hardware I have around.
So far though, Main, IOT, Guest, and MLO networks are all operating as intended on the two 550s for all bandwidths. I have not tried multinetwork yet.
Right now the only two things I could request are additional viable satellite models and for IOT Device names to transfer between the satellites and the main router. I have named all of them since most come through generic to the device model. If they are installed in the middle of the two radios and jump, the satellite doesn't pick up the device name. A sync for that would be neat. I can name them manually in both but with 100 devices currenlty its a bit of a PITA lol.
- Copy Link
- Report Inappropriate Content
@rm1091 out of curiosity do you get the same behaviour as me, with regards to changes to the channel width of the WiFi not affecting the satellites.
Unfortunately it makes sense that satellites without a new firmware don't play well with the new features, maybe by general release they're of at least minimise the negative effects of that.
good to hear it only effects the ui and not functionality though, would suggest fixing it would be easier
i believe easy mesh is a WiFi standard rather then a tp link standard, so hopefully that means they cover a wider range of devices with the updates to it.
- Copy Link
- Report Inappropriate Content
@Naebun I have a BE550 v2 as main and a BE230 v2 as a satellite, when I change the Channel Width on the BE550, the BE230 needs a reboot for the change to follow Channel Width of the BE550.
- Copy Link
- Report Inappropriate Content
Naebun wrote
@Gilad-A there's another post that says it's due to smb being enabled? Is that the case for you too, or does it happen without smb.
To TP LInk: One thing i've noticed is that the channel width i set for my main router, doesn't apply to the satelite router, i live in the uk and near an airport so concerned about overlapping with DFS channels, is this something that's being worked on.
Also for people wondering, after applying the update, mlo accross 2.4/5/6 all work as expected, and my pixel 10 pro swaps between the main router and the satellite, fast enough that i can't notice the difference without staring at wifiman. I have two be550 v2's.
I've taken a backup of my config in case the issues with reboots and losing configuration happen.
How are the two BE550s connected to each other, via wireless or cable?
If it's wireless, the channel width settings on the main BE550 should be synchronized to the satellite without an issue.
It may not synchronize properly if they are connected via cable. Please try the following to check if you can make it synchronize:
Reset the satellite BE550;
Connect it to the main BE550 wirelessly via EasyMesh;
Once the EasyMesh is working properly via the wireless connection, connect the main BE550's LAN port to any Ethernet port of the satellite via an Ethernet cable;
Check again to see whether the channel width is synchronized correctly.
Regarding the DFS channel concern, please don't worry about it overlapping. When the channel is in DFS, and a radar signal is detected, it automatically switches to a non-DFS channel.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Naebun wrote
@Naebun Sorry to hear that.
My apologies that I actually missed a very important step in my previous response.
Reset the satellite BE550.
Connect it to the main BE550 wirelessly via EasyMesh.
Once the EasyMesh is working properly over the wireless connection, check that the channel width is correctly synchronized on the satellite.
Connect the main BE550's LAN port to any Ethernet port of the satellite via an Ethernet cable.
Check again to see whether the channel width is synchronized correctly.
If possible, I hope you can give it a try and let me know whether it works.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 20729
Replies: 120
Voters 4
