HomeAssistant-Tapo-Control
Control for Tapo cameras as a Home Assistant component
Could not verifysource: GitHubPythonApache-2.0commit 1b7a7d6fa671
Python, Apache-2.0 licensed. The project labels itself: camera, cameras, home assistant, home automation, homeassistant, homeassistant custom component, ptz and tapo.
Argusic could not get HomeAssistant-Tapo-Control running. An Argusic agent installed it in 9 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 15 Python modules of Tapo: Cameras Control v7.1.27 import cleanly in Python 3.12.3 venv with HA 2025.1.4. All translation, manifest, and config files validate. Cannot run without physical Tapo camera hardware and a running Home Assistant instance.
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 77.5 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.
- onvif-zeep-async 4.3.0 requires aiohttp>=3.12.9 but HA 2025.1.4 needs aiohttp==3.11.112 minutes
- externally-managed-environment preventing system pip install1 minute
- haffmpeg package not found (pip install haffmpeg fails)1 minute
- Missing Python packages: aiofiles, numpy1 minute
- Manifest requires HA 2026.9.0 but installed HA is 2025.1.4
- Install time
- 9 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- python -m compileall -q custom_components/tapo_control/ passed; python -c '... all 15 modules imported OK'; json/yaml validation of all config files passed
- Model tokens used
- 73,687
- Exact commit tested
- 1b7a7d6fa671
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
{"msg": "haffmpeg package not found (pip install haffmpeg fails)", "fix": "Installed ha-ffmpeg …
{"msg": "onvif-zeep-async 4.3.0 requires aiohttp>=3.12.9 but HA 2025.1.4 needs aiohttp==3.11.11…
{"msg": "Missing Python packages: aiofiles, numpy", "fix": "Installed both", "minutes": 1},
{"msg": "Manifest requires HA 2026.9.0 but installed HA is 2025.1.4", "fix": "Not blocking - al…
],
"test_depth": "tier3_none",
"notes": "Home Assistant custom component (Tapo camera integration). No test suite in repo. All 1…
"verified_how": "python -m compileall -q custom_components/tapo_control/ passed; python -c '... a…
"final_state": "All 15 Python modules of Tapo: Cameras Control v7.1.27 import cleanly in Python 3…
}
tokens used
73,687Replay 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 9 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
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 | Unverified | 75.00 | 0.18 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.10 |
Topics (from GitHub)
cameracamerashome-assistanthome-automationhomeassistanthomeassistant-custom-componentptztapo
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/homeassistant-tapo-control)Questions
- Does HomeAssistant-Tapo-Control run?
- Argusic could not verify that HomeAssistant-Tapo-Control runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test HomeAssistant-Tapo-Control?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1b7a7d6fa671. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test HomeAssistant-Tapo-Control?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does HomeAssistant-Tapo-Control take to install?
- 9 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-Tapo-Control need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing HomeAssistant-Tapo-Control?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for HomeAssistant-Tapo-Control?
- 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.