boschshc-hass

Home Assistant component for accessing Bosch Smart Home Controller using boschshcpy python library.

Runs with mockssource: GitHubPythonApache-2.0commit dee60155deb1

Python, Apache-2.0 licensed. The project labels itself: bosch smart home, boschshcpy, home assistant, home assistant component and smart home.

boschshc-hass runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

3388 unit tests pass (out of 3409 total in tests/bosch_shc/) with mock fixtures under Python 3.12 and Home Assistant 2025.1.4, with 3 compatibility patches applied (ZeroconfServiceInfo import fallback, OptionsFlowWithConfigEntry base class, config_entry constructor arg).

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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.21 (measured)
recorded runs
1
last tested
stars
239
forks
40
open issues
10
watchers
9
size
5 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 boschshc-hass, 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.

  • HA 2026.9.2+ required Python 3.14.2+, only Python 3.12 available; installed HA 2025.1.4 as fallback which works for most tests5 minutes
  • ZeroconfServiceInfo import path differs between HA versions (helpers.service_info.zeroconf vs components.zeroconf)2 minutes
  • OptionsFlowWithReload not available in HA 2025.1.4, replaced by OptionsFlowWithConfigEntry2 minutes
  • Harness tests incompatible with installed HA 2025.1.4 (require HA beta matching phccc version)1 minute
Install time
12 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 && . /tmp/venv/bin/activate && PYTHONPATH=/work/repo PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python3 -m pytest tests/bosch_shc/ -q -o addopts='' --tb=no returned 3388 passed, 21 skipped
Model tokens used
484,625
Exact commit tested
dee60155deb1
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

mock_module = types.ModuleType('homeassistant.helpers.service_info.zeroconf')
mock_module.ZeroconfServiceInfo = 'new_path_works'
sys.modules['homeassistant.helpers.service_info.zeroconf'] = mock_module
from homeassistant.helpers.service_info.zeroconf import ZeroconfServiceInfo
print('New path result:', ZeroconfServiceInfo)
\" 2>&1" in /work/repo
 succeeded in 0ms:
New path result: new_path_works
Now let me report the final result.
tokens used
484,625
Now let me report the final 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

  • Installed in 12 minutes.
  • Recovered from all 4 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.

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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 Runner1/3Runs with mocks92.000.21

Topics (from GitHub)

bosch-smart-homeboschshcpyhome-assistanthome-assistant-componentsmart-home

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/boschshc-hass.svg)](https://argusic.com/subject/boschshc-hass)

Questions

Does boschshc-hass run?
boschshc-hass runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test boschshc-hass?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit dee60155deb1. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test boschshc-hass?
The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does boschshc-hass take to install?
12 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 boschshc-hass need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing boschshc-hass?
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 boschshc-hass?
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.

Discussion