homebridge-config-ui-x
The Homebridge UI. Monitor, configure and backup Homebridge from a browser.
Runssource: GitHubhomepageTypeScriptMITcommit bb94ef61d69f
TypeScript, MIT licensed. The project labels itself: gui, hb service, homebridge, homebridge plugin, homebridge server, homebridge webserver, smart home and supervisor.
homebridge-config-ui-x runs. An Argusic agent installed it in 16.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All npm dependencies installed successfully for both root and ui packages, TypeScript server compiled to dist/, Angular UI built to public/, all 797 tests pass across 31 e2e test suites, and the Nest/Fastify standalone server starts on port 8080 serving the API and SPA.
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 100 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.
- System Node.js v18.19.1 is incompatible; project requires ^22.12.0.3 minutes
- Native binding @rolldown/binding-linux-x64-gnu missing in UI node_modules.2 minutes
- Native binding @oxc-parser/binding-linux-x64-gnu missing, causing 'Cannot find native binding' error in Angular build.2 minutes
- Install time
- 17 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test exited 0, 31 test files passed, 797 tests passed; app launched with log 'Homebridge UI v5.29.0 is listening on 0.0.0.0 port 8080'; Angular production build completed outputting to public/.
- Model tokens used
- 349,595
- Exact commit tested
- bb94ef61d69f
- 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
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 2, 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.
- Built UI output is in `public/` directory ✅
- App launched and was listening on port 8080 (per mock config) ✅
exec
/bin/sh -lc 'export PATH="/tmp/node-v22.22.3-linux-x64/bin:$PATH"
cd /work/repo && /tmp/node-v22.22.3-linux-x64/bin/node /tmp/node-v22.22.3-linux-x64/bin/npm test 2>…
succeeded in 149029ms:
Test Files 31 passed (31)
Tests 797 passed (797)
All tests pass. Now let me compile the final report.
tokens used
349,595
All tests pass. Now let me compile the final report.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
- Reached a running state on a clean machine, with the session recorded.
- Installed in 16.5 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
Topics (from GitHub)
guihb-servicehomebridgehomebridge-pluginhomebridge-serverhomebridge-webserversmart-homesupervisoruiweb-interface
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/homebridge-config-ui-x)Questions
- Does homebridge-config-ui-x run?
- Yes. homebridge-config-ui-x runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test homebridge-config-ui-x?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bb94ef61d69f. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test homebridge-config-ui-x?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does homebridge-config-ui-x take to install?
- 16.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 homebridge-config-ui-x need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing homebridge-config-ui-x?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for homebridge-config-ui-x?
- 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.