v0.8.0 - support sub-entries and many QOL improvements by Poshy163 · Pull Request #225 · CharlesGillanders/homeassistant-alphaESS

Poshy163 · 2026-02-07T08:22:39Z

Breaking Changes

Config entry version bumped from v1 to v2 - existing
entries are auto-migrated
Device customizations (custom names, area
assignments) are reset during migration
Add minimum version of 2026.1.0
Add time entitles for charging/discharging slots (aimed towards larger automations)

New Features:

Today's Generation & Income Sensors - Added
epvtoday and todayIncome from getSumDataForCustomer
batHighCap/batUseCap API Push - Number entities now
immediately push to API on change instead of only
saving locally
Grid Charge/Discharge Switches - New switch
platform with toggles for gridCharge and ctrDis,
preserves all existing config when toggling
Config Subentries: Each inverter and EV charger is
now a separate subentry under the main integration
entry
- EV Charger Current - Replaced read-only sensor with
  controllable number entity (6-32A), calls setEvChargerCurrentsBySn API
- Inverters can be added/reconfigured individually
  with their own IP address
- EV chargers can be added/reconfigured individually
  with parent inverter association
Per-Inverter IP Address: Each inverter can have its
own local IP address configured
Auto-Discovery: Inverters are auto-discovered from
the API during setup; EV chargers are auto-discovered
on first data fetch
Per-Inverter Local Data Fallback: When cloud API is
unavailable, each inverter with a configured IP gets
its own local data independently

Migration (v1 → v2)

Old IPAddress from entry data/options is preserved
and assigned to the first inverter's subentry
Old devices are cleaned up on first startup after
migration to avoid "devices that don't belong to a
sub-entry" duplicates
Entity unique IDs are preserved so automations
continue to work

…er entered

Poshy163 · 2026-02-12T09:14:03Z

Migrations from 0.7.6 -> 0.8.0 have been confirmed working. w/ multiple tests

…t for next poll to update it)

Copilot

Pull request overview

This PR bumps the AlphaESS Home Assistant integration to v0.8.0, introducing a v2 config entry model that uses sub-entries per inverter (and EV charger), plus new controllable entities and improved local-data fallback behavior.

Changes:

Add config entry v2 with inverter sub-entries, inverter bind/reconfigure flows, and EV-charger sub-entry auto-creation/migration support.
Add new platforms/entities: grid charge & discharge control switches, charge/discharge time slot time entities, and new “Today’s Generation/Income” sensors.
Add per-inverter local IP mapping and independent local fallback fetch when the cloud API is unavailable; bump minimum Home Assistant version to 2026.1.0.

Reviewed changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 17 comments.

Show a summary per file

File	Description
hacs.json	Declares HA minimum version requirement (2026.1.0).
custom_components/alphaess/manifest.json	Bumps integration version to 0.8.0.
custom_components/alphaess/const.py	Adds subentry types/keys and registers new platforms (switch/time).
custom_components/alphaess/config_flow.py	Implements v2 config flow + inverter subentry flow (bind/reconfigure/unbind).
custom_components/alphaess/init.py	Builds coordinator using subentries, handles v1→v2 migration, and cleans up devices/entities.
custom_components/alphaess/coordinator.py	Adds per-inverter IP handling, local fallback improvements, and new summary fields.
custom_components/alphaess/sensor.py	Refactors sensor setup to be subentry-based and adds device-info builders.
custom_components/alphaess/sensorlist.py	Adds new sensor/switch/time/number descriptions (today stats, EV current, switches, time slots).
custom_components/alphaess/number.py	Adds EV charger current number + pushes inverter cap changes to the API on change.
custom_components/alphaess/button.py	Refactors button setup for subentries and adds per-subentry notification preference.
custom_components/alphaess/switch.py	New switch platform for gridCharge/ctrDis toggles.
custom_components/alphaess/time.py	New time platform for charge/discharge slot start/end times.
custom_components/alphaess/enums.py	Adds enum keys for new entities (times, today stats, switches).
custom_components/alphaess/entity.py	Adds Switch/Time entity description dataclasses.
custom_components/alphaess/strings.json	Adds/updates UI strings for subentries and new entities.
custom_components/alphaess/translations/en.json	Updates EN translations for subentries and removed global IP option.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

custom_components/alphaess/number.py

custom_components/alphaess/__init__.py

custom_components/alphaess/button.py

custom_components/alphaess/time.py

custom_components/alphaess/coordinator.py

custom_components/alphaess/config_flow.py

custom_components/alphaess/number.py

custom_components/alphaess/sensor.py

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot

Pull request overview

Copilot reviewed 16 out of 16 changed files in this pull request and generated 12 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-02-12T10:03:59Z

custom_components/alphaess/config_flow.py

        if user_input:
-
            try:
-                await validate_input(self.hass, user_input)
-
+                result = await validate_input(self.hass, user_input)
            except CannotConnect:
                errors["base"] = "cannot_connect"


Config flow doesn’t set a unique_id / abort if the same account is already configured. This can create duplicate config entries for the same AppID and duplicate polling/entities. Consider async_set_unique_id(AppID) + async_abort_if_unique_id_configured() (or another stable identifier).

custom_components/alphaess/number.py

custom_components/alphaess/coordinator.py

Copilot · 2026-02-12T10:04:00Z

