XE75 V3.6 2.4GHz mass client disconnects — does firmware 1.5.0 add 20MHz/channel-width control
I have a 3-node Deco XE75 V3.6 mesh using wireless backhaul. Approximately 130 clients are connected, including approximately 80 stationary 2.4GHz IoT devices (ESP/Espressif, WiZ, Hubspace, AiDot, ecobee, Ring, Chromecast, etc.).
This problem began immediately after replacing my older TP-Link Deco mesh with the XE75. The previous Deco system did not exhibit this problem.
I collected 68.6 hours of continuous monitoring data and measured:
- 27,057 client drop events (~394/hour)
- 70% reconnect in under 60 seconds
- Median disconnection duration: ~40 seconds
- 24% occur during mass-drop events, with 5–39 devices disappearing in the same second
- Affected devices are overwhelmingly stationary 2.4GHz clients
- 5GHz and wired clients are stable
- Signal strength is strong; for example, a monitored client averaged approximately -50 dBm during events
I have already tested disabling Fast Roaming, Beamforming and Mesh Technology per client, as well as Connection Preference, Smart Connect/network configuration changes and the dedicated IoT network. These have not resolved the problem.
I am currently being offered the irreversible firmware update 1.5.0 Build 20260603 Rel.14401.
Before installing it, I need clarification from TP-Link engineering on the following:
1. Does XE75 V3/V3.6 firmware 1.5.0 Build 20260603 Rel.14401 include the “WiFi Network Mode” / 2.4GHz performance changes that appeared in the V2/V3 beta firmware (including 1.4.999 Build 20260319 Rel.57690 Beta)?
2. Does 1.5.0 Build 20260603 Rel.14401 allow manual selection of 2.4GHz channel width, specifically forcing 20MHz rather than 40MHz? If yes, where is this setting located?
3. If manual channel-width selection is not exposed, does this firmware internally change 2.4GHz channel-width/channel allocation or mesh-backhaul behavior to address IoT stability?
4. Is TP-Link aware of an XE75 V3/V3.6 issue causing large numbers of stationary 2.4GHz clients to disconnect simultaneously and reconnect approximately 30–60 seconds later?
5. Is there a current V3/V3.6 beta or engineering firmware specifically intended to address this issue if Build 20260603 Rel.14401 does not?
Because the offered 1.5.0 upgrade states that it cannot be downgraded, I would appreciate confirmation of these points before installing it.
I can provide the monitoring logs and analysis showing the disconnect frequency, duration distribution and synchronized mass-drop events if TP-Link engineering would find them useful.
@Nate541 I have XE75 (v1, firm 1.5.0)) & XE75 Pro (v3, firm 1.5.0) & I've been unable to locate a 20Mhz channel width option for 2.4Ghz.
...I even purchased a brand spanking new BE95, but even that did not have the option (I promptly returned). Sadly, the Deco line appears designed to be app-only with limited access to advanced controls. It seems like TP-Link desgined Deco for "easy mode" with "advanced mode" only available via Archer or Omada. I really would like to know why we're locked out of an "advanced mode" with fine-grain controls. ...This is the reason people hack their routers to install OpenWRT, especially since TP-Link benefits from using the project's software, but lock it down for end users. Also, based on my experience & those of others I read, the Deco line is ill-equiped to deal with crowded 2.4Ghz band
I also have a large 2.4 client list comprising of ESP32's, Smart Fans, Wyze Cams, etc. I've literally been working with tech support for --3 months-- to diagnose my 2.4Ghz slow down and the best I get is "try this beta firmware & if no 20Mhz option, maybe one day we might give it to you." So much for IoT. :/ Kicker for me is I droped money on the XE75 Pro, as tech support led me to believe if would help resolve my problems with my XE75, but since it hasn't and their support is VERY slow, now I can't return it and they refuse to refund me. To add insult to injury, both my XE75's now have a dead top ethernet port, which didn't occur until diagnosis started (dumb luck I guess, as I've read multiple reports of the top port dying).
Side-note, @Solla-topee, I really would like to see TP-Link improve their tech support experience. I was shocked to find your support site pushes me to talk with AI, then web chat with real person, then email, with calling only as a last resort. Imagine you just bought a new router, your having problems connecting to the internet, and the router company wants you to connect with them on the internet you don't have, because their product isn't working? ...That's backwards & a recipe for upsetting customers. The agents are nice, but the current support system is slow, clunky and wasteful. If I were a tech support person, I'm not sure I would enjoy coming to the same problem for --3 months--, having to re-read diag steps to help customer on next step. Should have been escalated via phone immediately & resolved in 1 day. God help the average non tech-savvy person who only knows "my wifi is broken." 