homeassistant-blitzortung

Custom Component for fetching lightning data from blitzortung.org

Runssource: GitHubPythonMITcommit 2c3b4a35438c

Python, MIT licensed. The project labels itself: blitzortung, home assistant, home automation and lightning network.

homeassistant-blitzortung runs. An Argusic agent installed it in 32 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.

The Home Assistant blitzortung integration builds on Python 3.14.9, passes all 98 tests plus ruff/prek checks; ws-client connects to the live blitzortung websocket and relays decoded lightning strikes to a verified local MQTT broker and stays running, after an asyncio fix for Python 3.14; only the upstream strike-frame decoding beyond the first frames remains unverified.

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 93.3 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
93.3 / 100
cost of the verifying run
$0.48 (measured)
recorded runs
1
last tested
stars
358
forks
54
open issues
3
watchers
16
size
1 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 homeassistant-blitzortung, 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.

  • Upstream blitzortung websocket stream: ws-client's LZW decoder cannot decode current server frames (ws3/ws7 return HTTP 502; ws1/ws8 serve frames in an encoding the pinned client code doesn't parse); also blitzortung.ha.sed.pl:1883 closes TCP without CONNACK45 minutes
  • Container only had Python 3.12 but requirements need 3.13/3.14; initial pip install failed for pytest-homeassistant-custom-component==0.13.3668 minutes
  • ws-client crashed on Python 3.14: asyncio.get_event_loop() with no running loop raises RuntimeError5 minutes
Install time
32 minutes
Cold machine to finish
34 minutes
Errors hit and fixed
3 hit, 2 fixed with no human help
How the result was proved
pytest tests -> '98 passed, 36 warnings in 1.58s'; ruff check -> All checks passed; ruff format --check -> '12 files already formatted'; prek run (6 hooks) -> all Passed; local MQTT broker on 127.0.0.1:18830 -> paho client received 'GOT2 test/delivery b'after-sub-probe'', delivered: 1; ws-client mqtt://127.0.0.1:18830 -j -l INFO -> 'connected to mqtt server', 'connected to wss://ws8.blitzortung.org:443/', 40-52 valid strike topic lines, process still running
Model tokens used
2,097,772
Exact commit tested
2c3b4a35438c
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.

- Upstream blitzortung websocket protocol mismatch (ws-client's LZW decoder can't decode current se…
- Early broker harness instability (background-daemon SIGKILL on test-process cleanup; wrong depend…
## Verification evidence (only what I observed)
- `pytest tests` → `98 passed` on Python 3.14.9
- `ruff check` → all checks passed; `ruff format --check` → 12 files already formatted; `prek run .…
- Amqtt MQTT broker on `127.0.0.1:18830`: TCP connect, subscriber-side delivery confirmed (`GOT2 te…
- `ws-client mqtt://127.0.0.1:18830 -j -l INFO` → logs `INFO:ws_client.client:connected to mqtt ser…
- Live blitzortung websocket hosts `ws1`/`ws8` produce data; `ws3`/`ws7` return HTTP 502. `blitzort…
- HA integration import works: `geohash_overlap(50.0, 10.0, 100)` → `{'u0x', 'u28', 'u1n', 'u0w', '…
**Test depth:** tier1_real (98 pytest tests + live MQTT/websocket connections, including actually d…
**Final state:** One tracked change remains: `ws_client/ws_client/client.py` (one-line `asyncio.run…
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 32, "e…

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 32 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 3 errors during setup, 1 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.

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/3Runs93.330.48

Topics (from GitHub)

blitzortunghome-assistanthome-automationlightning-network

Embed the badge

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

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

Questions

Does homeassistant-blitzortung run?
Yes. homeassistant-blitzortung runs. Argusic installed and launched it on a clean machine in 32 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test homeassistant-blitzortung?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2c3b4a35438c. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test homeassistant-blitzortung?
The run that produced this verdict cost $0.48: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does homeassistant-blitzortung take to install?
32 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-blitzortung need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing homeassistant-blitzortung?
3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for homeassistant-blitzortung?
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