deconz-rest-plugin
deCONZ REST-API plugin to control ZigBee devices
Runssource: GitHubC++BSD-3-Clausecommit a4c17adfa04a
C++, BSD-3-Clause licensed. The project labels itself: conbee, home automation, raspbee, raspberry pi, zha, zigbee and zll.
deconz-rest-plugin runs. An Argusic agent installed it in 24 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The deCONZ REST API plugin libde_rest_plugin.so builds successfully on Ubuntu 24.04 with Qt6, and the 303-timeref unit test compiles and passes 1/1 test cases with all 7 benchmarks completing.
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.
- Qt6 development packages not installed5 minutes
- FindOpenGL could not find GL libraries3 minutes
- Catch2 v2.13.1 fails on GCC 132 minutes
- ninja not available1 minute
- Qt6DBus lib not in prefix1 minute
- deconz headers not in include path1 minute
- Install time
- 24 minutes
- Cold machine to finish
- 25 minutes
- Errors hit and fixed
- 9 hit, 9 fixed with no human help
- How the result was proved
- cmake --build build --target de_rest_plugin exited 0; /work/repo/build/tests/303-timeref ran 1 test case with all 7 benchmarks completing
- Model tokens used
- 434,945
- Exact commit tested
- a4c17adfa04a
- 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.
### Errors encountered and fixed | Error | Fix | |---|---| | No Qt6 dev packages installed, no root/sudo | Extracted Qt6 debs from archive to `/tmp/qt6prefix`… | `ninja` not installed | Switched to `Unix Makefiles` generator | | `FindOpenGL` couldn't find OpenGL libs | Provided `OPENGL_opengl_LIBRARY`, `OPENGL_glx_LIBRARY`, … | Qt6DBus library missing from prefix | Copied from system `/usr/lib` | | Catch2 v2.13.1 incompatible with GCC 13 (`sysconf` not constexpr) | Upgraded to Catch2 v2.13.10 | | `deconz/u_assert.h` and other deconz headers not found by test libs | Added `deconzlib-src` inclu… | `SKIP_EMPTY_PARTS` not defined for test libs | Added compile definition to `deconz_common` target… | `resource` library needed `deCONZLib` linkage | Added `deCONZLib` as dependency to resource CMake… | `device_js` CMakeLists referenced nonexistent files | Rewrote to use existing source files only |
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 24 minutes.
- Recovered from all 9 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 BSD-3-Clause, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/deconz-rest-plugin)Questions
- Does deconz-rest-plugin run?
- Yes. deconz-rest-plugin runs. Argusic installed and launched it on a clean machine in 24 minutes, hitting 9 errors on the way, and recorded the session.
- How did Argusic test deconz-rest-plugin?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a4c17adfa04a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test deconz-rest-plugin?
- The run that produced this verdict cost $0.41: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does deconz-rest-plugin take to install?
- 24 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 deconz-rest-plugin need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing deconz-rest-plugin?
- 9 things broke in the recorded run, and 9 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for deconz-rest-plugin?
- 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.