Release v2.2.1-pre.1

• Fix MMPPT validation conditions in #92

Full Changelog: v2.2.0...v2.2.1-pre.1

Release v2.2.0

This release contains a breaking change!

We fixed a problem observed in issue #61 (breaking change) with duplicate meters appearing after initial setup, and adds support for SolarEdge Synergy inverters (#86).

Recommended Upgrade Procedure

The change required to fix issue #61 will cause duplicate entity names for meters and batteries.

1. Delete integration from Settings -> Devices & Services.
2. Update to v2.2.0 release (manually or through HACS).
3. Re-Add the integration under Settings -> Devices & Services.

This procedure will preserve entity names. If updated in place, existing meter and battery entities will have a _2 suffix after updating to a v2.2.x or higher release. This procedure is not necessary if you are upgrading from a 2.2.0-pre.X release.

What's Changed

• Duplicate meters after initial setup in #83
• SolarEdge Synergy Multiple MPPT Support in #86
• Change exception class base name in #89
• Remove unused strings from language files in #90

Some inverters do not provide stable meter device information for unknown reasons. Unfortunately, using this information for the entity Unique ID causes new entities to be created if the inverter changes what it reports for that device. The issue has not been observed with the inverter device information, so the fix for #61 is to change the Unique ID for meter and battery entities to be based on the parent inverter's model and serial number.

Full Changelog: v2.1.3...v2.2.0

Release v2.2.0-pre.3

Reverted several commits to add new sensors reported to cause connection failure in issue #85.

Breaking Change

• Duplicate meters after initial setup in #83

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

Release v2.2.0-pre.2

• Add support for SolarEdge Inverters with Synergy Technology
• Add Multi MPPT (mmppt) events sensor.
• Modbus Client Object in #87

Breaking Change

• Duplicate meters after initial setup in #83

Full Changelog: v2.1.3...v2.2.0-pre.2

Release v2.2.0-pre.1

This release contains a breaking change!

This release fixes a problem observed in issue #61 with duplicate meters appearing after initial setup. Some inverters do not provide stable meter device information for unknown reasons. Unfortunately, using device information for the entity Unique ID causes new entities to be created if the inverter suddenly changes what it reports for that device. The issue has not been observed with the inverter device information, so this release changes the Unique ID for meter and battery entities to be based on the parent inverter's model and serial number.

Breaking Change
The Unique ID change will cause duplicate entity names for meters and batteries.

Recommended upgrade procedure:

1. Delete integration from Settings -> Devices & Services.
2. Update to v2.2.x release (manually or through HACS).
3. Re-Add the integration under Settings -> Devices & Services.

This procedure will preserve entity names. If updated in place, any existing entities with the updated Unique ID will have a _2 suffix.

Release v2.1.3

• Shut down hub before unloading in #84
• Qualify modbus errors in #81

Full Changelog: v2.1.2...v2.1.3

Release v2.1.3-pre.4

• Shut down hub before unloading in #84

Observed a problem while deleting the integration would not actually remove it from the list of configured integrations, and a second delete would cause a home assistant exception requiring a reboot. It could also manifest during reload or changing the "enable polling for updates" system option.

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

Release v2.1.3-pre.3

Clear modbus client object on disconnect.

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

Release v2.1.3-pre.2

Add pymodbus connection exception.

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

Release v2.1.3-pre.1

This pre-release qualifies modbus errors and disconnects on read errors.

Full Changelog: v2.1.2...v2.1.3-pre.1