v2.0.2 – SmartMeter/battery fix, migration cleanup, 1200 W option
What's fixed in v2.0.2
SmartMeter and expansion battery entities missing after HA restart (Issue #7)
A regression in v2.0.0 caused SmartMeter 3P, BP2500, and smart plug entities to never be created after a Home Assistant restart or integration reload.
Root cause: The coordinator attribute config_entry_id was accidentally renamed to _config_entry_id (private) in v2.0.0, while the hasattr(self, "config_entry_id") guards in the sub-device discovery code still checked the old public name — always returning False. Fixed by restoring the public attribute.
Duplicate "unavailable" sensors after upgrade from v1.x
The v2.0.0 entity migration had two bugs that left orphaned entities showing "unavailable" or "unknown" alongside working duplicates:
- Main-device sensors with
battery_*orct_*in their name (e.g.Battery SoC,CT Status) were incorrectly skipped during migration. - Switch and number entities were migrated to the wrong unique-ID format (
…_main_swEpsinstead of…_switch_swEps).
v2.0.2 detects and removes these orphaned/wrongly-migrated entities on startup. No manual cleanup needed.
Upgrading from v1.x: After updating and restarting Home Assistant, duplicate "unavailable" entities are removed automatically. A browser hard-refresh (Ctrl+Shift+R) may be needed if the UI still shows stale entries.
What's new in v2.0.2
Max Feed-in Power: 1200 W option for SV3 Pro (Issue #5)
The Max Feed-in Power select entity now includes 1200 W (SV3 Pro) alongside 800 W and 2500 W (SV3 Pro Max). Previously, SV3 Pro users with 1200 W set in the app saw "unknown" in the select entity.
See CHANGELOG.md for full history.