Deco X1500 Mesh instability – cfg80211 -19 errors / nrd AP sync timer

Deco X1500 Mesh instability – cfg80211 -19 errors / nrd AP sync timer

Deco X1500 Mesh instability – cfg80211 -19 errors / nrd AP sync timer
Deco X1500 Mesh instability – cfg80211 -19 errors / nrd AP sync timer
3 hours ago
Model: Deco X1500  
Hardware Version: V1
Firmware Version: 1.3.0 Build 20250725 Rel. 54254

Hello,

 

I am experiencing persistent Wi-Fi instability with my TP-Link Deco mesh system, despite running the latest firmware and performing extensive troubleshooting.

 

Configuration:

  • 3 × Deco X1500 (indoor units)

  • 1 × Deco X50 Outdoor (currently removed from the mesh for testing)

  • Operating mode: Access Point

  • Vertical house (Ground floor / 1st floor / 2nd floor)

  • Wireless backhaul only (no Ethernet)

  • Firmware: latest available via Deco app

 

Symptoms:

  • Regular Wi-Fi freezes every few minutes (15–30 seconds)

  • Client disconnections

  • Issue reproducible even with the Deco X50 Outdoor completely powered off

 

System logs observed repeatedly:

  • rtk_get_vap_status: cfg80211 return -19

  • ar_apinfo_collect: AP sync timer expires!

  • Frequent VAP recreation

  • Abnormal activity from the mesh controller daemon nrd

  • 802.11k measurement timeouts and forced roaming events

 

Tests already performed:

  • Full removal of the Deco X50 Outdoor from the mesh

  • Factory reset and full reconfiguration

  • Fast Roaming / Band Steering / Beamforming disabled

  • Preferred connection fixed between Deco units (2nd → 1st → Ground floor)

  • Tests with and without Ethernet backhaul (the issue disappears immediately when at least one Ethernet backhaul link is present)

 

Conclusion:
This strongly appears to be a firmware issue in the wireless mesh implementation (nrd / Realtek cfg80211 driver) when three or more Deco X1500 units operate with wireless backhaul, especially in a vertical topology.

 

Could you please:

  1. Confirm whether this issue is known for the Deco X1500 series?

  2. Advise if a firmware fix, beta firmware, or stable older version is available?

  3. Escalate this case to the firmware / mesh development team?

 

I can provide:

  • Full system logs

  • Exact timestamps

  • Network topology diagram

 

Thank you in advance for your assistance.

 

Best regards,

Sébastien

  0      
  0      
#1
Options