Repository navigation
Austrian Smartmeter for Home Assistant
Changelog
All notable changes to the Austria Smartmeter integration will be documented in this file.
[1.1.6] - 2025-01-03
🚀 Added
-
Internationalization (i18n): Added full translation support for Config Flow and Options.
-
Languages supported: English (
en), German (de), French (fr), Italian (it), Spanish (es). -
Diagnostic Sensors: New entities added to the "Diagnostic" category for better insights:
-
Detailed Address (Street, Zip, City, Stair, Door).
-
Metering Point ID & Customer ID.
-
Facility Type (e.g., "Consumption" or "Feed-in").
-
Smart Meter Market Readiness status.
-
Contract Active status.
-
Statistic Sensors: Added dedicated sensors for daily statistics provided by the API:
-
Consumption Yesterday -
Consumption Day Before Yesterday -
Device Info: The device registry is now fully populated with:
-
Serial Number (
geraetNumber). -
Hardware Version (
equipmentNumber). -
Manufacturer (e.g., "Wiener Netze") and Model.
-
Link to the provider's configuration portal.
⚡ Changed
-
Entity Naming: Significantly improved the naming convention for sensors.
-
Old:
sensor.smart_meter_at001000..._energy_consumption_total(Hard to read). -
New:
sensor.friendly_name_energy_consumption_total(Uses the name set in the Web Portal, e.g., "Apartment"). -
Unit of Measurement: Strictly enforced Wh (Watt-hours) as the native unit for all energy sensors.
-
This ensures consistency with the Home Assistant Energy Dashboard and long-term statistics.
-
Removed dynamic conversion to kWh to prevent database corruption if API units fluctuate.
🐛 Fixed
-
Config Flow Crash (Error 500): Fixed a critical issue where opening the "Configure" options would crash with a
500 Internal Server Error. -
Resolved by fixing a read-only property conflict (
config_entry) in the Options Flow handler. -
Added robust error handling and default fallbacks for
scan_interval. -
Crash on Missing Data: Fixed
AttributeErrorcrashes when the API returnednullfor statistic values. -
Coordinator Logic: Fixed an issue where consumption statistics were not correctly assigned to the corresponding meter if the API response structure varied (list vs. dict).
⚠️ Breaking Changes
- Entity ID Changes: Due to the naming cleanup, Entity IDs have changed.
- If you used
sensor.smart_meter_at...in your Lovelace dashboards or automations, you will need to update them to the new Entity IDs (check Settings > Devices & Services > Austria Smartmeter to find the new names).