New Release Deco M5 1.7.4/1.7.6
Current Release
For Deco M5(V1/V2/V3/V3.2)
Deco M5_1.7.6 Build 20240305 for EU version
Deco M5_1.7.4 Build 20231222 for other versions(like US/CA/AU, etc.)
Modifications and Bug Fixes:
1. Improved system stability.
2. Fixed several security vulnerabilities.
---------------------------------------------------------------------------------------------------
History Release
For Deco M5(V1/V2/V3/V3.2)
Deco M5_1.7.3_Build 20230906
New Features/Enhancements:
1. Optimized the auto-upgrade function.
2. Optimized the accuracy of the client list display.
3. Improved system stability.
4. Fixed the bug that port scanning errors recognized some IOT devices as risky devices.
5. Fixed the bug that parental control doesn't take effect.
For Deco M5(V1/V2/V3/V3.2)
Deco M5_1.7.1_Build 20230608
Modifications and Bug Fixes:
1. Added the static route function.
2. Added the ability to customize the MTU.
3. Added IoT network function.
4. Added auto upgrade function
5. Added ECO Mode (includes Power Mode, Wi-Fi Schedule, and LED Control) to save energy.
6. Optimized the MAC Clone function.
7. Fixed the bug of network abnormality under specific ISP.
For Deco M5(V1/V2/V3/V3.2)
Deco M5_1.6.5_Build 20230110
Modifications and Bug Fixes:
1. Fixed the issue that failed to set up Deco on Android 13 phones.
2. Fixed the issue that the online client displays zero incorrectly.
3. Optimized the Network Optimization feature.
For Deco M5(V1/V2/V3/V3.2)
Deco M5_1.6.1_20220818
- Apply to US/EU/JP/AU/CA/TW/ID/UK/SW/EU/B4 versions.
- 1.6.1 firmware will be gradually released to different areas and if currently it could not be detected on the Deco APP, you could wait for a while or a firmware upgrade via web UI is recommended.
Improvements:
1. Optimized the Monthly Reports.
2. Improved system reliability.
Bug fixed:
1. Fixed the bug that clients won't be able to obtain IP addresses randomly.
2. Fixed the bug that insight/time limit of parental control won't reset the next day.
3. Fixed the bug that No-IP DDNS doesn't take effect under PPPoE connection.
4. Fixed the bug that the client list randomly does not show any client or recognizes satellite Deco as a client.
For Deco M5(V1/V2/V3/V3.2)
New Features/Enhancement:
1. Added Reboot Schedule for every day/week under Deco App > More > Reboot Schedule.
2. Added support for customizing Satellite Deco signal source under Deco App > Internet > Select the Satellite Deco > Signal Source.
3. Added support for customizing clients connection preference under Deco App > CLIENTS > Select the client > Click the gear icon on the right-up corner > Connection Preference.
4. Added No-IP and DynDNS to the DDNS settings under Deco App > More > Advanced > DDNS
5. Added Smart DHCP on/off switch in Access Point mode under Deco App > More > Advanced > Smart DHCP
6. Added a prompt when the Ethernet link rate goes down to 100Mbps.
7. Added schedule and bandwidth limit to guest network under Deco App > More > Wi-Fi > Guest Network.
8. When configuring Deco for the first time, you can choose to establish an IPv6 connection directly.
Related Articles:
Frequently Asked Questions on Deco Firmware Update
Deco Monthly Recap- Check What's Currently Going on With Deco
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@NanoG6 Hi, I have sent a middle firmware between 1.6.5 and 1.7.1 and you could install the beta firmware first, then check whether you could downgrade it back to 1.6.5.
And it is also suggested to send an email to support.forum@tp-link.com (please add forum ID-274402)so that we could check more details to see whether there is any other workaround instead of downgrading the firmware.
@XWEBNetwork Thank you for the feedback and sorry for the delay.
"Same symptons as others", it did not help too much to understand what had happened to your Deco after the firmware upgrade. You are welcome to send an email to
support.forum@tp-link.com (please add forum ID-274402)as well so that we could check more details to see if there are some useful suggestions.
Thank you very much.
Best regards.
- Copy Link
- Report Inappropriate Content
Hi, Thank you very much for the feedback.
I was a little curious about what devices you have used for the WDS Bridge as well as the Powerline between Decos.
Compared with 1.6.5, there are more new features added. So more background processes might occupy RAM usage. so personally, I think it might interfere with the network performance in certain ways. Are you able to stably reproduce the regular timeouts issue on Deco units in a short time since it might be earlier to troubleshoot the problem?
And How many clients do you have in the whole Mesh network?
It is suggested to leave both "Fast Roaming" and "Mesh Technology" disabled on the Deco APP.
Thank you very much for your time and patience.
best regards.
- Copy Link
- Report Inappropriate Content
@David-TP Since 1.7.1 I notice all my Espressive devices are missing from the connected devices list.
All are connected, I can access these and Home Assistant communicate right with them using Wi-Fi so these devices are not offline.
It is really anoying because for example if I want to check if roaming is disabled as I wish I cannot because this setting is not even showed for offline devices.
These are both ESP32 and ESP8266 devices.
- Copy Link
- Report Inappropriate Content
I've managed to get the network stable again by:
-Disable beamforward
-Disable fast roaming
-Set DNS to 8.8.8.8 / 8.8.4.4
Followed by a full power cycle of every single unit. We've been OK for about 4 days now.
However, these are features that were previously enabled and working without issue on 1.6.5.
Further, as expressed by others, device recognition has been quite spotty. I'm just getting a bunch of "network device" hostnames as opposed to the actual devices. And interestingly, a bunch of the Decos have just reverted to saying M5 instead of the set custom name. So now I have to re-identify them all within the topology.
So, to elaborate, 1.6.5 was stable and excellent, for the most part. Transitioning to 1.7.1 introduced a sleu of performance issues, especially with Deco's connected via WIFI backhaul. Most are hardwired. But they too were susceptible.
Post reboot, everything would funciton as expected but within a few hours, anything connected to any deco outside of the main would slow to a crawl, have trouble maintaining a connection, and/or just say no internet. I even noticed on my phone, the SSID would completely disappear.
The app would report all as fine, but clearly, things were not. I really should have gotten a dump, but it was more important to just get things stabilized. Once our season slows down, I can do that.
Perhaps there is a mem leak or a rogue process causing the issues? This only seems to be affecting our larger network here. I have several other small M5 nets with like 2-4 decos and 1.7.1 seems OK so far.
- Copy Link
- Report Inappropriate Content
@David-TP Hi David, the two devices I am using are:
- for the WDS bridge: TPlink TL-WA901ND. Hardware revision V5, firmware version 3.16.9 Build 201030 Rel.58094n. I am running it in Bridge with AP mode.
- for the powerline connection I am using TPlink TL-WPA4220 at each end of the link (hardware revision WPA4220 v1 08C84015, firmware version 1.2.9 Build 160525 Rel.35241n)
The bridging seems to work absolutely fine as I can access the network and the fiber connection no worries all the way down at the YARD2 node.
I turned off beamforming last night as a test and the majority of web access seemed to vastly improved as a result. Today it looks like the timeout issue has reoccurred for atleast two computers which would access via wifi. I carried out a full reboot of the deco network and the speed returned briefly, not sure what this indicates but its an observation?
The two computers which are having the worst issues have been connected to the LAN via cat6 for the moment until this can be resolved as it is affecting work activities during the day etc... especially teams calls and general browsing.
Overall the whole network has around 25 clients, the majority of which are CCTV IP cameras connected via cat 6 (and a switch) to YARD1 or YARD2. The access is excellent to these both within the network and also via internet connection via 4G. Other devices (Sky Q and NAS drive) are working well within the confines of the LAN.
It is a shame as 1.6.5 worked very well and we had no issues, presumably we can regress the firmware back to 1.6.5 without any major headaches??
EDIT: Even one of the machines ive connected using cat6 is now having connection problems with web pages so not sure what is happening here?! This needs to be addressed as one would hope a firmware update would improve things and not the opposite? :o
- Copy Link
- Report Inappropriate Content
I have used 1.6.x for a very long time. It was always very stable.
I regret upgrading to 1.7.1.
I have three m5's arround the house. Ethernet backhaul.
They run in Accesspoint mode.
Since upgrading the deco's my IoT devices (also mainly ESP8266) drop connection 20 times a day.
Sometimes they connect back within 90 seconds. Sometimes it takes 90 minutes.
I also sometimes have difficulties using the app. When I open it, it is trying to connect to the network but with no luck.
This also only happend after 1.7.1.
All my wired connections that dont depend on TP-Link are rock solid.
I've disabled Beamforming.
I've disabled eco mode.
I rather not disable fast roaming.
Im using a local DNS (Adguard Home), and that is using Google's DNS (8.8.8.8, 8.8.4.4)
Everything else is default.
(running M5 v3 1.7.1 Build 20230608 Rel. 74023)
- Copy Link
- Report Inappropriate Content
@Er1 Yeah, that's one of the unfortunate things about 1.7.1 You MAY be able to obtain stability, but at the cost of arguably mesh's most important features...
- Copy Link
- Report Inappropriate Content
Thanks for the feedback.
I noticed you both mentioned ESP devices and I also randomly saw some similar feedback before. But so far, there hasn't been a complete solution yet.
@Nardol , could you please help me submit the APP log here:
@Er1, could you please refer to this link to set up connection alerts on Deco for the ESP devices, then help me submit the Deco APP which reported the online/offline time:
How to configure the Connection Alerts feature on the Deco app
Recently, I posted a beta firmware about RAM optimization on Deco X50/X55 and sometimes it made me think the reported issue on 1.7.1 might be related to it as well since more memory usage could be used for new features. Personally, I agreed with what @XWEBNetwork said about the conflict between new features and network stability. It might take a long to find a solution but I do hope the next firmware could find a balance between them.
Thank you very much and best regards.
- Copy Link
- Report Inappropriate Content
I am running in Accesspoint mode. To much of my network will get broken if I disable this.
Therefore I am not able to enable connection alerts / notifications.
I can provide you with the deco log file tho.
Home Asssistant reports this (to avoid getting a to long list these are the last 8 hours):
August 18, 2023
esp8266 became unavailable 14:17:11 - 27 minutes ago
esp8266 became online 14:16:19 - 28 minutes ago
esp8266 became unavailable 14:12:37 - 31 minutes ago
esp8266 became online 14:11:27 - 32 minutes ago
esp8266 became unavailable 14:04:10 - 40 minutes ago
esp8266 became online 14:02:09 - 42 minutes ago
esp8266 became unavailable 13:59:26 - 44 minutes ago
esp8266 became online 13:58:34 - 1 hour ago
esp8266 became unavailable 11:55:31 - 3 hours ago
esp8266 became online 11:54:55 - 3 hours ago
esp8266 became unavailable 11:53:54 - 3 hours ago
esp8266 became online 11:15:07 - 3 hours ago
esp8266 became unavailable 11:08:11 - 4 hours ago
esp8266 became online 11:07:36 - 4 hours ago
esp8266 became unavailable 11:06:30 - 4 hours ago
esp8266 became online 10:58:57 - 4 hours ago
esp8266 became unavailable 10:58:44 - 4 hours ago
esp8266 became online 09:43:52 - 5 hours ago
esp8266 became unavailable 09:42:46 - 5 hours ago
esp8266 became online 09:36:47 - 5 hours ago
esp8266 became unavailable 09:33:54 - 5 hours ago
esp8266 became online 09:30:28 - 5 hours ago
esp8266 became unavailable 08:02:53 - 7 hours ago
esp8266 became online 07:51:53 - 7 hours ago
esp8266 became unavailable 07:50:58 - 7 hours ago
esp8266 became online 07:43:43 - 7 hours ago
esp8266 became unavailable 07:43:32 - 7 hours ago
esp8266 became online 07:37:57 - 7 hours ago
esp8266 became unavailable 07:36:24 - 7 hours ago
esp8266 became online 07:34:41 - 7 hours ago
esp8266 became unavailable 07:31:58 - 7 hours ago
esp8266 became online 07:31:21 - 7 hours ago
esp8266 became unavailable 07:29:10 - 7 hours ago
esp8266 became online 07:27:45 - 7 hours ago
esp8266 became unavailable 07:16:13 - 7 hours ago
esp8266 became online 07:14:59 - 7 hours ago
esp8266 became unavailable 06:57:50 - 8 hours ago
esp8266 became online 06:40:00 - 8 hours ago
- Copy Link
- Report Inappropriate Content
Hi, Thanks for the details.
Actually, I was wondering whether you are able to make any adjustments to your network topology.
For example:
TL-WA901ND is 2.4Ghz only and When the Mesh connection went after the WDS bridge, its speed and stability would be reduced and the network ping latency would be highly increased.
Are you able to wire the kitchen Deco to the main Deco via Ethernet cable as well, then use the TL-WPA4220 Powerline connection between Kitchen Deco and Yard 1 Deco?
Basically, you have already tried almost all the troubleshooting suggestions, and if nothing improved, we could only wait for the next firmware upgrade, or we could try to downgrade back to 1.6.5 via firmware recovery.-https://community.tp-link.com/en/home/forum/topic/616452
(If you do plan to perform the firmware downgrade, please try to downgrade some of them first, like the main/kitchen/annex Deco just to make sure everything could go back to normal on 1.6.5.)
Thank you very much and best regards.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 14
Views: 207779
Replies: 844
Voters 6
