hass-entso-e

Integration for Home Assistant to fetch day ahead energy prices from European countries via ENTSO-e Transparency Platform

Runs with mockssource: GitHubPythonApache-2.0commit cbdf67ac0e73

Python, Apache-2.0 licensed. The project labels itself: day ahead, day ahead auction, day ahead market, electricity market, electricity prices, energy, energy prices and entso e.

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

With pinned pycares and the two small source fixes, the entsoe component installs into a Home Assistant 2025.1.4 config, HA starts and serves 302 on :8123 with the component loaded, its 5 unit tests pass, and the client retrieves 24 hourly prices end-to-end from a schema-correct mock ENTSO-e API.

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.30 (measured)
recorded runs
1
last tested
stars
280
forks
65
open issues
52
watchers
19
size
0 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 hass-entso-e, 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.

  • test_api_client.py used Windows-only backslash paths (..\, .\datasets\) and top-level relative import, so tests could not run on Linux12 minutes
  • HA default_config can not build/install C-extension deps (pyspeex-noise, netifaces, mutagen, libturbojpeg) because Python.h and system libs are missing without root10 minutes
  • test_be_15M_avg failed: parser did not fill sparse 15-min period hours into hourly buckets (expected 36.30 at 00:00-02:00; got 38.94 and missing keys)8 minutes
  • HA crash: aiodns 3.2.0 + pycares 5.2.1 TypeError Channel.getaddrinfo() on DNS resolution6 minutes
Install time
45 minutes
Cold machine to finish
40 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
.venv/bin/python -m unittest discover -s custom_components/entsoe/test -p test_*.py -> Ran 5 tests, OK; mock API fetch: asyncio.run(EntsoeClient(fake-mock-key).query_day_ahead_prices(BE, 2024-10-07T22Z, 2024-10-08T22Z)) -> 24 hourly prices (64.98..50.0); hass -c ha_config -v -> HTTP 302 on :8123, process alive, log Loaded entsoe from custom_components.entsoe
Model tokens used
791,198
Exact commit tested
cbdf67ac0e73
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

The end of the recording

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

- This repo is a Home Assistant (HA) custom component; there is no repo-level install script. Stand…
- Installed `.venv` with `homeassistant 2025.1.4` (brings `aiohttp`, `pytz`), copied the component …
**Errors fixed**
- Windows-only paths in `test_api_client.py` (`..\\`, `.\\datasets\\`) and a top-level relative imp…
- HA crash: `aiodns 3.2.0` + `pycares 5.2.1` raises `TypeError: Channel.getaddrinfo()` on any DNS →…
- HA `default_config` can't build C-extension deps (`pyspeex-noise`, `netifaces`, `mutagen`, libtur…
- `test_be_15M_avg` failed: parser didn't fill sparse 15-min period hours into hourly buckets per t…
**Verified**
- `unittest discover -s custom_components/entsoe/test` → `Ran 5 tests ... OK`.
- End-to-end over real HTTP: schema-correct mock ENTSO-e API on `127.0.0.1:8125`; `EntsoeClient.que…
- `hass -c ha_config -v` → HTTP 302 on `:8123`, process stayed alive, log shows `Loaded entsoe from…
Parting note: a real ENTSO-e API key isn't available in this container; the mock covers the fetch/p…

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 45 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.30

Topics (from GitHub)

day-aheadday-ahead-auctionday-ahead-marketelectricity-marketelectricity-pricesenergyenergy-pricesentso-eentsoehacshome-assistanthome-automationhomeassistantintegration

Embed the badge

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

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

Questions

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