ha-linky
📊 Home Assistant app for Linky smart meters
Runs with mockssource: GitHubTypeScriptMITcommit 99419a30e879
TypeScript, MIT licensed. The project labels itself: enedis, home assistant, linky and smart home.
ha-linky runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.1 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The project installs, builds, and all 27 unit tests pass. The app starts, reads config, and communicates with Home Assistant WebSocket API. Real Linky meter credentials (PRM + Conso API token) are required for full e2e data sync.
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 56 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.
- Tests failed because container timezone (UTC) differs from test expectations (Europe/Paris) - 8 tests failed with timezone-offset date mismatches2 minutes
- Config path hardcoded to /data/options.json, preventing non-root app launch2 minutes
- Install time
- under a minute
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm test exited 0, 27 passed (all 4 test files); npm run build (tsc) exited 0; app with empty config ran to completion: 'HA Linky is starting' -> 'Add-on is not configured properly' -> 'HA Linky stopped', exit 0; app with mock HA WebSocket reached 'Connection with Home Assistant established' before needing real Linky API credentials
- Model tokens used
- 223,325
- Exact commit tested
- 99419a30e879
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
+ parsed = JSON.parse(readFileSync(process.env.CONFIG_PATH || '/data/options.json', 'utf8'));
} catch (e) {
throw new Error('Cannot read user configuration: ' + e.toString());
}
Here is my report:
**ARGUSIC_RESULT:**{"install_succeeded":true,"launch_succeeded":true,"install_minutes":0.1,"errors"…
2026-10-18T13:44:30.992172Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
2026-10-18T13:44:30.992204Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
tokens used
223,325
Here is my report:
**ARGUSIC_RESULT:**{"install_succeeded":true,"launch_succeeded":true,"install_minutes":0.1,"errors"…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.1 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, 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.17 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.19 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ha-linky)Questions
- Does ha-linky run?
- ha-linky runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test ha-linky?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 99419a30e879. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ha-linky?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ha-linky take to install?
- 0.1 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 ha-linky need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ha-linky?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for ha-linky?
- 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.