Apple HomePod mini

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 a compatible pyatv client with its control sockets routed over HomeLink (using discovery already supplied by Link rather than agent-side multicast), permission for the requested audio action and its target speakers, and the speaker's existing access, password and pairing requirements honoured and preserved — access settings are never weakened to obtain a connection, and credentials and session encryption are preserved. Installing the file configures none of that. Install "Apple HomePod mini" for me. It controls HomePod mini volume, supported existing-session playback, and output groups through Muse Home Link; it is not for starting new audio streams. It is used when fresh discovery identifies a HomePod mini, commonly model identifier AudioAccessory5,1, with a compatible local control service: model identity, current AirPlay/RAOP service endpoints and the intended speaker or existing stereo-pair primary are matched, and pyatv device information and feature availability are the capability boundary — a service advertisement alone does not prove every control is available. The client configuration is constructed from the current device identity and supported service endpoints, and only the local TCP control paths needed for the operation are connected. It reads device_info, feature availability, volume and available output-device/session state first (Unavailable during idle is different from permanently unsupported). For a volume change it uses the supported volume setter or step operation with the documented scale, then reads volume back, because some firmware has acknowledged a setter without changing the level. For transport controls it checks that the existing session exposes the requested play/pause/next/previous capability, without assuming this client can inspect or control all playback started elsewhere. For a group change it uses supported output-device operations with explicitly identified existing receiver IDs and confirms group membership afterward; group changes can affect other rooms and are not part of discovery. Volume and the relevant session/group state are read after an action, and unavailable metadata is reported honestly. Limits: no general RAOP/UDP audio streaming, no media hosting on Link, no signed-in Mac automation, no Siri/Intercom, no Home configuration and no temperature/humidity access is promised; play_url is not recommended for this device, and controlling a supported existing session is distinct from creating a new media stream; a stereo pair is not inferred to be creatable or dismantlable through the output-device API, and other HomePod generations and third-party AirPlay receivers require their own capability checks. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-apple-homepod-mini/ 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-apple-homepod-mini/ 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 0b03c3dc546fc4a8cc274fec9adfc627743f61312f5208634f32b7933cc24890 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 (3,026 bytes). There is no script, no code and no configuration in it; the procedure runs at use time through a compatible pyatv client routed over Muse Home Link against my own local HomePod mini. It has no dependency on any other gadget skill in this lot. - 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, no pairing is started and no playback is started during installation. - At use time, exchanges go only to my local HomePod mini, over the local TCP control paths needed for the operation, with discovery already supplied by Link rather than agent-side multicast. The speaker's existing access, password and pairing requirements are honoured and preserved, credentials and session encryption are preserved, and access settings are never weakened to obtain a connection. - The skill does not do general RAOP/UDP audio streaming, media hosting on Link, signed-in Mac automation, Siri/Intercom, Home configuration or temperature/humidity access, and it does not recommend play_url for this device: controlling a supported existing session is distinct from creating a new media stream. It also does not infer that a stereo pair can be created or dismantled through the output-device API. - 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-apple-homepod-mini folder into the agent's skills directory, in a folder named exactly "gadget-apple-homepod-mini", 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-apple-homepod-mini), 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 HomePod mini already set up on my local network exposing compatible local pyatv services; use a compatible pyatv client routed over HomeLink; and keep the speaker's existing access/password/pairing requirements in place, preserved and never weakened; 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.