Skip to content

Per-Inverter Subentries & Advanced Controls

Choose a tag to compare

View all tags
@Poshy163 Poshy163 released this 12 Feb 12:45
v0.8.0
bdab540
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Breaking Changes

  • Config entry version bumped from v1 to v2. Existing entries are automatically migrated, but device customizations (custom names, area assignments) will be modified to append the inverter serial number. As a result, some automations/UI components referencing device names may break and require updating.
  • Minimum Home Assistant version is now 2026.1.0.

New Features

Config Subentries

Each inverter and EV charger is now a separate subentry under the main integration entry. Inverters can be added, reconfigured, or unbound individually with their own local IP address. EV chargers are auto-discovered and associated with a parent inverter.

Grid Charge/Discharge Switches

New switch platform with toggles for grid charge and controlled discharge. Switches update in the UI immediately rather than waiting for the next poll cycle.

Charge/Discharge Time Slot Entities

New time entities for configuring charging and discharging time slots, limited to 15-minute intervals. Aimed at enabling more advanced automations.

Today's Generation and Income Sensors

Added epvtoday and todayIncome sensors from the getSumDataForCustomer API endpoint.

EV Charger Current Control

Replaced the read-only EV charger current sensor with a controllable number entity (6-32A) that calls the setEvChargerCurrentsBySn API.

Immediate API Push for Battery Capacity

The batHighCap and batUseCap number entities now push changes to the API immediately on change, rather than only saving locally.

Per-Inverter Local Data Fallback

When the cloud API is unavailable, each inverter with a configured IP address fetches local data independently.

New Known Inverters

Added SMILE-G3-B5-INV and SMILE-G3-T10-INV to the list of known inverter models.

Migration (v1 to v2)

  • Existing IP address configuration is preserved and assigned to the first inverter's subentry.
  • Old devices are cleaned up on first startup after migration to avoid duplicate entries.
  • Entity unique IDs are preserved so existing automations continue to work.
Assets 2
Loading