Official Release Deco M5 1.7.8
Current Release
For Deco M5(V1/V2/V3/V3.2)
Deco M5_1.7.8 Build 20240719 for All versions
Modifications and Bug Fixes:
1. Improve the device stability.
2. Enhance the system security.
3. Fixed the bug of Deco network disconnection after adding satellite Deco.
Note: We recommend all users upgrade to this firmware version for important security updates.
---------------------------------------------------------------------------------------------------
History 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.
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
Hardware Model: Deco M5 3.20 (us)
Number of Units (decos): Only one (1) unity (as router on pppoe mode)
Current version: Deco M5(US)_V3.20_1.7.1 Build 20230608
I live in small apartment with only one deco as main router (with pppoe mode):
On versions 1.61 and 1.65 (us model 3.20) The Deco M5 in general is very stable: (lan is perfect, and wlan wifi2&5 is perfect).
Since, 1,7.X versions, i have 3 disconnections per day wlan side (wireless 5ghz), lan is perfect!
Tp-Link engineers, please read my logs bellow and take note of my explanations: (I use voidlinux, and use wpa_supplicant in debugmode with a ax200 intel pci-e wireless adapter) POWER SAVE IS OFF and PCI is on MAX PERFOMANCE.
Disconnection Type 1: (3 beacon losts) without disconnect SSID session on wifi adapter:
2023-08-22T16:28:45.05991 daemon.notice: Aug 22 13:28:45 wpa_supplicant[750]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-22T16:28:45.16226 daemon.notice: Aug 22 13:28:45 wpa_supplicant[750]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-23T00:34:30.19308 daemon.notice: Aug 22 21:34:30 wpa_supplicant[758]: wlp2s0: CTRL-EVENT-BEACON-LOSS
Disconnection Type 2: (5 beacon losts or more) disconnecting SSID session on wifi adapter:
2023-08-22T16:28:45.05991 daemon.notice: Aug 22 13:28:45 wpa_supplicant[750]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-22T16:28:45.16226 daemon.notice: Aug 22 13:28:45 wpa_supplicant[750]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-23T00:34:30.19308 daemon.notice: Aug 22 21:34:30 wpa_supplicant[758]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-23T00:34:30.29555 daemon.notice: Aug 22 21:34:30 wpa_supplicant[758]: wlp2s0: CTRL-EVENT-BEACON-LOSS
2023-08-23T00:34:30.39786 daemon.notice: Aug 22 21:34:30 wpa_supplicant[758]: wlp2s0: CTRL-EVENT-BEACON-LOSS
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=30:de:4b:48:XX:XX reason=4 locally_generated=1
When this beacon losts occur? (logs on debug mode on deco M5v3.20 US)
When MESH (daemon), scan all devices on wireless network to measure wifi signal of clients for realize the deco swap. (with 2 or 3 decos). On my case, with only 1 unity, (disable mesh mode on all clients in deco app), this problem occur with low frquency. And i discover after 1 or 2 days without found wifi mesh clients (with mesh mode disable set on deco app), this daemon enter in sleep mode and the deco operates perfect, like 1.6X firmware versions.
I will generate the log on deco M5, when the problem occur and post bellow:
Please, Waiting for I catch the entries and post here... (to be continued)
SUGESTION FOR DECO ENGINEERS OF M5 FIRMWARE: (PLEASE READ)!
Because Deco Mesh system uses ARP protocol to generate temporary client keys and and use a daemon to measure the signal, the beacon interval time value dont be set as Beacon Interval = 1, as default tplink routers (without mesh), like Archer c6v3, Archer C9v2 (my old tplink routers).
Increase the beacon interval time to Beacon Interval = 2 OR 3, will give to deco m5 more time to wifi clients respond and more time to mesh daemon do a network scan, renew arp generate wifi keys without disconnect wifi clients. (or other decos)
- Copy Link
- Report Inappropriate Content
Ive reverted back to firmware 1.6.1 via the recovery tool.
I am still experiancing drops. Still mainly of the esp8266/esp32 devices.
I factory reset all Deco's one by one.
Network is on the same channel it was on a months ago (before issues).
Since ive also read that some devices battery drain faster since the update I suspect that perhaps the radio rom also had been updated. And that this update persists, even while downgrading. Regardless of the regular deco firmware.
I also notice on for example my phone, wich does not have connection issues that the signal strenght is reduced.
Coult it be that since firmware 1.7.1 the transmission power has been reduced?
- Copy Link
- Report Inappropriate Content
@Er1 no, im in router Mode.
- Copy Link
- Report Inappropriate Content
If you are in accespoint mode:
"NOTE: The Connection Alerts feature is not available when Deco works in AP mode."
https://www.tp-link.com/en/support/faq/3022/
- Copy Link
- Report Inappropriate Content
i have 4 Deco M5 with firmware Deco M5_1.7.1_Build 20230608 but Connection Alert not working. This is a bug into app/firmware or M5 don't have this function anymore?
- Copy Link
- Report Inappropriate Content
@David-TP No problem, log submitted.
About another subject, I have a Nuki smart lock, the 3.0 pro model and I notice a lot of disconnections.
Fortunately the smart lock reconnect quickly and I can use MQTT again.
Nuki have made some optimisation in firmware but I still observ the same disconnections.
Someone at Nuki told me the following: "You could try changing your WiFi DTIM interval to 3 if your router allows it. In combination with the “Medium” power saving setting this will lead to the Smart Lock not skipping anything on the network."
Unfortunately, it is not something we can change with Deco except if I miss-understood something.
Do you think a solution could be found? Because I am pretty sure I am not the only person who use a Nuki smart lock 3.0 pro on a Deco network.
When I connect my smart lock using other network, I don't observe any disconnection.
- 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
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
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
@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
Information
Helpful: 14
Views: 313121
Replies: 866
Voters 5
