2.4 GHz network VERY unstable with Deco XE70s
2.4 GHz network VERY unstable with Deco XE70s

I am experiencing an issue with the 2,4 GHz networks provided by my XE70 Pro mesh (3 nodes). The mesh provides 3 networks: main, IoT, and Guest. The IoT and Guest are 2.4 GHz only. The problem became apparent when my Wyze cameras were often VERY slow to connect to and sometimes even appear offline. These camera are 2.4 GHz only and are on the IoT network. Thought it may be a coverage issue so moved some cameras closer as a test, but no luck.
After lots of Googling research and seeing other reports of similar issues, I started to look for tools to help me diagnose my particular issue. I found a tool called WIFI Explorer which has provided some interesting insight into the behavior of my network. I'll use screenshots below to tell the story. Since I have 3 XE70s in my mesh network, there are 3 versions of each of my networks (main, IoT, and Guest) visible at any given time.
I'll start by showing a picture of the signal strength of my 5 GHz network from the XE70 node that I am closet to:
The signal strength remains nice and flat for the 5 minute duration shown, which is what you would expect of your network. This is consistent across all XE70 nodes regarding the 5GHz network. Never appears to be a drop in signal strength.
However, I'll now show the signal strength for all 3 nodes for the 2.4 GHz IoT network.
Node 1 - closest to my location:
Node 2 - Room 2
Node 3 - Room 3
All 3 nodes show VERY frequent times of complete outage during the same timeframe! This also happens on the 2.4 GHz network of my main network and Guest networks so is common to the system. I thought perhaps that it may be something in TP-Links implementation of a mesh network, but there have been times when ALL THREE are out at the same time giving me ZERO 2.4 GHz network coverage and wreaking havoc on my 2.4 GHz-based devices - particularly my Wyze cameras to the point where they are damn near useless.
I certainly HOPE someone can help here as I really want to like TP-Link products as I have quite a few. And I will be MORE THAN HAPPY to admit ignorance if it is something that I am doing wrong. Nothing special about my configuration as it is as it was out of the box. No fancy config here.
I am quite remote with the next neighbor about 1/2 mile away, so I would not think interference plays a part here.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, Thank you very much for the feedback.
Could you please send an email to support.forum@tp-link.com (please also add the forum ID#712394) with the following details:
1. Some screenshots of the Deco network maps, such as:
2. How many smart home devices or 2.4GHz devices do you have in total?
Wait for your reply and best regards.
- Copy Link
- Report Inappropriate Content
Really good insight - I have the exact issue, but with 3 X55's. @ David-TP Is this being addressed on that model as well?
- Copy Link
- Report Inappropriate Content
Hi, Thank you for the feedback.
Can I have the current firmware version of your Deco X55?
Here are beta firmware versions for Deco X55 v1.6/V2.6 that have optimized the overall 2.4GHz performance.
Wait for your reply and best regards.
- Copy Link
- Report Inappropriate Content
I want to join in the fun. Lately, my deco system that has been fine for 2 years started dropping or even prevent devices from connecting to both my IOT (2.4) network and my 5G network. I have literally tried everything i've googled (Fast roam, beamforming, etc) and nothing helps as it may work for a bit then disconnect. sometimes able to reconnect and sometimes not.
My next option is to completely reset and startover which is obviously a giant Pain in the *** as i know i have dozens of IOT devices but it may be my last option.
However, i wanted to check here since i saw this thread. I also have the X55 system which again, as been except the last about month.
Thanks
- Copy Link
- Report Inappropriate Content
Thanks for picking this up.
So interestingly, I have 3 X55's with 2 different FWs, but they all think they are current. The main unit and one remote are on 1.6.1 Build 20241010 Rel 65389. The third unit is on
1.2.0 Build 20231229 Rel. 43148.
The third unit was a refurb that tp-link sent to replace a dead OOB unit. It won't seem to upgrade the FW past 1.2 although all three are set to auto update.
Regards,
Ryan
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I'm happy to report that with the beta firmware, I've been able to decommission my google wifi network and get Eufy fully working on the deco network. It's only been a couple of hours, but it's been solid so far!
Thanks!
Greg
- Copy Link
- Report Inappropriate Content
@Simpsong00 - glad to hear you had success. I was finally able to upgrade some of my 5 XE75pro's, using the tip from David in another thread (Log into the web UI via the IP address of Deco XE75 Pro on the Deco APP, instead of http://tplinkdeco.net). However, not all of them would update after two tries. Only 3 updated - the other 2 are still at 1.2.11. I first thought it was because of different hardware versions (v2 versus v3) but one of the v3's also updated. I will have to test some of the connections over the weekend (my Nest cams and smoke detectors) and see if things now work better - although I would assume all pod's should update to 1.2.12 to have a consistently operating network.
I guess we are all still waiting on a formal firmware upgrade that can be run over the app to ALL XE75pro's regardless sub-versions and making sure that all 2.4Ghz traffic is handled properly.
- Copy Link
- Report Inappropriate Content
@MickF Yes, a formal firmware release would be best! Sorry it didn't take for all of your units. Best of luck.
- Copy Link
- Report Inappropriate Content
I did the 1.6.4 update on my X55s yesterday AM and things are seeming stable. Two of my units are v1 including the main unit - they took the upgrade. The v2 third device stayed on 1.2. I can't tell from this thread if the x2 hardware is an issue or not so I took the additional step in the app to force all the 2.4 IoT devices to only use the closest v1 unit.
Thanks for getting this into the 1.6.4 build - I'll report back if I see any bad behaviors.
Ryan
- Copy Link
- Report Inappropriate Content

Information
Helpful: 3
Views: 892
Replies: 20
Voters 2

