ioBroker
Automate your life!
Runssource: GitHubhomepageShellMITcommit e30d19e15377
Shell, MIT licensed. The project labels itself: home automation, iobroker, nodejs and smarthome.
ioBroker runs. An Argusic agent installed it in 7.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.
npm install and build succeed; ioBroker controller 7.2.2 starts and serves Admin UI on port 8081 with real packages installed via npm path
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 75 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.
- bash installer (dist/install.sh) cannot run — needs root for useradd, apt-get, mkdir in /opt. Cannot install system packages3 minutes
- Node.js v18 is too old for ioBroker (requires 22+). Had to download Node.js v22.14.0 from official tarball into $HOME/.local2 minutes
- sudo command not available in container1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- node test.js exited 0 and printed 'ioBroker admin is running'; curl -s http://127.0.0.1:8081 returned HTML with <title>Admin</title>; controller logs showed admin.0 listening on port 8081
- Model tokens used
- 95,905
- Exact commit tested
- e30d19e15377
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.a… (node:2638) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS… (Use `node --trace-warnings ...` to show where the warning was created) ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.a… exec /bin/sh -lc 'kill -9 2617 2>/dev/null; kill -9 2616 2>/dev/null; sleep 1; ps aux | grep iobroker | … exited 1 in 870ms: Now let me compile the final result. tokens used 95,905 Now let me compile the final result.
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 7.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.
- A quick evaluation: it was running 7.5 minutes after the clone.
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 | 100.00 | 0.07 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.06 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/iobroker)Questions
- Does ioBroker run?
- Yes. ioBroker runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test ioBroker?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e30d19e15377. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ioBroker?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ioBroker take to install?
- 7.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 ioBroker need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ioBroker?
- 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 ioBroker?
- 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.