[Topology] Click master node show client's information

[JohnnyWuLinksys]

Description
Click master node on topology page, it leads to client device information instead of master node
log-2026-07-15_17_03_07_topology_master_information_not_correct.txt

Steps

1. Menu > Topology
2. Click master node

Current result
Show device information

Expected result
Show master information

Information
Pinnacle 2.0 FW: 1.2.2.26062820
Linksys Now Version: 2.5.0.700525

Severity
S3

[AustinChangLinksys]

🔍 Automated investigation (preliminary triage)

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

Root cause:

• UI defect: The master (gateway) node in the topology is rendered as MeshNodeType.gateway, and tapping it opens a floating detail panel whose "Details" button navigates to RouteNamed.uspNodeDetail (onDetailsTap in node_detail_popup.dart). However, the log shows navigation landed on uspDeviceDetail with a {mac: ...A3:89} argument — i.e. the client device-detail route, not the node-detail route. This means the tapped element was treated as a client, so the client MAC (...a3:89, Host.1 = client) was passed instead of the master node's deviceId. The topology's node-vs-client routing (_navigateByNodeId type check / node registry mapping in usp_topology_view.dart) is mis-classifying or mis-wiring the master node's tap target.

Evidence (from attached log.txt):

1. Backend reported the roles correctly — Host.3 is master, Host.1/2 are client (USP Device.Hosts GET, no error):

"Device.Hosts.Host.1.DeviceRole": "client",
"Device.Hosts.Host.2.DeviceRole": "client",
"Device.Hosts.Host.3.DeviceRole": "master",
"Device.Hosts.Host.3.FriendlyName": "Community00014",
"Device.Hosts.Host.3.ModelName": "M60CF-EU",
"Device.Hosts.Host.1.PhysAddress": "XX:XX:XX:XX:a3:89",
"Device.Hosts.Host.3.PhysAddress": "XX:XX:XX:XX:56:76",

2. TopologyBuilder collapsed to a non-mesh view (single-node network), so the master is the gateway node and there are no slaves:

[D][USP][TopologyBuilder]: hasMesh=false, slaveNodes=0, slaveDeviceIds=[]
[D][USP][TopologyBuilder]: Device Pixel-8a hasMesh=false, parentNodeId=XX:XX:XX:XX:56:76 → gateway

3. The actual navigation after the tap went to the client device-detail route carrying a client MAC (A3:89 = Host.1, a client), not the master node route:

[D][Route]: did push the page - uspTopology
[D][Route]: did push the page - uspDeviceDetail
[D][Route]: did remove the page - ModalRoute(Page("uspDeviceDetail", [...], {mac: XX:XX:XX:XX:A3:89}), ...)

4. No JNAP _Error*, no USP failure code, no HTTP non-200, no Flutter exception anywhere in the log — the backend data is complete and correct. The wrong screen is produced entirely on the UI navigation layer.

Confidence: High — backend DeviceRole data confirmed correct in the attached log, and the mis-navigation to uspDeviceDetail with a client MAC is reproduced in the Route history; root cause is isolated to the topology node-tap routing (usp_topology_view.dart / node_detail_popup.dart) in PrivacyGUI 2.5.0.

---

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