zwave-js / zwave-js-ui / 27954958160

8%

push

github

fix(ui): separate virtual and physical devices in nodes table (#4673)

Closes #4672

## Problem

The recently introduced virtual nodes (broadcast / multicast groups)
were rendered in the same device list as physical nodes. Since virtual
nodes have very different characteristics (no battery, routes, firmware,
interview, etc.), the mixed table looked broken. Worse, there was no
logic excluding them from group physical-device actions, so selecting a
virtual node together with physical ones and triggering **Re-interview /
Ping / Rebuild Routes / Refresh Values / Remove Failed** would dispatch
those node-level actions to the virtual node too.

## Changes

- **Physical/Virtual view toggle** — added to both the full nodes table
(`nodes-table`) and the compact `SmartView` (used on mobile / small
screens). The toggle only appears when the network actually contains
virtual nodes, so existing networks see no change. Defaults to the
*Physical* view, so virtual nodes no longer clutter the device list.
- **Virtual nodes are not selectable** — `item-selectable` on the data
table and a guarded select handler in `SmartView` prevent virtual nodes
from ever entering the selection that drives the bulk action toolbar.
Switching views clears the current selection.
- **Bulk-action boundary guard** — `sendAction` now filters virtual
nodes out of bulk node actions as a final safety net, since those
actions don't apply to them.

## Testing

- `npm run lint` — clean on all changed files
- `npm run build:ui` (vite build) — succeeds

🤖 Generated with [Claude Code](https://claude.com/claude-code)

436 of 564 branches covered (77.3%)

Branch coverage included in aggregate %.

0 of 48 new or added lines in 3 files covered. (0.0%)

4523 of 25146 relevant lines covered (17.99%)

1.13 hits per line