HomeTiles
Touch dashboards for Home Assistant on ESP32-P4 and ESP32-S3 displays. Lights, climate, sensors, energy, weather and more, set up in your browser.
Runs with mockssource: GitHubhomepageCMITcommit e0acbc94628d
C, MIT licensed. The project labels itself: dashboard, esp32, esp32 p4, esp32 s3, guition, home assistant, home automation and lvgl.
HomeTiles runs, with stand-ins for the services it depends on. An Argusic agent installed it in 78 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The repo now installs cleanly, its Web asset generation and device-profile checks pass, its host test suite passes 248 of 343 tests (95 skipped for missing headless Chrome), and firmware for the Waveshare 4B ESP32-P4 profile compiles successfully to a 6.75 MB app image; the remaining uncommitted changes are the 4 production-header enum fixes, 2 test-harness fixes, and regenerated Web asset includes.
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
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.
- 6 host C++ tests failed to compile: enum/int comparisons in ternaries (GCC 13 -Werror=extra) in swipe_gestures.h, clock_format.h, text_options.h, tile_config.h15 minutes
- HomeTiles.ino is a bare .ino file, so arduino-cli resolves the sketch name from the directory basename (repo.ino), not the file12 minutes
- Stale generated Web assets: generate-web-assets.mjs --check reported src/web/generated/admin_css_gzip.inc stale8 minutes
- Host harness test-settings-access-record.mjs failed: -Werror=class-memaccess on memset of non-trivial DeviceConfig8 minutes
- Host harness test-tile-update-service.mjs failed: -Werror=sign-compare in unsigned/int asserts5 minutes
- Initial compile failed: missing version.txt in build root (fatal include in firmware_version.h)2 minutes
- Install time
- 78 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- node tools/run-tests.mjs exited 0: 248 passed, 95 skipped, 0 failed in 142.7s; arduino-cli compile --fqbn esp32:esp32:esp32p4:... (Waveshare 4B flags) exited 0 and reported 'Sketch uses 6750936 bytes (51%) of program storage space'; node tools/generate-web-assets.mjs --check, node tools/generate-device-profiles.mjs --check, node --check src/web/assets/admin.js, git diff --check all exited 0.
- Model tokens used
- 743,295
- Exact commit tested
- e0acbc94628d
- 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.
- Installed the firmware toolchain in `$HOME` (arbitrary-user, not system): `arduino-cli` 1.5.2-rc.… **Errors found and fixed** 1. Stale generated Web assets: `node tools/generate-web-assets.mjs --check` reported `admin_css_gzi… 2. Six host-C++ harness tests failed to compile under this container's GCC 13.3 with `-Wall -Wextra… - Enum/int ternary comparisons in production headers (`swipe_gestures.h`, `clock_format.h`, `tex… - Harness-side diagnostics: `memset` on a nontrivial `DeviceConfig` (`-Wclass-memaccess`) and si… **Verification (tier1 for host, tier2+ for firmware)** - Full suite: `node tools/run-tests.mjs` → **248 passed, 95 skipped, 0 failed in 142.7s**. 95 skips… - Firmware build: `arduino-cli compile` (Waveshare 4B / ESP32-P4, exact CI flags) → exit 0, `Sketch… - `node --check src/web/assets/admin.js`, `tools/generate-web-assets.mjs --check`, `generate-device… No real Home Assistant / MQTT broker / panel hardware was exercised — firmware behavior on hardware… **Changes left uncommitted** (per `AGENTS.md`, no commit unless asked): `src/core/config/swipe_gest…
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
- Recovered from all 6 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.
- Took 78 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 dashboard projects Argusic has installed and timed, HomeTiles was the 5th fastest to reach a running state, and 3 of 5 reached one at all.
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 | 1/3 | Runs with mocks | 92.00 | 0.16 |
Topics (from GitHub)
dashboardesp32esp32-p4esp32-s3guitionhome-assistanthome-automationlvglm5stackmqttsmart-hometouchscreenwall-panelwaveshare
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hometiles)Questions
- Does HomeTiles run?
- HomeTiles runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 78 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test HomeTiles?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e0acbc94628d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test HomeTiles?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does HomeTiles take to install?
- 78 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 HomeTiles need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing HomeTiles?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does HomeTiles compare with the alternatives?
- Of the 5 dashboard projects Argusic has installed and timed, HomeTiles was the 5th fastest to reach a running state, and 3 of 5 reached one at all.
- Where is the evidence for HomeTiles?
- 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.