← Search

Logitech Squeezebox via Lyrion
Smart Home 📌 Pinned version: commit e6fe517
⚙ Needs: Before you start: read this whole install prompt…

Logitech Squeezebox via Lyrion

Read player status and control Squeezebox playback or volume through Muse Home Link, via an existing local Lyrion/Squeezebox server and its JSON-RPC HTTP endpoint.

At a glance
What
Read player status and control Squeezebox playback or volume through Muse Home Link, via an existing local Lyrion/Squeezebox server and its JSON-RPC HTTP endpoint.
Cost
Free
Needs
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.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

M
Created by: Meta (facebookincubator)
⌁

Install

Copy the install package below, then paste it into Muse📌 Pinned version: commit e6fe517

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 an existing configured local Lyrion/Squeezebox server with a Squeezebox player already connected to it, any required HTTP authentication for that server, and an existing library item or media source reachable and usable by that server/player with any necessary entitlements. No new server is deployed. Installing the file configures none of that. Install "Logitech Squeezebox via Lyrion" for me. It reads player status and controls Squeezebox playback or volume through Muse Home Link, through an existing local Lyrion/Squeezebox server. It is used when a Squeezebox-compatible player is already connected to a reachable local Lyrion/Squeezebox server: it identifies the existing server's actual HTTP endpoint and server version, then enumerates its connected players and resolves the intended player by returned player ID and name — the speaker's own network port is not necessarily the server's JSON-RPC endpoint. It needs an existing configured Lyrion server, any required HTTP authentication, a player already connected to it, a JSON-RPC HTTP client routed through HomeLink and an existing library item or media source reachable and usable by that server/player, with any necessary entitlements. It sends HTTP JSON to the server's /jsonrpc.js endpoint using method slim.request, a request ID and params: [player_id, command_array], using the empty player ID for documented server-wide reads; it enumerates players with the documented players command (following pagination), queries the selected player's status and reads power, playback, volume and current playlist before acting. For the requested playback it issues supported commands such as play, pause, stop, playlist selection or mixer volume, using returned library IDs/URLs and the command's documented argument semantics, and it uses an explicit desired pause/volume value where supported rather than ambiguous toggles; it does not replace a queue or select a new source merely to inspect status. It polls the selected player's status and correlates JSON-RPC errors/replies to the request, checking both JSON-RPC errors and the player's subsequent status, not just HTTP success: a queue entry or buffering state is not proof that audio is playing, and the intended player is confirmed before changing a shared server playlist. Limits: no new server deployment, no direct SlimProto implementation and no automatic access to cloud media services; HomeLink is not a media server and agent-local files are not automatically reachable by Lyrion or the player. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-logitech-squeezebox/ 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-logitech-squeezebox/ 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 fa2dec1935619270797c70aef33c27264ba8b922cc165984242581ee0e506b0a 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 994 bytes). There is no script, no code and no configuration in it; the procedure runs at use time through Muse Home Link against my own local device. 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 device is contacted, no pairing is started and no key is asked for during installation. - At use time, exchanges go only to my existing local Lyrion/Squeezebox server's /jsonrpc.js endpoint over HTTP JSON (method slim.request), through a JSON-RPC client routed through HomeLink: player enumeration, status reads and the playback/volume commands I requested, with the server's HTTP authentication only if that server requires it. No new server is deployed and no cloud media service is accessed automatically. - The skill does not deploy a new server, implement SlimProto directly, or access cloud media services automatically, and HomeLink is not a media server: agent-local files are not automatically reachable by Lyrion or the player. - 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-logitech-squeezebox folder into the agent's skills directory, in a folder named exactly "gadget-logitech-squeezebox", 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-logitech-squeezebox), 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 an existing configured local Lyrion/Squeezebox server with a Squeezebox player already connected to it, plus any HTTP authentication that server requires; no new server is deployed; 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this build does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-22
🔒 Security and provenance
📌 Pinned version: commit e6fe517 · 2026-10-22
🔎 Last checked · Oct 22, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.