custom_components/alphaess/coordinator.py

            f"Reset Charge and Discharge configuration - "
            f"Charge: {results['charge']}, Discharge: {results['discharge']}"
        )
+        # Optimistically update so switches reflect the change immediately
+        if serial in self.data:


reset_config() reads bat_use_cap / bat_high_cap using AlphaESSNames.batUseCap / AlphaESSNames.batHighCap as dict keys (a few lines above). Those enum values are human-readable strings and won’t match the values saved by the number entities (which use keys like "batUseCap"/"batHighCap"), so reset may always fall back to defaults. Use the same keying scheme as update_charge/update_discharge (or read from self.data).

custom_components/alphaess/coordinator.py

custom_components/alphaess/switch.py

Copilot · 2026-02-12T10:04:01Z

custom_components/alphaess/number.py

    async def async_set_native_value(self, value: float) -> None:
        self._attr_native_value = value
        await self.save_value(value)
        self.async_write_ha_state()



async_set_native_value() persists and publishes the new number value before performing the API write. If the API call fails, HA will show/restore a value that never applied. Only persist/update state after a successful API call, or revert on exception.

Copilot · 2026-02-12T10:04:01Z

custom_components/alphaess/number.py

+        if self.key is AlphaESSNames.batHighCap:
+            grid_charge = data.get("gridCharge", 1)
+            result = await self._coordinator.api.updateChargeConfigInfo(
+                self._serial,
+                value,


The new API push in async_set_native_value() isn’t wrapped in try/except. If updateChargeConfigInfo/updateDisChargeConfigInfo raises, the exception will propagate and the entity will stay at the optimistic value. Handle exceptions and revert/log appropriately.

custom_components/alphaess/coordinator.py

Copilot · 2026-02-12T10:04:02Z

custom_components/alphaess/config_flow.py

            ): bool,
        }

-        return self.async_show_form(step_id="init", data_schema=vol.Schema(schema), errors=errors)
+        return self.async_show_form(step_id="init", data_schema=vol.Schema(schema))


Options flow still includes the "Disable Notifications On Charge/Discharge Confirmation" option in the schema, but the UI translations were removed and the runtime behavior now appears to be per-inverter (CONF_DISABLE_NOTIFICATIONS). Either remove this option here or wire it up to update all inverter subentries and restore its translation.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

CharlesGillanders

That's an enormous amount of work. I'm in awe. Thanks for flagging the breaking changes. That's going to be important that it's clearly called out.

Poshy163 added 4 commits February 7, 2026 18:51

support sub-entires

ab32f4b

Separate chargers from inverters

9f0f429

remove minimum version

996a436

Update strings and remove redundant code

3105303

Poshy163 changed the title ~~support sub-entries~~ support sub-entries and QOL improvements Feb 7, 2026

Poshy163 added 9 commits February 7, 2026 20:09

Add minimum version of 2026.1.0

3320d20

Make dataclasses frozen

f3873ed

Update sensors for value mapping (local data)

75d570a

Fix migration of ID's

2e9ef43

add SMILE-G3-B5-INV to list of known inverters

63509ae

add SMILE-G3-T10-INV as a known inverter

7ba1b26

Add time entitles

d2a66cd

limit to 15 minute intervals and update to nearest 15 mins other numb…

ee8f9d8

…er entered

Add rest of the missing entities + bug fixes and QOL changes

a18b0b2

Poshy163 changed the title ~~support sub-entries and QOL improvements~~ v0.8.0 - support sub-entries and many QOL improvements Feb 10, 2026

Poshy163 added 4 commits February 10, 2026 23:16

Add bind/unbind selection

b7a87e6

Re-add ip address/notifcations toggle

83a5545

fix for notifications not working

34b7370

Merge branch 'main' into support-sub-entries

4d6e71e

Poshy163 added 2 commits February 12, 2026 19:48

switch now flips in the UI and stays till next poll

31c4412

toggle sliders when charge/discharge buttons are pressed (and not wai…

3a1ffde

…t for next poll to update it)

Poshy163 marked this pull request as ready for review February 12, 2026 09:29

Poshy163 requested review from CharlesGillanders and Copilot and removed request for CharlesGillanders February 12, 2026 09:29

Copilot started reviewing on behalf of Poshy163 February 12, 2026 09:29 View session

Copilot AI reviewed Feb 12, 2026

View reviewed changes

Update custom_components/alphaess/sensorlist.py

02fd597

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Poshy163 and others added 3 commits February 12, 2026 20:10

Update custom_components/alphaess/sensor.py

0ba7d30

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

improvements from code review

942d97b

more code review changes

1439cb2

Poshy163 requested a review from Copilot February 12, 2026 09:53

Copilot started reviewing on behalf of Poshy163 February 12, 2026 09:53 View session

Copilot AI reviewed Feb 12, 2026

View reviewed changes

Poshy163 and others added 2 commits February 12, 2026 20:37

Update custom_components/alphaess/coordinator.py

509599b

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

final code review improvements

5d35d82

CharlesGillanders approved these changes Feb 12, 2026

View reviewed changes

Poshy163 merged commit bdab540 into main Feb 12, 2026
1 check passed

Poshy163 deleted the support-sub-entries branch February 24, 2026 12:42

Conversation

Poshy163 commented Feb 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Poshy163 commented Feb 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

CharlesGillanders left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Poshy163 commented Feb 7, 2026 •

edited

Loading

Poshy163 commented Feb 12, 2026 •

edited

Loading