Home-Assistant-Mail-And-Packages
Home Assistant integration providing day of package counts and USPS informed delivery images.
Runs with mockssource: GitHubPythonMITcommit f2a8ecfedb56
Python, MIT licensed. The project labels itself: home assistant, home assistant config, home automation, homeassistant, lovelace card and lovelace custom card.
Home-Assistant-Mail-And-Packages runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All dependencies install cleanly, 103 of 109 tests pass (6 fail due to pre-existing test expectation bugs), the integration compiles without errors and loads in HA 2025.1.4's custom component framework.
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.
- pip install -r requirements_test.txt failed building numpy on Python 3.12 (old setuptools/pyproject.toml incompatibility)8 minutes
- mock_listdir fixture patched os.listdir globally, breaking HA loader's pathlib.Path.iterdir() which uses os.listdir internally, causing 'Integration not found'5 minutes
- config_entry.version = 4 in async_migrate_entry fails on HA 2025.1.4 (version is now a frozen attr)3 minutes
- config_entry.options = config_entry.data fails (options is a frozen attr)1 minute
- .called_with() is not a valid mock assertion in Python 3.12+1 minute
- entry.version = 2 fails (version is a frozen attr)0.5 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 56 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- PYTHONPATH=/work/repo .venv/bin/python -m pytest tests/ --timeout=30 returned '103 passed, 6 failed, 1 error'. The 6 failures are pre-existing test bugs (mock argument mismatches, locale date parsing) present in the original repo, not introduced by fixes.
- Model tokens used
- 7,179,257
- Exact commit tested
- f2a8ecfedb56
- 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.
}
],
\"test_depth\": \"tier2_mock\",
\"notes\": \"103 pytest tests pass, 6 fail (pre-existing test expectation bugs, not regression)…
\"verified_how\": \"PYTHONPATH=/work/repo .venv/bin/python -m pytest tests/ --timeout=30 return…
\"final_state\": \"All dependencies install cleanly, 103 of 109 tests pass (6 fail due to pre-e…
}
print(\"ARGUSIC_RESULT: \" + json.dumps(result))
PYEOF" in /work/repo
succeeded in 0ms:
tokens used
7,179,257Replay 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.
- 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.
- Took 15 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 home-assistant projects Argusic has installed and timed, Home-Assistant-Mail-And-Packages was the 4th fastest to reach a running state, and 2 of 4 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 | 2/3 | Did not run | 20.00 | 0.47 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 1.39 |
Topics (from GitHub)
home-assistanthome-assistant-confighome-automationhomeassistantlovelace-cardlovelace-custom-card
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/home-assistant-mail-and-packages)Questions
- Does Home-Assistant-Mail-And-Packages run?
- Home-Assistant-Mail-And-Packages runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test Home-Assistant-Mail-And-Packages?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f2a8ecfedb56. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Home-Assistant-Mail-And-Packages?
- The run that produced this verdict cost $1.39: 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-Mail-And-Packages take to install?
- 15 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-Mail-And-Packages need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Home-Assistant-Mail-And-Packages?
- 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 Home-Assistant-Mail-And-Packages compare with the alternatives?
- Of the 4 home-assistant projects Argusic has installed and timed, Home-Assistant-Mail-And-Packages was the 4th fastest to reach a running state, and 2 of 4 reached one at all.
- Where is the evidence for Home-Assistant-Mail-And-Packages?
- 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.