Console networking and audio

Network status

The Network page separates internet connectivity/default route from robot Ethernet/DDS. Inspect adapters, current connection, gateway and routes before changing anything. Wi-Fi supports filtering available networks, rescan, connect with credentials, disconnect and forgetting saved networks.

Forgetting a network removes its saved profile; it is different from temporary disconnect. Rescan can take time. A browser request failure after changing the connection may reflect loss of its own network path rather than backend rejection.

Ethernet safe apply

1. Select the intended physical adapter.
2. Choose DHCP internet/network, static IPv4, or Robot LAN without default route.
3. Review address/netmask/gateway and DDS-related choices shown for that mode.
4. Choose Apply safely.
5. Reconnect/check reachability and run Test DDS route.
6. Confirm the change within the backend's deadline if it works; otherwise choose Roll back now or let the rollback window expire.

The default backend window is 45 seconds. Apply creates a rollback token and deadline; confirm and rollback must use that token. The UI's Connect/Disconnect button changes adapter connection state separately. Do not confirm blindly just to dismiss the countdown.

The route panel switches between key/all routes. Use it to verify that robot LAN traffic uses the selected Ethernet interface while internet traffic uses the intended default route. Enabling internet sharing is a separate persistent gateway function with a selected target; inspect its current persisted state before enabling/disabling.

Audio device selection

The Audio page lists input/output choices and volume controls, with live/shared level information. Selecting an application output/input can involve card/profile selection as well as a sink/source name. A visible host device is not proof that the SDK container can access it.

Select the physical output and microphone first. Start at a controlled volume, inspect activity and test the intended path. Distinguish the robot's host playback from the operator browser speaker switch in Robot WebUI.

Routing graph

The graph maps HRSDK source channels to physical target channels. It reflects the selected sink's actual channel layout, including stereo cases. Select a source and target to create/toggle a route; select a route to change gain or delete it. Escape clears graph selection. Mobile controls expose equivalent route operations.

Routing edits are applied live after a debounce; they are not merely a disconnected drawing. Pending/applying/applied/failed states reflect asynchronous operations. If another edit arrives during apply, the UI queues the latest payload. Wait for the final state before testing or navigating away.

Choose a preset for a known mapping or edit connections to create a custom mapping. Save applies the current mapping with persistence; ordinary live edits default to nonpersistent apply. Changing the physical sink can trigger immediate reapplication for its channel layout.

Per-source test voice/tone controls help verify routing audibly. They produce actual sound. Gain and channel-map controls affect their respective routing/device layers; do not assume all volume sliders are the same gain stage. Reset changes routing and should be followed by inspection.

Container check and recovery

Read routing/device warnings and the container visibility check. If the host plays sound but the robot does not, inspect PulseAudio socket/cookie mounting, user/session selection, selected virtual/physical sink, and the container's view. If browser monitoring works while robot audio fails, inspect the physical/internal path rather than microphone ownership.

If a route edit fails, inspect the task/error and current backend connections before reapplying; the rendered pending graph can differ from the last applied mapping. Persist only after the physical channels have been tested.

Sources: hr_system_console/frontend/src/pages/{NetworkPage.jsx,AudioPage.jsx} and backend network/audio services. Console API guide.