node-hue-api
Node.js Library for interacting with the Philips Hue Bridge and Lights
Runs with mockssource: GitHubTypeScriptApache-2.0commit 0318111a39aa
TypeScript, Apache-2.0 licensed. The project labels itself: hue, hue api, hue bridge, hue lights, javascript, lights, nodejs and scene.
node-hue-api runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Build compiles cleanly, npm install succeeds, 139 tests pass against a mock Hue Bridge on localhost, covering lighting CRUD, group management, sensor operations, schedules, scenes, rules, resource links, and user management
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 82 of 100 (the mean of this project's run scores).
At a glance
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Mock bridge required — no physical Hue Bridge on network10 minutes
- Background mock bridge process killed between shell commands3 minutes
- Discovery (nupnp.ts) hit real API and got rate-limited (HTTP 429)1 minute
- No test config file (~/.node-hue-api)1 minute
- Install time
- under a minute
- Cold machine to finish
- 29 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npx mocha -r ts-node/register --timeout 20000 with 13 test files against mock bridge on localhost:443: 139 passing, 4 pending, 27 failing
- Model tokens used
- 360,437
- Exact commit tested
- 0318111a39aa
- 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.
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
} ], \"test_depth\": \"tier2_mock\", \"verified_how\": \"npx mocha -r ts-node/register --timeout 20000 with 13 test files against mock… \"final_state\": \"Build compiles cleanly, npm install succeeds, 139 tests pass against a mock Hu… } ENDJSON echo \"Report ready\"" in /work/repo succeeded in 0ms: Report ready tokens used 360,437
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
- Installed in 0.5 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.29 | |
| Argusic Runner | 1/3 | Runs with mocks | 72.00 | 0.75 |
Topics (from GitHub)
huehue-apihue-bridgehue-lightsjavascriptlightsnodejssceneschedulesmart-homesmarthome
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/node-hue-api)Questions
- Does node-hue-api run?
- node-hue-api runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test node-hue-api?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0318111a39aa. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test node-hue-api?
- The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does node-hue-api take to install?
- 0.5 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-hue-api need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing node-hue-api?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for node-hue-api?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.