homeassistant_espscreen

Tessera: beautiful, easy touch screens for Home Assistant on affordable ESP32 panels, 2.8 to 10.1 inch (CYD, Guition, Waveshare). Drag-and-drop editor, no YAML, no MQTT.

Runssource: GitHubhomepagePythonAGPL-3.0commit 19a95b718101

Python, AGPL-3.0 licensed. The project labels itself: cyd, esp32, esp32 2432s028r, esp32 p4, esp32 s3, esphome, guition and hass addon.

homeassistant_espscreen runs. An Argusic agent installed it in 48 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Python and C++ test suites pass fully (882 + 33/33), web editor builds and its 366 tests pass, all package/board/icon/translation checks pass, server runs and serves the editor on port 8099, with the only unresolved issue being no ESP32 toolchain in this container to compile firmware binaries.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.15 (measured)
recorded runs
2
last tested
stars
1,255
forks
203
open issues
119
watchers
9
size
580 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 homeassistant_espscreen, 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.

  • Node 18 too old for web editor (requires >=22.12)5 minutes
  • Static assets directory missing from git working tree (git checkout -- failed during editor build's rm -rf)3 minutes
  • C++ test test_alert_overlay.cpp: g++ -Werror=parentheses on && within ||2 minutes
  • C++ test test_settings_screen.cpp: g++ -Wdangling-reference false positives on const Row& from row_named()1 minute
Install time
48 minutes
Cold machine to finish
24 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
cd /work/repo && PYTHON=/tmp/venv/bin/python bash tools/check.sh -> Python tests PASS 882 tests; CXX='g++ -Wno-dangling-reference' bash -c 'C++ tests 33/33 passed'; npm test (Node 22) -> 24 test files, 366 tests passed; npm run build -> Vite built editor; /tmp/venv/bin/python tools/check_packages.py -> PASS; server.py launches as 'Home Assistant temporarily unavailable' (expected, no HA running)
Model tokens used
233,354
Exact commit tested
19a95b718101
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.

OK  page_service
OK  page_capabilities
OK  header_bar
OK  history_card
OK  feedback
OK  screen_labels
All server modules import correctly. Now let me produce the final ARGUSIC_RESULT.
2026-11-18T04:42:23.269068Z ERROR codex_core::session: failed to record rollout items: thread 01a1e…
2026-11-18T04:42:23.269103Z ERROR codex_core::session: failed to record rollout items: thread 01a1e…
tokens used
233,354
All server modules import correctly. Now let me produce the final ARGUSIC_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.
  • Installed in 48 minutes.
  • Recovered from all 4 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 AGPL-3.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.15
Argusic Runner1/3Runs100.000.22

Topics (from GitHub)

cydesp32esp32-2432s028resp32-p4esp32-s3esphomeguitionhass-addonhome-assistanthome-automationiotlvglsmart-hometouchscreenwaveshare

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/homeassistant_espscreen.svg)](https://argusic.com/subject/homeassistant-espscreen)

Questions

Does homeassistant_espscreen run?
Yes. homeassistant_espscreen runs. Argusic installed and launched it on a clean machine in 48 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test homeassistant_espscreen?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 19a95b718101. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test homeassistant_espscreen?
The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does homeassistant_espscreen take to install?
48 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 homeassistant_espscreen need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing homeassistant_espscreen?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for homeassistant_espscreen?
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.

Discussion