Dashboard: WiFi Performance: 5GHz client miscounted into 2.4GHz on Channels tab

[kateatlinksys]

Reproduce steps:

1. Login to Linksys Now.
2. Connect one client to 2.4GHz and one to 5GHz (single router, no mesh).
3. Go to Dashboard > WiFi Performance > Channels tab.

Actual result:
The 5GHz client is counted under 2.4GHz — Channels shows "2.4GHz: 2 clients / 5GHz: 0 clients" and the donut is 100% 2.4GHz. (Signal tab lists both clients correctly, so the data is present.)

Expected result:
"2.4GHz: 1 client / 5GHz: 1 client", donut split accordingly.

Env.: M60DU-EU / Pinnacle 2.0 FW 1.2.2.26062820 / Linksys Now 2.5.0.700525

Log:

GUI_wifiperformance_error_0715.txt

Screenshot:

[AustinChangLinksys]

🔍 Automated investigation (preliminary triage)

Line: 2.x / USP (TR-369)

Root cause:

• Trigger (firmware side): the Device.WiFi.AccessPoint.*.AssociatedDevice.* table never populates AccessPoint.2 (the 5GHz AP). Both connected clients are always reported under AccessPoint.1 (the 2.4GHz AP), even though other firmware tables (Device.Hosts.Host.*.Layer1Interface and the DataElements STA table) do reflect a 5GHz association.
• UI defect: the Channels tab resolves each client's band solely through the chain AssociatedDevice → parent AccessPoint → SSIDReference → SSID.LowerLayers → Radio.OperatingFrequencyBand. Because every AssociatedDevice entry the firmware returns hangs off AccessPoint.1, every client resolves to Radio.1 = 2.4GHz. There is no cross-check against the more reliable Hosts.Layer1Interface, so the miscount goes uncorrected.

Evidence (from attached log.txt):

1. The AssociatedDevice GET returns both client MACs under AccessPoint.1 and nothing under AccessPoint.2 (L1038-1039). A repo-wide scan of the whole log finds zero AccessPoint.2.AssociatedDevice.*.MACAddress keys:

"Device.WiFi.AccessPoint.1.AssociatedDevice.1.MACAddress": "XX:XX:XX:XX:4c:c4",
"Device.WiFi.AccessPoint.1.AssociatedDevice.2.MACAddress": "XX:XX:XX:XX:a7:b8",

2. The band-resolution chain the UI follows: Radio band map + SSID→Radio links (L920-921, L975-978). AccessPoint.1 → SSID.1 → Radio.1 = 2.4GHz, so both clients above collapse to 2.4GHz:

"Device.WiFi.Radio.1.OperatingFrequencyBand": "2.4GHz",
"Device.WiFi.Radio.2.OperatingFrequencyBand": "5GHz",
"Device.WiFi.SSID.1.LowerLayers": "Device.WiFi.Radio.1",
"Device.WiFi.SSID.2.LowerLayers": "Device.WiFi.Radio.2",

3. Firmware DOES know one client is on 5GHz — the Hosts table reports it on Radio.2 (L2967) while the AssociatedDevice subtree for AP.2 stays empty (L2991 points at an instance whose MACAddress never appears):

"Device.Hosts.Host.6.Layer1Interface": "Device.WiFi.Radio.2",
"Device.Hosts.Host.6.AssociatedDevice": "Device.WiFi.AccessPoint.2.AssociatedDevice.1",

This is why the Signal tab (which reads different data) lists both clients correctly while the Channels tab does not.

Confidence: Medium — the AssociatedDevice table populated by firmware directly contradicts the Hosts/DataElements tables; firmware-side confirmation is needed on why AccessPoint.2.AssociatedDevice never lists the 5GHz client. The UI is also brittle for relying on a single band source with no fallback.

---

Auto-generated triage by Austin's tooling, pending Austin's review. Not a fix commitment.