Official Release Deco X50/X55_V1_1.5.5 Support WireGuard VPN, Client Speed Limit and Fixed WAN Port
This Article Applied to
Deco X50/X55_V1_1.4.1
Firmware Modifications
1. Support WireGuard VPN Server/Client.
2. Support built-in easy configuration of NordVPN/Surfshark VPN.
Note: In compliance with local regulations, the Third-party VPN feature may be restricted in specific regions.
3. Add client speed limit under clients' detailed setting page.
4. Support Fixing the WAN port under Deco APP>More>Advanced>WAN Port.
5. Add Scene Priority under QOS.
6. Add Client MAC Identification to improve the accuracy of device detection.
7. Add more device icons in the Deco APP.
Download Link
Deco X50_V1 | Deco X50_V1_1.5.5- updated 2024.8.12 |
Deco X55_V1 | Deco X55_V1_1.5.5- updated 2024.8.12 |
Note:
1. *According to the user feedback and our further test, this 1.5.1 version does not support reverting to 1.4.1 via downgrade firmware recovery directly.
-Ever since 1.3.0, the firmware bin file has been over 32MB which passes the maximum file size of the HTTP uboot upgrade tool. So if you want to revert to 1.4.1, please refer to the following suggestions:
- Still run a firmware recovery on one of the satellites Deco X50 first.
- Try to upload an older official version, 1.2.2_Build_230301.zip for example,
- Then update to 1.4.1 from 1.2.2 via web UI.
- If this process works for the satellite Deco X50, We could repeat it on the main Deco later.
2. Please make sure the Deco APP is up-to-date.
3. Some features might not be available when there are other models in the Mesh network.
Configuration Procedure for the Newly-added Features
WireGuard VPN Server& Client
NordVPN/Surfshark VPN
-
NordVPN
-
Surfshark
Client Speed Limit
Manual Selection of the WAN Port
Set Scene Priority under QOS
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, Thanks for the notification.
The release of the official 1.5.0 firmware for Deco X50 was indeed delayed a little bit. We now have a new beta firmware available that addresses the reported instability issue. Initial tests by users have been positive. If all continues to progress smoothly, I plan to update the community with the latest beta firmware within the next week.
Thank you very much and best regards.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@David-TP
I've just checked my email inbox and found that I receive a new beta firmware for the X50
1.5.0 Build 20240407 Rel. 36755
Updated it yesterday, and found out a few things that I find it should be reported.
- CPU usage % keeps fluctuating and at times can even reach close to 100%
- The Main node feels hot and uncomfortable to touch despite minimal load usage during sleeping hours.
- Despite the fact that I've turned off QOS and Scene Priority,I initially suspecting that it is causing the Deco to work extra hard. There is no VPN server/clients running, no parental control running at all. Also removed Speed Limits on my Tapo Cams.
- While checking the WEB UI, and concurrently through Deco App, the CPU usage % shot up and cause my other nodes to show as offline as if it is lagging to send a signal to show that it is working.
Here are the logs that I manage to get (can't upload as it keeps showing failure),video attached for your reference.
Sun Apr 14 02:45:32 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:32 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:32 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:32 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:32 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:32 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:33 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:33 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:33 2024 user.err : Error: Received TDP packet with error code 01
Sun Apr 14 02:45:33 2024 daemon.err wandetect3: [test] carrier = 1, carrier_type = 0
Sun Apr 14 02:45:34 2024 user.notice root: [safesearch] insert kmod if needed
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:34 2024 user.notice root: [safesearch] iptables -w -F block_dot
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:34 2024 user.notice root: [safesearch] reload
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:34 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:35 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:35 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:36 2024 daemon.err wandetect3: [test] carrier = 1, carrier_type = 0
Sun Apr 14 02:45:36 2024 daemon.notice pppd[2407]: len < 0
Sun Apr 14 02:45:36 2024 daemon.notice netifd: internet (2407): len < 0
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:37 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:38 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:38 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
Sun Apr 14 02:45:38 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:38 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:38 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:38 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:39 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:39 2024 daemon.err tmpsvr[3251]: Error: tdp_trans_relay
Sun Apr 14 02:45:39 2024 kern.emerg the module failed
Sun Apr 14 02:45:40 2024 daemon.err tmpsvr[3251]: Error: memfree less than 15000 KB
Sun Apr 14 02:45:40 2024 daemon.err tmpsvr[3251]: Error: tmp_trans_relay
I will be providing support with a video recording and further logs to notify them about this occurrence.
So far, no more WAN PPPOE disconnection as per the previous beta firmware that was posted on first page.
- Copy Link
- Report Inappropriate Content
just experience the same issue a while back.
Deco LED did really change from green to red within a few seconds .
This happened when i turned off AUTO WAN/LAN, and set the specific ports to be my WAN port linking to my ISP modem.
and when this happens, I went back to the option to check, and to see the option being set to Enabled back by itself. Further clicking it to re-set back the port will only show up 2-port to be selected where else I'm actually using a X50 with 3 ports.
I am not running any network switches, just only one cat 6 cable linking to my other X50 node
- Copy Link
- Report Inappropriate Content
Tapo TC70 Cameras failure to register on IoT SSID network when I reset the entire network and try pairing it again with Tapo app and Deco app starting from a fresh firmware on 1.5.0 Build 20240407 Rel. 36755 after a hard reset due to the previous WAN disconnection error.
Thought resetting and start setting up Deco from scratch will solve but instead I found a whole load of new headaches and troubles. Oh boy, how wrong was I.
No matter what I did
-turned off fast roaming (beamforming didn't showed up as I have a X20 on my network topology)
-set WPA/WPA2 only on both SSID
-trying to get the camera connect back to Main Network SSID with only 2.4Ghz turned on, also failed to pair.
-network optimization done
-turning on off 2.4/5Ghz on main network and IoT network
-even the previously paired cameras had difficulties getting connected back to the IoT SSID even when I purposely set up the exact same IoT network with the same password and security authentication protocol as how I did with previous stable 1.4.1 firmware.
-trying to pair it back on the main network even with 2.4Ghz, the Tapo app keeps showing my camera is only loading to pair to the network and will never proceed to successful pairing at all!
-This wasn't the case at all, when I was using 1.4.1 firmware, no matter how many times I reset the network, as long my IoT network is configure the same as how I paired with details for the cameras, it will automatically connect itself back to the SSID.
-This wasn't the case for my smart bulbs L530. Funny.
I'm done with this new beta firmware features, until TP-Link really get it sorted out, I had enough of those new features. No point testing it out with all of this bugs around.
With every new update comes with heap loads of features that may or may not work, and accompanied by weird bugs and errors.
- Copy Link
- Report Inappropriate Content
@David-TP Thank God, the new firmware is running well again. However, I haven't seen any clients in the app since the night. But I haven't restarted the router yet, but I've already shot down the app several times.
- Copy Link
- Report Inappropriate Content
@David-TP
Hi David, just wanted to update here that the recent beta firmware I receive promptly from Tp Link support is stable and has not faced any disconnection issues ever since 3 days ago.
However, I will monitor the network to see if it disconnects and changes my IP address as how the previous firmware did.
Everything is running in order currently and no minor bugs or that I couldn't discover yet.
Thank you once again for the prompt update to solve the X50 buggy issues.
- Copy Link
- Report Inappropriate Content
Same goes for me. With the newer version you provided I don't have any issues and everything is working as expected.
- Copy Link
- Report Inappropriate Content
@David-TP Is it normal that updating the online devices sometimes takes more than 20 seconds when opening the app?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 37870
Replies: 196