sonoscli▌
steipete/clawdis · updated Apr 8, 2026
Local network Sonos speaker control with discovery, playback, volume, and grouping.
- ›Discover speakers on the local network and control individual devices by name with play, pause, stop, and volume commands
- ›Manage speaker groups with join, unjoin, party, and solo operations; browse and play favorites and queue tracks
- ›Optional Spotify search integration via SMAPI (requires Spotify Web API credentials) and fallback IP specification for SSDP discovery failures
- ›Requires the sonos CLI b
Sonos CLI
Use sonos to control Sonos speakers on the local network.
Quick start
sonos discoversonos status --name "Kitchen"sonos play|pause|stop --name "Kitchen"sonos volume set 15 --name "Kitchen"
Common tasks
- Grouping:
sonos group status|join|unjoin|party|solo - Favorites:
sonos favorites list|open - Queue:
sonos queue list|play|clear - Spotify search (via SMAPI):
sonos smapi search --service "Spotify" --category tracks "query"
Notes
- If SSDP fails, specify
--ip <speaker-ip>. - Spotify Web API search is optional and requires
SPOTIFY_CLIENT_ID/SECRET. - If there is an error, check the troubleshooting section and offer advice if there is a decent match.
Troubleshooting
sonos discover - no route to host
- On error
Error: write udp4 0.0.0.0:64326->239.255.255.250:1900: sendto: no route to host (Command exited with code 1)- Note that the port number after
0.0.0.0:is ephemeral and will change and the netmask may not match exactly either - The
sendto: no route to hostshould stay consistent
- Note that the port number after
- Advise the user that in
direct(no Docker sandbox) mode on Mac OS that Settings -> Privacy & Security -> Local Network will need to be enabled for the top-level host parent process of the Gatewaynodeif running vialaunchdTerminalif running the gateway directly in the terminalVisual Studio Codeif running via terminal in VS Code
- An alternative option is to use
sandbox(docker container) with network access allowed for that sandbox
sonos discover - bind: operation not permitted
- On error
Error: listen udp4 0.0.0.0:0: bind: operation not permitted - Advise the user that they may be running via a Codex or other sandbox that does not permit network access (this can be replicated by running
sonos discoverwithin a Codex CLI session with sandbox enabled and not approving the escalation request)
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★44 reviews- ★★★★★Shikha Mishra· Dec 24, 2024
sonoscli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★James Harris· Dec 20, 2024
sonoscli has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kabir Mehta· Dec 8, 2024
We added sonoscli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yuki Chen· Dec 8, 2024
sonoscli reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Hiroshi Nasser· Nov 27, 2024
I recommend sonoscli for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Layla Gonzalez· Nov 15, 2024
sonoscli fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Mia Wang· Nov 11, 2024
Keeps context tight: sonoscli is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sakura Agarwal· Oct 18, 2024
Useful defaults in sonoscli — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Layla Harris· Oct 6, 2024
We added sonoscli from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Nikhil Mehta· Oct 2, 2024
sonoscli is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 44