Release v2.4.9-pre.4

• Catch ModbusIOException from setup by @WillCodeForCats in #515

Full Changelog: v2.4.9-pre.3...v2.4.9-pre.4

Release v2.4.9-pre.3

• Fix spelling in English translation by @WillCodeForCats in #510
• Add Italian translation by @WillCodeForCats in #511
• Refactor battery detection by @WillCodeForCats in #509
• Cleanup switch domain classes by @WillCodeForCats in #503
• Refactor meter detection by @WillCodeForCats in #512

Full Changelog: v2.4.9-pre.2...v2.4.9-pre.3

Release v2.4.9-pre.2

• Add support for third battery by @WillCodeForCats in #508

Full Changelog: v2.4.9-pre.1...v2.4.9-pre.2

Release v2.4.9-pre.1

This release changes the following battery device attributes into sensors:

• batt_charge_peak
• batt_discharge_peak
• batt_max_charge
• batt_max_discharge

These are listed as "nameplate" values in specs which implies static information, but it was noted that these values may change (Issue #495 and discussion #496). Values that are dynamic in their own right should be implemented as sensors. It's unknown if they are dynamic for all battery types or only some.

What's Changed

• Battery charge/discharge power as sensors by @WillCodeForCats in #501

Full Changelog: v2.4.8...v2.4.9-pre.1

Release v2.4.8

This release has a new AC energy class which now uses the inverter's native watt-hour units internally. This is mostly a quality improvement, but there is a backwards compatibility (not strictly breaking) change with entity naming.

The decision to previously use units in kWh for energy sensors was before Home Assistant had the ability users to select display precision and dynamically convert between units in a sensor class that supported different units. Now that the units and precision can be changed in the UI, having "kwh" in the sensor name is no longer appropriate and possibly inaccurate. The default energy unit will still be kWh unless changed in the sensory entity configuration.

Backwards compatibility note: units ('kwh') have been removed from the energy sensor names. This will affect new users to the integration that use templates intended for older versions. Upgrading as an existing user will not change any existing entity names. The internal Unique ID for these sensors is not changing.

Minimum version of Home Assistant is now 2023.12.0 with Python 3.11.

What's Changed

• Remove support for Python versions older than 3.11 by @WillCodeForCats in #484
• Min version HA 2023.12.0 by @WillCodeForCats in #481
• Bump github/codeql-action from 2 to 3 by @dependabot in #485
• New SolarEdgeACEnergy class by @WillCodeForCats in #482
• Use UnitOfTime enum class by @WillCodeForCats in #487
• Only log energy 'went backwards' once per event by @WillCodeForCats in #492

Full Changelog: v2.4.7...v2.4.8

Release v2.4.8-pre.3

• Only log energy 'went backwards' once per event by @WillCodeForCats in #492

Full Changelog: v2.4.8-pre.2...v2.4.8-pre.3

Release v2.4.8-pre.2

• Use UnitOfTime enum class by @WillCodeForCats in #487

Full Changelog: v2.4.8-pre.1...v2.4.8-pre.2

Release v2.4.8-pre.1

This release has a new AC energy class with improvements and now uses the inverter's native watt-hour units.

The decision to use fixed units in kWh predates the ability for Home Assistant users to select display precision and dynamically convert between units in a supported sensor class. But now that users can change the units and precision in the UI, having "kwh" in the sensor name is no longer appropriate and possibly inaccurate.

Backwards compatibility note: units have been removed from the energy (kWh) sensor names and entity names. This will affect new users to the integration that use templates intended for older versions. Upgrading as an existing user does not change existing entity names.

Minimum version of Home Assistant is now 2023.12.0 with Python 3.11.

What's Changed

• Remove support for Python versions older than 3.11 by @WillCodeForCats in #484
• Min version HA 2023.12.0 by @WillCodeForCats in #481
• Bump github/codeql-action from 2 to 3 by @dependabot in #485
• New SolarEdgeACEnergy class by @WillCodeForCats in #482

Full Changelog: v2.4.7...v2.4.8-pre.1

Release v2.4.7

This release updates the minimum version of pymodbus to address a potential bug with a setting in pymodbus versions older than 3.5.3 and has a whole bunch of internal changes that should go unnoticed, but improve the overall quality of the integration.

What's Changed

• Update some sensor classes by @WillCodeForCats in #423
• Set charge/discharge limit constants to 1MW by @WillCodeForCats in #446
• Bump WillCodeForCats/python-lint-action from 1.0.1 to 1.0.2 by @dependabot in #448
• Bump min pymodbus version to 3.5.4 by @WillCodeForCats in #451
• Refactor checks on switch platform by @WillCodeForCats in #455
• Refactor checks in binary sensor platform by @WillCodeForCats in #456
• Refactor checks on select platform by @WillCodeForCats in #457
• Refactor checks on number platform by @WillCodeForCats in #458
• Add object type to debug logging by @WillCodeForCats in #465
• Move RetrySettings class to top by @WillCodeForCats in #466
• Handle available TypeError in number platform by @WillCodeForCats in #467
• Raise TypeError from struct.error in helper by @WillCodeForCats in #468
• Increase retry limit by 1 by @WillCodeForCats in #471
• Update received requested logging by @WillCodeForCats in #472
• Add ReconnectDelayMax to const.py by @WillCodeForCats in #473 and #474
• Site limit values less than 0 display as 0 instead of unavailable by @WillCodeForCats in #476

Full Changelog: v2.4.6...v2.4.7

Release v2.4.7-pre.7

• Site limit values less than 0 display as 0 instead of unavailable by @WillCodeForCats in #476

Full Changelog: v2.4.7-pre.6...v2.4.7-pre.7