Linus-Dashboard

Auto-generated dashboard for Home Assistant, with no YAML: built from your areas and floors, it organizes your devices by room, floor and device type, places new devices on its own and can embed views from your existing dashboards. Install via HACS.

Runs with mockssource: GitHubJavaScriptMITcommit 46172e00d841

JavaScript, MIT licensed. The project labels itself: connected home, custom dashboard, dashboard, domotics, hacs, hacs integration, hass magic areas and home assistant.

Linus-Dashboard runs, with stand-ins for the services it depends on. An Argusic agent installed it in 8.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 55 Python tests and 74 frontend TypeScript tests pass, Home Assistant boots on port 8123 serving HTTP 302 with the linus_dashboard integration recognized, and the frontend rspack build completes successfully.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.13 (measured)
recorded runs
1
last tested
stars
214
forks
10
open issues
4
watchers
5
size
21 MB
created
last push

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.

Time lost to each failure while testing Linus-Dashboard, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • aiohasupervisor==0.6.0 not on PyPI (max 0.3.3)1 minute
  • homeassistant==2026.4.0 requires Python >=3.13, container has 3.121 minute
Install time
9 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
pytest tests/python/ -q exited 0, 55 passed; npx vitest run exited 0, 74 passed across 7 files; HA started on port 8123 returned HTTP 302 with custom integration loaded
Model tokens used
100,412
Exact commit tested
46172e00d841
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

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 1, 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.

None of these affect the Linus Dashboard integration itself — it has no `requirements` in its `mani…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 8…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 8.5, "errors": [{"msg": "a…
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\": true, \"launch_succeeded\": true, \"insta…
 succeeded in 0ms:
2026-10-30T15:41:07.361334Z ERROR codex_core::session: failed to record rollout items: thread 01a18…
2026-10-30T15:41:07.361377Z ERROR codex_core::session: failed to record rollout items: thread 01a18…
tokens used
100,412

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 8.5 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.

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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.13

Topics (from GitHub)

connected-homecustom-dashboarddashboarddomoticshacshacs-integrationhass-magic-areashome-assistantiotlinusresponsive-designsectionssmart-home

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Linus-Dashboard.svg)](https://argusic.com/subject/linus-dashboard)

Questions

Does Linus-Dashboard run?
Linus-Dashboard runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 9 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test Linus-Dashboard?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 46172e00d841. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test Linus-Dashboard?
The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Linus-Dashboard take to install?
8.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 Linus-Dashboard need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Linus-Dashboard?
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 Linus-Dashboard?
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.

Discussion