node-sonos

🔈 Sonos Media Player Interface/Client

Runs with mockssource: GitHubhomepageJavaScriptMITcommit ceaa85502d49

JavaScript, MIT licensed. The project labels itself: home automation, javascript, music, nodejs and sonos.

node-sonos runs, with stand-ins for the services it depends on. An Argusic agent installed it in 26 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.82 (measured)
recorded runs
1
last tested
stars
720
forks
140
open issues
19
watchers
25
size
2 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing node-sonos, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Mock SOAP responses were malformed (double closing tags, over-escaped TrackMetaData, literal ZoneGroupState wrapper, SSDP bound only to 127.0.0.1)20 minutes
Install time
26 minutes
Cold machine to finish
26 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
Model tokens used
3,947,624
Exact commit tested
ceaa85502d49
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

How the result was proved
runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- Ran `npm test` — `27 passing, 18 pending`, exit 0 (includes `standard` lint).
- Stood up a schema-correct mock Sonos speaker (HTTP SOAP/XML endpoints on `127.0.0.1:1400`, GET `/…
- Drove the real library over real HTTP end to end with `node run-e2e.js`; the device methods retur…
- Exercised `DeviceDiscovery`: `run-discovery.js` printed `FOUND device host=172.25.0.24 model=ZPS1…
- No third-party credentials are used by this project; all verification is via the local mock (tier…
**Errors hit and fixed (all in my mock, none in the repo)**
1. Mock emitted SOAP responses with doubly-nested closing tags (`</GetPositionInfoResponse></u:GetP…
2. Mock lacked the `SUBSCRIBE`-relevant endpoint handling initially, and response bodies returned c…
3. Mock's `GetZoneGroupState` handler wrapped the value in literal `<ZoneGroupState>…</ZoneGroupSta…
4. Mock's `TrackMetaData` string was double-escaped (`&amp;amp;`); rebuilt it with a single pass of…
5. UDP SSDP listener bound only to `127.0.0.1` (container multicast/broadcast didn't deliver); boun…
I did not modify any repository files. All fixes were outside the repo, in `/tmp/sonosmock/`. Test …

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 26 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 5 home-automation projects Argusic has installed and timed, node-sonos was the 5th fastest to reach a running state, and 3 of 5 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.82

Topics (from GitHub)

home-automationjavascriptmusicnodejssonos

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/node-sonos.svg)](https://argusic.com/subject/node-sonos)

Questions

Does node-sonos run?
node-sonos runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 26 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test node-sonos?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ceaa85502d49. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test node-sonos?
The run that produced this verdict cost $0.82: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does node-sonos take to install?
26 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does node-sonos need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing node-sonos?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does node-sonos compare with the alternatives?
Of the 5 home-automation projects Argusic has installed and timed, node-sonos was the 5th fastest to reach a running state, and 3 of 5 reached one at all.
Where is the evidence for node-sonos?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion