Deco XE75 v1 fw 1.4.3 — same disconnection issue as topic/738406, requesting beta firmware

Deco XE75 v1 fw 1.4.3 — same disconnection issue as topic/738406, requesting beta firmware

Deco XE75 v1 fw 1.4.3 — same disconnection issue as topic/738406, requesting beta firmware
Deco XE75 v1 fw 1.4.3 — same disconnection issue as topic/738406, requesting beta firmware
a week ago
Model: Deco XE75  
Hardware Version: V1
Firmware Version: 1.4.3 Build 20240926 Rel. 38336

Hello David-TP and TP-Link team,

I am experiencing the same issue described in topic/738406 (ThatGuy015) where you mentioned a beta firmware for Deco XE75 v1 that "optimized the 2.4 GHz connection by disabling the 2.4 GHz backhaul among Decos and allowing different Decos to use non-overlapping 2.4 GHz channels for mobile devices".

I would like to request access to that beta firmware. Below are my setup, evidence, and what I have already tried.

Setup

  • 3x Deco XE75 v1 (one main, two satellites)
  • Firmware 1.4.3 Build 20240926 Rel.38336 on all nodes
  • Ethernet backhaul active on all 3 nodes (verified in Deco app)
  • Region: EU (Italy)
  • Operating mode: Access Point (Decos behind an upstream router on 192.168.1.1)
  • Mixed clients: iPhones, Android phones, tablets, IoT (smart plugs, bulbs, robot vacuum, smart TVs), Linux laptops, Windows laptops

Symptoms

1. Frequent micro-drops on multiple devices during real-time activities (WhatsApp voice/video, video calls). Same as ThatGuy015: some devices drop dozens of times per hour, signal strength is excellent.

2. Continuous band-bouncing on stationary devices. One iPhone (XX:XX:XX:c1:f1:4f) switches between 5 GHz (wl02) and 2.4 GHz (wl22) dozens of times in 2 hours while sitting still in the same room. Example from main Deco log:

10:35:19  associate wl22
10:35:29  disassociate wl22
11:57:22  associate wl22
11:57:53  disassociate wl22
11:59:53  associate wl02
12:05:56  associate wl22 / disassociate wl02
...

3. Spontaneous roaming events on stationary clients overnight. From main Deco log between 02:35 and 08:15 (clients on charger, not moving):

stadbUpdateAssoc: Station XX:XX:XX:XX:DD:23 roams itself
stadbEntry_updateARBtmThreshold: update threshold ... reason 2
ar_config_set_thres: Null thres!

Multiple clients show associate / disassociate cycles every 30 to 60 seconds, with Null thres! warnings each time. Example sequence at 08:06-08:09:

08:06:32  XX:XX:XX:XX:DD:23 associate wl22
08:07:19  disassociate (Station roams itself, Null thres!)
08:07:49  associate again
08:08:45  disassociate (roams itself, Null thres!)
08:09:22  final disconnect

4. Recurring 802.11k / band-steering errors in the log:

estimatorDot11kIterateCB: Timeout waiting for 802.11k response
steeralgFindBestAPCallback: targetBand(X) != measuredBss->band(Y)
ar_pat_calc_cand_datarate: Cannot find <BSSID> in apinfo list

5. Deco app "Network Optimization" keeps changing the 2.4 GHz channel between 3, 4 and 5, never settling. It reports "channel 36 perfect" on 5 GHz, but an external scan shows all my Decos share channel 36 (see below).

External RF evidence (Linux laptop scan, fixed position)

2.4 GHz — 5 Deco BSSIDs all on channel 3:

XX:XX:XX:3b:3c:e6  ch 3  -55 dBm  "MyWiFi"
XX:XX:XX:3b:3c:e7  ch 3  -55 dBm  "MyWiFi 2.4"
XX:XX:XX:00:32:60  ch 3  -59 dBm  (hidden)
XX:XX:XX:00:32:61  ch 3  -62 dBm  "MyWiFi"
XX:XX:XX:00:32:62  ch 3  -60 dBm  "MyWiFi 2.4"

5 GHz — all Deco BSSIDs on channel 36:

XX:XX:XX:3b:3c:e7  ch 36  -53 dBm  (satellite A)
XX:XX:XX:00:32:6a  ch 36  -55 dBm  (satellite B)

This is co-channel interference between my own Deco nodes. The Network Optimization tool does not detect it because it does not see its own BSSIDs as external interference.

Independent monitoring

I run independent diagnostics outside the Deco system:

  • SmokePing on a wired Proxmox container probing gateway, DNS, and WAN targets for 6+ hours: 0% packet loss, sub-millisecond jitter. The wired LAN and the ISP are completely clean.
  • systemd Wi-Fi monitor on two stationary Linux laptops (Mint + Pop_OS), each connected to a different Deco satellite, logging RSSI, BSSID, bitrate and retries every 5 seconds. Both record band-bouncing and roaming events while the laptops never move.

The problem is isolated to the Deco Wi-Fi layer.

Cross-check with an alternative AP

