xknx
XKNX - A KNX library written in Python
Runssource: GitHubhomepagePythonMITcommit 02994fae1440
Python, MIT licensed. The project labels itself: hacktoberfest, home assistant, home automation, knx and python.
xknx runs. An Argusic agent installed it in 4 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
xknx 3.20.0 installed with all dependencies, 4037 unit tests passing, all lint/type-check hooks passing, and KNX telegram encode/decode round-trip verified working.
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.
- uv package manager not installed in container1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- uv run pytest returned '4037 passed, 2 warnings in 10.38s'; uv run prek run --all-files returned all 8 hooks Passed; manual DPT telegram round-trip: 22.5C encoded to bytes 0c65 and decoded back to 22.5C
- Model tokens used
- 42,938
- Exact commit tested
- 02994fae1440
- 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.
This is a Python library, not a desktop app. The "launch" is running the test suite and exercising … The verification is `tier1_real` because the full test suite ran with real protocol logic and I ver… exec /bin/sh -lc 'cd /work/repo && export PATH="$HOME/.local/bin:$PATH" && uv run pytest --quiet 2>&1 | … succeeded in 11580ms: 0.10s call test/management_tests/procedures/device/test_dmp_interface_object_read_r.py::test_dm… 0.10s call test/management_tests/procedures/device/test_dmp_interface_object_write_r.py::test_d… 4037 passed, 2 warnings in 10.38s All verified. Now let me compile the final result. tokens used 42,938 All verified. 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.
- Recovered from all 1 error 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.
What did not, or is not known
- Took 4 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 12 hacktoberfest projects Argusic has installed and timed, xknx was the 8th fastest to reach a running state, and 11 of 12 reached one at all.
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 4 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xknx)Questions
- Does xknx run?
- Yes. xknx runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test xknx?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 02994fae1440. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test xknx?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does xknx take to install?
- 4 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 xknx need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing xknx?
- 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 xknx compare with the alternatives?
- Of the 12 hacktoberfest projects Argusic has installed and timed, xknx was the 8th fastest to reach a running state, and 11 of 12 reached one at all.
- Where is the evidence for xknx?
- 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.