Archer BE550 - Upload speed capped below 100 Mbps on Wi-Fi 6 device (POCO F5 Pro)
Hello TP-Link Community / Support team,
I am experiencing a very specific and frustrating upload speed issue with my new Archer BE550 (Wi-Fi 7) router, and I believe it is a firmware compatibility bug.
My Setup:
* ISP: Airtek Solutions (Venezuela) - Fiber Optics (1 Gbps Symmetric plan).
* Router: Archer BE550 (BE9300).
* My Device: POCO F5 Pro (Wi-Fi 6 capable, Snapdragon 8+ Gen 1 chip).
* Comparison Device: Redmi Note 11 (Wi-Fi 5).
The Problem:
When my POCO F5 Pro connects to the 5 GHz band, the download speed is amazing (around 900+ Mbps), but the upload speed is strictly capped and stuck at 93-94 Mbps. It never goes higher, behaving as if there is a 100 Mbps link-rate limit or an aggressive QoS rule applied specifically to my device's upload traffic.
Troubleshooting already done:
1. Cross-device testing: A Redmi Note 11 (Wi-Fi 5 device) on the exact same 5 GHz network easily surpasses 200+ Mbps upload.
2. Band testing: If I connect my POCO F5 Pro to the 2.4 GHz band, the upload restriction disappears, and it unblocks, reaching over 105-161 Mbps upload.
3. Router Settings: I have completely factory-reset the router. Parental Controls are off, QoS is default, and no bandwidth limitations are configured in the Tether App.
4. Wireless modifications: I tried changing the 5 GHz mode from "802.11a/n/ac/ax/be mixed" to "802.11a/n/ac/ax mixed" (disabling Wi-Fi 7 protocols) and reducing the channel width to 20/40/80 MHz. This briefly allowed the upload speed to peak at 123 Mbps, but it eventually drops back down or remains unstable compared to the 900 Mbps download. Turning off OFDMA/MU-MIMO didn't help either.
There seems to be a specific handshake/protocol bug between the Archer BE550's Wi-Fi 7 firmware features and the Wi-Fi 6 (ax) chip on certain Xiaomi/POCO devices when managing upload streams on the 5 GHz band.
I would highly appreciate it if the engineering team could investigate this compatibility issue. I am willing to test a Beta firmware if available to resolve this bug.
Thank you in advance!