To rule out client-side issues I temporarily activated a separate 802.11g AP (different hardware, channel 11, isolated SSID). My S25 Ultra phone made a WhatsApp voice call lasting more than 12 minutes with zero drop on that AP. The issue is not phone-specific — it is on the Deco side.

What I have already tried

  • Network Optimization (multiple times)
  • Disabled Fast Roaming
  • Disabled Beamforming
  • Power-cycled all Decos
  • DHCP reservations / static IPs for problem devices
  • Verified Ethernet backhaul on all 3 nodes
  • Verified ISP and upstream router via independent SmokePing baseline
  • Tested with an alternative AP (problem absent)
  • Verified the issue is not phone-specific (occurs on iPhone, Android, Linux laptops, IoT devices)

Request

Could you please send me the beta firmware referenced in your reply on topic/738406:

"there is a beta firmware for Deco XE75_v1, which has optimized the 2.4 GHz connection by disabling the 2.4 GHz backhaul among Decos and allowing different Decos to use non-overlapping 2.4 GHz channels for mobile devices. (It could revert to the official 1.4.1 directly via web UI)"

I am happy to provide:

  • Full system logs from all 3 Decos
  • Deco app network map screenshots
  • SmokePing 24-hour baseline graphs
  • Linux Wi-Fi monitor event logs
  • Before/after comparative tests once the beta is installed

Thank you very much for your support.

Best regards, Frappo

1
1
#1
4 Reply
Re:Deco XE75 v1 fw 1.4.3 — same disconnection issue as topic/738406, requesting beta firmware
Wednesday

  @Frappo 

Hi, 
I have sent the requested firmware to you via a private message. You can update the firmware via the web UI and check if it helps.
How to Update TP-Link Deco Firmware
Best Regards

0
0
#2
Re:Deco XE75 v1 fw 1.4.3 — same disconnection issue as topic/738406, requesting beta firmware
Friday

Hi  @Solla-topee 

I would like to add my own Deco XE75 V2 logs because they seem to point in the same direction as this report.

 

My setup uses Ethernet backhaul, but the logs still show repeated 802.11k / RRM / BTM steering activity, including for stationary clients.

 

The most concerning patterns are:

 

steerexecStartSteer: Starting new steer for [client]

targetBand(1) != measuredBss->band(0)

estimated pat datarate is 0

Timeout waiting for 802.11k response

Failed to initiate 11k measurement

bcnrpt_append_chan_report: don't find regclassnum

qca_send_rrm_beacon_req : fail to append channel report

Beacon report for STA ... in unexpected state 2

 

One affected client is a stationary LG webOS TV. It is not moving around the house, but Deco keeps running steering logic against it.

 

My logs also show different 2.4 GHz channels per Deco node:

 

channel_2g:10 channel_5g:40 channel_6g:37

channel_2g:3 channel_5g:40 channel_6g:37

channel_2g:6 channel_5g:40 channel_6g:37

 

So even if per-node 2.4 GHz channel separation is active, there still seems to be a steering / 802.11k / RRM issue.

 

Could you please clarify:

 

1. Why is Deco repeatedly trying to steer stationary clients in Ethernet backhaul mode?

2. What does "targetBand(1) != measuredBss->band(0)" mean?

3. Why does "estimated pat datarate is 0" appear before steering decisions?

4. Are the 802.11k/RRM errors above expected, known, or considered firmware bugs?

5. Does Stable Mode affect only wireless backhaul, or also client steering, BTM, 802.11k/RRM and AP selection?

 

Thanks in advance 

 

This does not look like a generic interference issue. It looks like Deco’s closed radio-management logic is making decisions that users cannot audit, tune or disable.

0
0
#3
Re:Deco XE75 v1 fw 1.4.3 — same disconnection issue as topic/738406, requesting beta firmware
Friday
I also checked the logs from the two satellite Deco XE75 V2 units. They add one important detail: both satellites detect Ethernet backhaul: ethstatus=1,set meshmode_2g 0 meshmode=0, meshstate=1 But even with Ethernet backhaul active, they still keep running automatic 2.4 GHz radio-management logic: get fap channel_2g:5 pick channel---2 pick channel---10 target_chan=2/10, cur_chan=2/10 So the satellites are not simply “wired APs”. Deco is still actively managing per-node 2.4 GHz channel behavior. The logs also repeatedly show: fail to get ptr record_mode fail to get record_channel_2g record_mode fail to get auto_bandwidth record_mode uci get record_channel_2g=0 uci get bandwidth_2g=2 Could you please clarify what "record_mode" is, why it fails repeatedly, and which configuration source actually controls 2.4 GHz channel and bandwidth in Ethernet backhaul mode? One satellite also shows repeated 802.11k measurement timeouts and "Failed to get uplink rssi" for the same client, plus a "targetBand(1) != measuredBss->band(2)" mismatch. Thanks again
0
0
#4
Re:Deco XE75 v1 fw 1.4.3 — same disconnection issue as topic/738406, requesting beta firmware
Yesterday

  @Nicosilva86 

Hi, 
What specific problems did you encounter while using the Deco XE75 V2? The logs on the Deco web UI may not be relevant to the actual problems you are experiencing. We suggest you describe the specific issues so that we can provide appropriate advice.
Best Regards

0
0
#5