Sonos Speakers

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Muse Home Link and a compatible physical device are required to USE this skill, not to install it: installing the skill file itself needs no account, no key and no device, and this install does NOT set up Home Link, pair anything or ask for any credential. But the skill is instructions only. To use it I must read and follow ~/docs/devices/home_link.md in my Muse environment, have the compatible physical device named below already set up on my local network, and have no credentials at all — the local UPnP services need none — plus permission for the requested room/group and operation, and, for a new media item, an existing URL reachable by the speaker with the needed format and authorization. Installing the file configures none of that. Install "Sonos Speakers" for me. It controls Sonos speakers on my local network through their local UPnP/SOAP services, using a compatible SoCo client (or SOAP implementation) with the actual device service URLs through Home Link. It first reads the advertised device description and service/control URLs to confirm model, player identity and supported services, then reads zone/group topology and resolves the requested room, stereo pair and current group coordinator; not every network endpoint is a separately controllable room. It reads transport state, track/media information, volume/mute and group membership before acting. Volume and mute target the intended speaker/room or an explicitly requested group operation; playback goes to the group coordinator (play/pause/stop/seek or existing-queue actions), and changing the transport URI or queue contents is a separate user-authorized action. A group change uses the documented join/unjoin operation, preserving bonded stereo and home-theater configurations. It polls state afterwards instead of relying on device event callbacks. Limits: no inbound GENA callback server, no on-Link media/TTS server, no port-1443 requirement, no cloud fallback; no account/service provisioning, firmware updates or stereo/home-theater reconfiguration. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-sonos-speakers/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit e6fe5174092702ffddae6f90759a38d55a4ebae1 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/facebookincubator/muse-gadget-sdk into a temporary folder, check out commit e6fe5174092702ffddae6f90759a38d55a4ebae1, and copy the skills/gadget-sonos-speakers/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 8bac9aa4c1d2f0e8864fd0c6dbc85a0a8edb03bae9f2a1bb83c895b9a0e3b4b4 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (2,812 bytes). There is no script, no code and no configuration in it; at use time it works through a compatible SoCo client or SOAP implementation using the speaker's actual local UPnP service URLs via Muse Home Link. It has no dependency on any other gadget skill in this lot, and it needs no credentials. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No speaker is contacted and no group is touched during installation. - At use time, exchanges go only to my local Sonos speakers: transport, volume/mute and group operations on the resolved room or group coordinator. There is no cloud fallback. For a new media item, the speaker itself fetches an existing URL that it can already reach with the needed format and authorization; the skill does not upload private media and does not create a server implicitly. - The skill does not run an inbound GENA callback server or an on-Link media/TTS server, does not provision accounts or services, does not update firmware and does not reconfigure stereo pairs or home-theater setups; bonded configurations are preserved. - Do not pair any device, do not ask for or set any credential, do not run any control, print, scan or playback action, and do not use the skill in any way during this install: Home Link setup, pairing and use are my decisions, later, when I actually ask for them. 3. When I say "yes, install", install it as a skill: copy the whole gadget-sonos-speakers folder into the agent's skills directory, in a folder named exactly "gadget-sonos-speakers", keeping its 1 file (SKILL.md at its root). The exact folder name matters: relative links between sibling gadget skills depend on these exact names. 4. Verify with no network calls: frontmatter valid (name: gadget-sonos-speakers), the 1 file in place with matching fingerprint. Do not run anything and do not connect to any device to verify. 5. Report what was installed, where, and what I still need to do myself (for example: read ~/docs/devices/home_link.md in my Muse environment and follow its Home Link rules; have a compatible Sonos speaker already set up on my local network; and give permission for the exact room/group and operation, knowing grouping can interrupt or redirect audio in other rooms — no credentials are involved; using the skill is a separate step that only starts when I ask for it, and the use-time exchanges disclosed above happen only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.