Devices: The "Connected via/to" info should display the node name instead of the model name

[KarenChen-Linksys]

Preconditions:

1. A network is setup with 3 nodes.
2. Some clients connected to the network.

Steps:

1. Menu > Devices.
2. Click on the "Connected via" filter / Select a client.

Actual result:
The "Connected via/to" info displays the model name.

Expected result:
The "Connected via/to" info should display the node name instead of the model name.

Device
Pinnacle 2.0 FW: 1.2.2.26062820
Linksys Now Version: 2.5.0.700525

Screenshots

Additional context
log: log.txt

[AustinChangLinksys]

🔍 Automated investigation (preliminary triage)

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

Root cause:

• UI defect: when building the per-device presentation model, parentNodeName is populated with the mesh node's model name (matchingNode.model, e.g. "MR7500") instead of the node's user-assigned display name. A NodeUIModel.displayName getter already exists with the correct priority (friendlyName > hostName > model > deviceId), but the devices data service bypasses it and reads .model directly. The "Connected via/to" field (device detail + filter panel) therefore shows the model name rather than the node name.

Evidence (from source, dev-2.5.0):

• Data service assigns model name instead of the node display name — lib/page/devices/services/usp_devices_data_service.dart:

final matchingNode = meshTopology.nodes
    .where((n) => n.deviceId == parentNodeId)
    .firstOrNull;
parentNodeName = matchingNode?.model.isNotEmpty == true
    ? matchingNode!.model
    : parentNodeId;

• A correct display-name getter already exists but is not used here — lib/page/topology/models/node_ui_model.dart:

/// Display name priority: friendlyName > hostName > model > deviceId.
String get displayName {
  if (friendlyName != null && friendlyName!.isNotEmpty) return friendlyName!;
  if (hostName != null && hostName!.isNotEmpty) return hostName!;
  if (model.isNotEmpty) return model;
  return deviceId;
}

• The filter panel also falls back to .model for the same reason — lib/page/devices/views/components/usp_device_filter_panel.dart (connectedVia labelOf): return node?.model ?? id;

Confidence: High — code path confirmed on dev-2.5.0 (matches reported version 2.5.0.700525); pure UI mapping defect, no backend error involved. Likely fix direction: use matchingNode?.displayName (and the node's display name in the filter panel) instead of .model.

---

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