Home

Forums

Stories

Knowledge Base

Home Network Community > Deco > X50 wifi not working after 1.4.1 upgrade

< Deco

X50 wifi not working after 1.4.1 upgrade

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

X50 wifi not working after 1.4.1 upgrade

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

OvelhaNegra

2024-01-16 12:42:56 - last edited 2024-01-16 12:56:43

Posts: 12

Helpful: 4

Solutions: 0

Stories: 0

Registered: 2024-01-13

X50 wifi not working after 1.4.1 upgrade

2024-01-16 12:42:56 - last edited 2024-01-16 12:56:43

Model: Deco X50

Hardware Version: V1

Firmware Version: 1.4.1

I have instability issues since the upgrade to the latest 1.4.1 firmware.
I have 30+ wifi clients, on the previous version had no issue with none.

I run in three x50 in AP mode, all ethernet connected.

X50(1.0) Current firmware: 1.4.1 Build 20231122 Rel. 40485

Tried the following firmwares, all failed to downgrade using the uboot method:
- X50 1.0_en_1.3.1 Build 20230824 Rel. 74320_US_EU_CA_JP_up.bin
- X50v1_en_1.3.0 Build 20230719 Rel. 45755_US_EU_JP_CA_up.bin
- X50 1.0_en_1.2.7 Build 20230620 Rel. 31797_US_EU_CA_JP_up.bin

The problem seems to affect only with the 2.4 band.

I have a lot of Tasmota and Shelly devices (ESP based).
Not even my even my 6 Tapo C210 cameras work properly with this firmware version.

During the weekend I tried all:
- Disable Roaming
- Disable Beamforming
- Delete the network + Factory reset all AP
- Replacing all the cables to the Access Points.
- Reflashed again 1.4.1 (this is the ONLY firmware it allows to be flashed now)

I had to redeploy my older AP points.
The ONLY way to have SOME stability is to have ONLY ONE x50 connected and powered on.

Nevertheless the issue are the following:
- Difficulty to connect to the network
- Once connected very high latency times (even for devices within 1m of the AP)
- Ping shows random packet losses (more than 50%)

The product is completely faulty.
How can I revert back to an older firmware ?
Otherwise I would like to RMA the product as the 1.4.1 firmware has broken it's functionality.

Look at this beautiful output from ping..

Packet loss and 3secs response time for a device which is about 1m away from the access point.

Reply from 192.168.1.234: bytes=1500 time=839ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=16ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=653ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=994ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=1394ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=2673ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=470ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=1862ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=3398ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=1484ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=1805ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=2871ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=3834ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=3179ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.234: bytes=1500 time=3845ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.234: bytes=1500 time=3928ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=3236ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=179ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=1632ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=245ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=2508ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.234: bytes=1500 time=939ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=1358ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.234: bytes=1500 time=3245ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.234: bytes=1500 time=291ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=948ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=936ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=479ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=1114ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=1482ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=95ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=2089ms TTL=64
Reply from 192.168.1.234: bytes=1500 time=2486ms TTL=64

4 Reply

David-TP

2024-01-17 03:02:25

Posts: 12476

Helpful: 1724

Solutions: 1200

Stories: 9

Registered: 2020-04-14

Re:X50 wifi not working after 1.4.1 upgrade

2024-01-17 03:02:25

@OvelhaNegra

Hi, Thank you very much for the feedback and I also got your email.

Have you tried to enable "IOT Network" for 2.4 GHz only and set these 2.4 GHz devices connected to the nearby Deco X50 via connection preference?

Then please also try to disable "Mesh Technology" on the Deco APP for these devices.

Wait for your reply and best regards.

▶Check What's Currently Going on With Deco ▶Deco Starts Supporting Changing Wireless Channels! Deco BE85_1.1.1 Supports WireGuard VPN,Channel Selection and Matter Deco BE65_V2_1.1.0 Supports WireGuard VPN, Channel Selection and More ▶Deco APP 3.8.102/3.8.112-Ready for A New Deco Onboarding Experience! Try to leave a Message if urgent help is required.

OvelhaNegra

LV1

2024-01-17 11:43:52

Posts: 12

Helpful: 4

Solutions: 0

Stories: 0

Registered: 2024-01-13

Re:X50 wifi not working after 1.4.1 upgrade

2024-01-17 11:43:52

@David-TP Thanks for reading. I'm a bit frustated by now.

I've migrated all "IOT" devices to my previous AP. The only devices left on the x50 are the following:

