v0.13.0b2
Pre-releaseThis release adds quarter-hourly EPEX price support for dynamic tariff contracts, completing the EPEX v2 migration and expanding the automation surface with new quarter-hourly triggers and conditions.
What's new
-
Quarter-hourly EPEX price sensors. Dynamic tariff contracts now get a complete set of quarter-hourly sensors: current price, next price, lowest price today, and highest price today. The integration automatically detects your contract's granularity from the EPEX v2 API response.
-
EPEX v2 endpoint migration. The integration now uses the new endpoint which requires authentication and enables dynamic granularity detection (hourly or quarter-hourly).
-
Expanded automation support. All EPEX-purpose triggers and conditions have been extended to support both hourly and quarter-hourly granularities. Use the new quarter-hourly variants in your automations.
-
Improved icon semantics. EPEX sensors now use clearer icons for better visual distinction.
-
Security hardening. Entity IDs in trigger debug logging and BANs in statistics device names are now masked to prevent PII exposure.
-
Developer experience improvements. Fixed lint script path detection, consolidated constants, and improved docstrings.
Upgrading
Coming from v0.13.0b1 or earlier? Nothing to do. Home Assistant picks up the new sensors automatically after restart. Existing entities, automations, and history carry over unchanged. Your login and business agreements stay as-is.
If you have a dynamic tariff contract, you'll see both hourly and quarter-hourly EPEX sensors appear automatically.
Beta notes
- This is the second beta of the v0.13 line, focusing on quarter-hourly EPEX support and automation improvements.
- Bug reports are welcome in the issues.
Known limitations
- Quarter-hourly sensors are available for all dynamic tariff contracts. The integration creates both hourly and quarter-hourly EPEX coordinators, and all dynamic customers receive sensors for both granularities.
- The integration automatically detects your contract type from the API response.
For the full technical details, see the CHANGELOG.