[andreasthell]

Based on a HAR export of the EnergyInBalance dashboard from 2026-10-08.

New entities

• mFRR Activation Active (binary sensor): on while the battery is activated for mFRR. /ems/ActivationSchedule now lists the site's actual activations (MfrrUpActivation/MfrrDownActivation: start, end, power, ramp times). The list is fetched every 5 minutes, and the on/off state is re-evaluated every 60-second cycle so it turns off at the end time. Attributes describe the ongoing activation, or the latest one when off.
• mFRR Activation (event): fires up or down for each activation that appears after HA starts. Activations already listed at startup do not fire. An activation missing from a single response does not fire again when it reappears (seen activations are kept for 7 days).
• Total Revenue (sensor): the sum of /revenue?resolution=month since 2023-01-01, the same query the dashboard makes, with a per-service breakdown in by_service. If a response comes back empty, the sensor keeps its previous value.

activations is added to the slow updates shown on the Last API Poll sensor. Version is bumped to 1.6.0 (v1.6.0b1 is already published as a pre-release from this branch).

Docs

• docs/api.md is updated with all changes found in the export, marked 2026-10:
  • mFRR activations in ActivationSchedule; the hourly SpotPrice array is removed
  • the new mFRR EAM revenue service and resolution=month
  • Day/Month/Period resolutions and the new savings data types in SiteMeasurements
  • new fields in the site, energyflow, Statuses, CustomerDetail and diagnostics responses
• The README describes the new entities, explains that event entities show Unknown until they first fire, and documents both test suites.

Tests and CI

• tests_ha/ sets the integration up in Home Assistant 2026.10.0 (via pytest-homeassistant-custom-component, pinned in requirements_test_ha.txt) with a fake API client. It checks:
  • setup logs no errors, and unload works
  • events stay unknown until something happens, then fire with their attributes, and the last event survives a reload
  • the same activation in the next response is not a new event
  • the binary sensor and the total revenue sensor show the right values
• A new CI job, Tests (Home Assistant), runs tests_ha/ on Python 3.14, and releases now wait for it. It is a separate job because the stubs in tests/ replace homeassistant in sys.modules.

Local results: 115 stubbed tests pass, 6 real-HA tests pass on 2026.10.0, and ruff check/format are clean. As a check that the tests catch real failures, temporarily disabling the mFRR event made test_events_fire fail.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UwYSvzP667Y5pkhzfs8obW

---

Generated by Claude Code