2.4 band: Tapo C210 (6 units), Printer (1 unit)

5.0 band: Apple stuff (4 units), Google TV (4 units), Laptops (3 units)

I've disabled Mesh for the Tapo devices, the overall instability issue remains on the 2.4 band.

All the AP are connected using a 1Gbps uplink.

I've taken a laptop (wireless client) and a desktop (ethernet server) and run a couple of iperf tests.

Forced the laptop into the 5.0 band: $ iperf3.exe -c 192.168.1.2
Connecting to host 192.168.1.2, port 5201
[  4] local 192.168.1.197 port 60006 connected to 192.168.1.2 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  48.1 MBytes   404 Mbits/sec
[  4]   1.00-2.00   sec  57.8 MBytes   484 Mbits/sec
[  4]   2.00-3.00   sec  57.6 MBytes   483 Mbits/sec
[  4]   3.00-4.01   sec  56.4 MBytes   470 Mbits/sec
[  4]   4.01-5.00   sec  53.8 MBytes   453 Mbits/sec
[  4]   5.00-6.00   sec  53.1 MBytes   446 Mbits/sec
[  4]   6.00-7.00   sec  53.9 MBytes   452 Mbits/sec
[  4]   7.00-8.00   sec  57.8 MBytes   485 Mbits/sec
[  4]   8.00-9.00   sec  60.0 MBytes   502 Mbits/sec
[  4]   9.00-10.01  sec  52.0 MBytes   431 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-10.01  sec   550 MBytes   461 Mbits/sec                  sender
[  4]   0.00-10.01  sec   550 MBytes   461 Mbits/sec                  receiver

iperf Done.

Then forced the laptop into the 2.4 band:$ iperf3.exe -c 192.168.1.2
Connecting to host 192.168.1.2, port 5201
[  4] local 192.168.1.197 port 60039 connected to 192.168.1.2 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.01   sec   256 KBytes  2.09 Mbits/sec
[  4]   1.01-2.01   sec  0.00 Bytes  0.00 bits/sec
[  4]   2.01-3.00   sec  0.00 Bytes  0.00 bits/sec
[  4]   3.00-4.01   sec  0.00 Bytes  0.00 bits/sec
[  4]   4.01-5.01   sec  0.00 Bytes  0.00 bits/sec
[  4]   5.01-6.01   sec  0.00 Bytes  0.00 bits/sec
[  4]   6.01-7.00   sec  0.00 Bytes  0.00 bits/sec
[  4]   7.00-8.01   sec  0.00 Bytes  0.00 bits/sec
[  4]   8.01-9.01   sec  0.00 Bytes  0.00 bits/sec
[  4]   9.01-10.01  sec  0.00 Bytes  0.00 bits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-10.01  sec   256 KBytes   210 Kbits/sec                  sender
[  4]   0.00-10.01  sec  34.2 KBytes  28.0 Kbits/sec                  receiver

iperf Done.

I've been running this Deco x50 topology since May 2022.. I was happy with the platform, no complains.

I never upgraded the firmware since the initial installation in May, that's how stable things were.

Then I decided to click that "upgrade firmware" button on the mobile application..

OvelhaNegra

LV1

2024-01-18 20:53:39

Posts: 12

Helpful: 4

Solutions: 0

Stories: 0

Registered: 2024-01-13

Re:X50 wifi not working after 1.4.1 upgrade

2024-01-18 20:53:39

As suggested here https://community.tp-link.com/us/home/forum/topic/646686?replyId=1307900.

I only tried reflashing 1.4.1 on my main x50 using the uboot method.

The UI reported all three units at version 1.4.1, so I never tried to flash any other AP.

I forced flashed 1.4.1 into all of them, one by one and since then the 2.4 band seems usable again.

Let's see how it holds when I start moving back all the clients.

David-TP

2024-01-19 10:11:11

Posts: 12476

Helpful: 1724

Solutions: 1200

Stories: 9

Registered: 2020-04-14

Re:X50 wifi not working after 1.4.1 upgrade

2024-01-19 10:11:11

@OvelhaNegra

Hi, Thanks for the update.

Did you receive my email from support.forum@tp-link.com?

The engineer would like to help us to run further tests to locate the issue. If you are okay with the remote assistance, you could reply to the email to schedule a proper time.

Wait for your reply and best regards.

X50 wifi not working after 1.4.1 upgrade

X50 wifi not working after 1.4.1 upgrade

Information

Voters 2

Tags