homeassistant-solax-modbus
SolaX Power Modbus custom_component for Home Assistant (Supports some AlphaESS, Growatt, Sofar, Solinteg, Solis, SRNE, Swatten)
Runssource: GitHubPythonApache-2.0commit 05a4a716140e
Python, Apache-2.0 licensed. The project labels itself: alphaess, growatt, hacs, home assistant, home automation, homeassistant, integration and modbus.
homeassistant-solax-modbus runs. An Argusic agent installed it in 1.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Project installs in a venv, all 949 unit tests pass after fixing a logging format mismatch where block.start could be a string but the format string expected an integer for hex formatting.
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
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.
- TypeError: %x format: an integer is required, not str in logging for block.start0.3 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- pytest tests/ -v exited 0, 949 passed
- Model tokens used
- 56,503
- Exact commit tested
- 05a4a716140e
- 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
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.
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 1.5, "errors": [{"msg": "T…
```
tokens used
56,503
All 949 tests pass cleanly. Let me compile the final report.
Here's a summary of what happened:
**Install**: Created a Python virtual environment, installed the project in editable mode, then ins…
**Bug found and fixed**: The first test run hit a `TypeError: %x format: an integer is required, no…
**Verification**: Ran the full test suite — **949 passed, 0 failed** in ~8 seconds. This project is…
```json
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 1.5, "errors": [{"msg": "T…
```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 1.5 minutes.
- Recovered from all 1 error 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 Apache-2.0, as reported by its host.
What did not, or is not known
- 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 1.5 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)
alphaessgrowatthacshome-assistanthome-automationhomeassistantintegrationmodbusmodbus-rtumodbus-serialmodbus-tcppythonqcellsrs485sofarsolaxsolintegsolissrneswatten
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/homeassistant-solax-modbus)Questions
- Does homeassistant-solax-modbus run?
- Yes. homeassistant-solax-modbus runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test homeassistant-solax-modbus?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 05a4a716140e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test homeassistant-solax-modbus?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does homeassistant-solax-modbus take to install?
- 1.5 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-solax-modbus need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing homeassistant-solax-modbus?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for homeassistant-solax-modbus?
- 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.