esphome-intercom
VoIP Stack for Home Assistant and ESPHome: SIP audio/video calls, dashboard phones, ESP32 intercoms, ring groups, trunks and call routing through HA automations.
Runssource: GitHubPythonMITcommit 79c860f9c609
Python, MIT licensed. The project labels itself: esp32, esphome, hacs, home assistant, home assistant custom component, home automation, homeassistant and intercom.
esphome-intercom runs. An Argusic agent installed it in 8 minutes and hit 8 errors on a clean machine with no GPU, and the whole session was recorded.
With the coordinated ESP component sources in .test-deps, the project runner's software-full mode passed 2570 tests plus 219 subtests, the browser suite passed 41 real-Chromium tests, ESPHome generated the native firmware C++ (2050332 bytes), and a live UDP REGISTER was challenged 401 then authenticated 200 with registration and deregistration observed.
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 95 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- pytest-homeassistant-custom-component==0.13.365 needs Python >=3.14; container has 3.12 and no root12 minutes
- Node.js 18.19.1 loads the frontend .js ESM modules as CommonJS (Unexpected token 'export'; named export not found)8 minutes
- test_yaml_paths_contract asserted a literal ../../../../esphome-esp-video-camera/components that cannot exist under root-owned /work8 minutes
- Fallback plugin 0.13.205 pins HA 2025.1.4, which lacks 2026 APIs and auto-disabled sockets, breaking test_conference6 minutes
- Coordinated sibling ESP component repos could not be created under root-owned /work (PermissionError)4 minutes
- test_esphome_upstream_alignment failed: a hard-coded sibling path was not a filesystem path3 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 82 minutes
- Errors hit and fixed
- 8 hit, 6 fixed with no human help
- How the result was proved
- scripts/test_suite.sh software-full exited 0 with 2570 passed, 219 subtests, 0 failed; scripts/test_suite.sh browser exited 0 with 41 passed; esphome config and compile --only-generate both exited 0 and generated main.cpp (2050332 bytes); loopback UDP REGISTER sequence returned 401 then 200 OK with a binding, and a fresh-nonce deregister returned 200 OK with 0 bindings; ruff check reported all checks passed
- Model tokens used
- 1,355,637
- Exact commit tested
- 79c860f9c609
- 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.
- Ran the suites through the project runner, plus a live loopback SIP check, and verified ruff. **Results** - `scripts/test_suite.sh software-full` (HA-only and Node-dependent modules excluded): **2570 passe… - `scripts/test_suite.sh browser`: **41 passed, 2 deselected**, real Chromium. - Native ESPHome build: `esphome config` rc 0, `compile --only-generate` rc 0, 2,050,332-byte `main… - Live SIP over UDP against the real registrar: unauthenticated REGISTER → 401, authenticated → 200… - `ruff check …` → "All checks passed!". **Gap I could not close** - The HA suite needs `pytest-homeassistant-custom-component==0.13.365`, which requires Python 3.14;… - Node 18 here treats the frontend `.js` modules as CommonJS, so the scripts that `import()` them f… - Changes: `scripts/yaml_paths.sh:13` now honors `ESP_VIDEO_CAMERA_REPO`/`VOIP_STACK_REPO`/`AUDIO_S… - One transient failure: `test_dahua_audio_socket.py` invite timeout under full load; it passed 6/6…
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 8 minutes.
- 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
- Hit 8 errors during setup, 2 of which were not solved.
- 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.
- A quick evaluation: it was running 8 minutes after the clone.
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)
esp32esphomehacshome-assistanthome-assistant-custom-componenthome-automationhomeassistantintercomsipsoftphonevideo-callsvoip
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/esphome-intercom)Questions
- Does esphome-intercom run?
- Yes. esphome-intercom runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test esphome-intercom?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 79c860f9c609. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test esphome-intercom?
- The run that produced this verdict cost $0.69: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does esphome-intercom take to install?
- 8 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 esphome-intercom need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing esphome-intercom?
- 8 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.
- Where is the evidence for esphome-intercom?
- 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.