device-access

Hardware tools must run on the host the device is plugged into. A cloud

agent cannot see your USB ports. Run npx @ruvnet/ruview locally, start a

local Claude Code session there (claude remote-control in the repo if you

want to drive it from the Claude app), or add the machine as an SSH host.

1. Find devices

npx @ruvnet/ruview doctor --group python,serial,devices,remote
npx @ruvnet/ruview devices          # USB VID:PID → likely ESP32 / mmWave / RPLIDAR + confirm command

2. Read each modality

The UDP capture cannot share port 5005 with a running sensing server; stop

the server or have the nodes target another port.

3. Other machines (SSH, read-only)

npx @ruvnet/ruview hosts add --name lab-pi --ssh ruv@lab-pi.local
ssh ruv@lab-pi.local true                       # pin the host key once
npx @ruvnet/ruview hosts run --host lab-pi --tool ruview_devices_scan
npx @ruvnet/ruview hosts run --host lab-pi --tool ruview_mmwave_read --args-json '{"port":"/dev/ttyUSB0"}'

Remote hosts run a pinned @ruvnet/ruview and accept only read-only tools.

Flash, train, and calibrate on the host itself.

Evidence

Device readouts are MEASURED readings, not accuracy results. mmWave

heart/breathing values are the radar's own estimates. Hardware validation

still means a captured log or stream from real silicon, recorded with the

command that produced it.