Google Nest Audio Playback and Volume

Google Nest Audio

Humans to Know Editorial Context

Use the pinned Muse Gadget SDK repository for runtime setup. Existing LAN-device clients run on its Linux Home Link through system.run; the Muse app, SDK token and VM connection remain required.

This is a community-sourced Muse device skill, adapted by Humans to Know; it is not an official integration. Before choosing the runtime, read repository context and task handoff. That supplement identifies the pinned SDK, Linux command boundary, setup dependencies and the evidence to retain for this device.

Use this skill when current discovery identifies the Google Nest Audio.

Identify the Device

• Confirm Nest Audio model metadata, current receiver ID and whether the requested target is one speaker or an already-configured group.
• Match the current receiver to the user's intended device; use its current service endpoint, not a remembered address.
• This is an audio-only receiver. Pair/group topology must be observed rather than inferred from friendly names.

Prerequisites

Read the Humans to Know repository context before network access. It is an editorial supplement for the upstream home_link.md reference, whose target is absent from this public snapshot.

• The device is already provisioned and available as a receiver in its supported operating state.
• For new playback, an existing user-authorized media source must be reachable by the receiver. Device access alone does not supply media hosting.

Workflow

1. Use the Google Cast skill for discovery interpretation, receiver/media status, playback controls, volume, media loading and verification. That skill is the single protocol procedure.
2. Apply this profile's model and operating-state restrictions before selecting an operation. Missing media status while idle is not proof that the device is unreachable.
3. For an existing group, follow the shared skill's separate group-target rules and confirm that the user intended all group members.

Verify the Result

• Follow the shared skill's operation-specific checks and report whether the result was actually observed on this device.

Limits

• No stereo-pair creation, group reconfiguration, private setup-token operations, microphone access or assistant/cloud routines.
• Do not infer device administration or general remote-control capabilities from Cast support.

Sources

• Shared Google Cast skill and protocol sources