home-assistant-config
Home Assistant config files, rewritten to use the latest features, 100+ documented automations, automatically generated ToC :house: :robot:
Runssource: GitHubJavaScriptMITcommit 3b7b439761c4
JavaScript, MIT licensed. The project labels itself: appdaemon, automation, config, home assistant, home assistant config, home automation, internet of things and iot.
home-assistant-config runs. An Argusic agent installed it in 18 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Home Assistant 2025.1.4 starts successfully and responds to HTTP requests on port 8123 with the login page.
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.
- Python C headers (Python.h) not found, blocking netifaces build5 minutes
- pyspeex-noise==1.0.2 fails to build (no root for python3-dev)3 minutes
- Broken symlink custom_components/adaptive_lighting2 minutes
- aiodiscover/aiodns version conflict with HA requirements2 minutes
- Missing secrets.yaml with dummy values1 minute
- Missing custom_components/pyscript1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w '%{http_code}' http://localhost:8123/ returned 302 with HTML title 'Home Assistant'
- Model tokens used
- 120,335
- Exact commit tested
- 3b7b439761c4
- 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.
- **Python C headers missing** (`Python.h`) — extracted `libpython3.12-dev` from Ubuntu archive, pl… - **`allowlist_external_dirs: /config/`** not a valid dir — changed to `/work/repo/` - **`db_url: sqlite:////config/home-assistant.db`** not writable — changed to `/tmp/home-assistant.… - **`aiodiscover`/`aiodns` version conflict** — pinned compatible versions **Remaining (non-blocking) issues**: - `pyspeex-noise==1.0.2` can't build (needs root for `python3-dev`, uses pybind11 in build isolatio… - Automation `webostv.turn_on` trigger not supported in HA 2025.1.x - `template` config has an invalid `switch:` section at `templates.yaml:564` - pyscript `wake_up_light.py` fails to load at runtime (likely API change) - `libturbojpeg` not available (camera snapshots degraded, core unaffected) - Person user_ids invalid (needs real HA onboarding) **Verification**: Launched HA server, which served HTTP 302 redirect to login page at `localhost:81…
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 18 minutes.
- Recovered from all 8 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.
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)
appdaemonautomationconfighome-assistanthome-assistant-confighome-automationinternet-of-thingsiotlovelacelovelace-uiphilips-hueyaml
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/home-assistant-config)Questions
- Does home-assistant-config run?
- Yes. home-assistant-config runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test home-assistant-config?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3b7b439761c4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test home-assistant-config?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does home-assistant-config take to install?
- 18 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 home-assistant-config need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing home-assistant-config?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for home-assistant-config?
- 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.