Official Release Deco X50/X55_V1_1.6.7 Optimized the Client Network Stability
This Article Applied to:
Deco X50/X55_V1_1.6.1/1.6.4
Modifications and Bug fixes:
- Supported EasyMesh
- Supported TSS_V2(TP-Link Simple Setup) function, which enables thed device to quickly discover and pair with TP-Link smart home and EasyMesh-compatible devices.
- Fixed the bugs of frequent client disconnections;
- Fixed the bug that clients cannot access the Internet after enabling the DoH server.
Download Link：
| Deco X50/X55_V1/V1.6 | 1.6.7_build20250314_Official |
Update Advice:
1. How to manually update the firmware via web UI- How to Update the Firmware of Deco.
2. The 1.6.7 could revert to the official 1.6.3/1.6.1 directly via web UI.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@David-TP I installed the newest Deco App. No difference. I can use the Deco app for a while, but then the following occurs:
- The device that normally is on top of the client list "IPhone van Jan (me)" is suddenly not in the list anymore.
- all other decos except the main deco have 0 clients.
- then suddenly all remote decos except the Main deco are displayed offline (red) in the app.
- the main deco is still working, but the remote decos are also still working but these are still displayed offline
- all iot devices are showing offline;
the only way recover is pull all plugs from all decos. Wait 10 seconds. Put all plugs from all decos back in power socket. Wait for reboot. And then after a while the decos and clients are displayed normally in app.
network management is useless in this way.
- is this issue fixed in 1.6.7?
- when will 1.6.7 be released?
thank you for your reply
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Exactly same for me too..
Boezio wrote
Hi, i m using the above build of 1.6.7 with five x50 and 1 x50outdoor (when the outdoor one Will receive updates, almost a beta?). My system with the above build Is stable and i have the Best functionality since today. The only issue Is that main x50 CPU Is often at 100% so the app in this case Is lagging in info updates? There Is something i can do? Thanks and keep up this good work! Alex
- Copy Link
- Report Inappropriate Content
I have the same problem with deco x50v1 1.6.7 and X20v4 1.5.5. Devices appear and disappear. Deleting. Rebooting doesn't help. Maybe the problem is in x20?
- Copy Link
- Report Inappropriate Content
Hi!
Deco was attempted to be set as Agent.
I did not collect Logs yet, but will try to play around again (in coming days) with settings and set Deco as Agent and Controller and collect Logs.
- Copy Link
- Report Inappropriate Content
Thanks for the feedback.
The CPU of Deco is limited, and newly introduced features will increase its workload. Additionally, more satellite units in the Mesh network will also add to CPU usage. Despite the rise in CPU utilization, as long as the Mesh system continues to operate effectively, it remains within acceptable CPU load parameters.
Best regards.
- Copy Link
- Report Inappropriate Content
xplodzs wrote
I have the same problem with deco x50v1 1.6.7 and X20v4 1.5.5. Devices appear and disappear. Deleting. Rebooting doesn't help. Maybe the problem is in x20?
Hi, nice to see you again.
It would be much better if you could start a new thread and add more details:
https://community.tp-link.com/en/home/forum/edit/topic?moduleId=39
"Devices appear and disappear. Deleting. Rebooting doesn't help."
What are these "devices"? Can I have their model numbers?
Can you constantly reproduce this issue?
By the way, how about your current network map on the Deco App, such as:
Best regards.
- Copy Link
- Report Inappropriate Content
@David-TP this is een ongoing issue widespread along many firmware versions on different Deco X models. Why start a new thread? Why not solve the issue.
- Copy Link
- Report Inappropriate Content
Hi, when the engineer approved the community to launch the Beta/EA testing, they hoped community users could help find out some hidden issues in the real user scenarios. If certain feedback has gone through many firmware versions, it would not be what they're expecting to see. While all feedback is valuable and important, it's just not their main focus for the EA testing.
You're right that there is similar feedback about "online Clients" on different models, so it is not dedicated to a particular version. The latest beta/EA versions not only introduce new features but also incorporate potential fixes identified by engineers during previous troubleshooting sessions with users. I can't guarantee it will 100% fix the similar issue, and it did mitigate some potential problems. Quoting "having the same issue" might not be helpful, and could prevent other users from installing the tested version. Starting a new thread with more details and submitting the APP log would offer more valuable clues for troubleshooting.
Since you asked, I'd like to talk more about email escalation. Many users prefer engaging directly in community chats as they believe it can benefit others. That's true, and it is also what all moderators tend to achieve. While some complicated and unusual issues are out of our control. So, if users can constantly reproduce this issue, I think it could expedite the resolution process if the engineers are involved, which, of course, needs your cooperation with the engineers. If the suggestions are approved as useful, I'll share them with the community as well.
Thanks for your patience.
Best regards.
- Copy Link
- Report Inappropriate Content
@David-TP thank you for your honest reply. Hoping that I will be able to install 1.6.7 manually without crashing te router. Do you know when it will be released?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 21684
Replies: 119
Voters 0
No one has voted for it yet.