Skip to content

Releases: wlcrs/huawei_solar

1.5.0 alpha 1

12 Oct 11:58
9938df8
Compare
Choose a tag to compare
1.5.0 alpha 1 Pre-release
Pre-release

⚠️ Alpha release: expect that things can be broken ⚠️

Please report any unexpected behavior via an Issue. I'm particularly expecting issues regarding to changing inverter and battery configuration parameters when connected via an EMMA device. Please check if you are using the latest EMMA firmware version, and properly document how you connect to the EMMA in your issue.

Improvements 🚀

This release adds:

  • support for Huawei EMMA devices
  • auto-discovery of devices during initial setup, making it unnecessary to lookup the Modbus Slave ID's of each device.

Fixes 🐛

  • Update of some device_class and entity_class values to remove warnings in logs (by @peetersch in #758)
  • fix unit of reactive power (by @mpw96 in #804)

Looking for translators 🔡

The new EMMA-sensors need translating!

Are you willing to help translate this integration? We now use Crowdin to make it easy to contribute translations.

Use this invitation link to get started!

Full Changelog: 1.4.1...1.5.0a1

1.4.1

16 Jun 12:28
Compare
Choose a tag to compare

Improvements 🚀

  • Add Active power control sensor: allows you to see current Active power control setting.

Fixes 🐛

  • Change unit of insulation resistance to MOhm by @olebowle in #734
  • Fix broken active power control services #736

Full Changelog: 1.4.0...1.4.1

1.4.0

15 Jun 16:08
Compare
Choose a tag to compare

This release is a large overhaul to further improve the efficiency of the integration, made possible by improvements in Home Assistant.

Most notably, the integration can now dynamically compute which registers must be queried from the inverter, depending if they are enabled or disabled in HA.

This has also made it possible to add more entities to the integration. While they have all been disabled by default for performance reasons/because they provide (almost) duplicate information, they might be of interest to some users.

Furthermore, the update cycle of inverter, power meter and battery entities have now been separated into three separate parts. This allows you to raise the update interval for only one of those three parts instead of all entities. This will be particularly useful for people wanting to update power meter values at high speed.

⚠️ If you have changed the polling frequency in the past, you will need to duplicate this into three separate automations now ⚠️

This release has been tested by 200 users for an extended time as an alpha-version. Thank you for testing! 🎉

Improvements 🚀

  • Add inverter active power derating entities (#683)
  • Add forcible charge status sensor (#731)
  • Add reconfigure flow (#689)
  • Add insulation resistance sensor (#727)

Fixes 🐛

  • Fix detection logic for power meters (#671)
  • Fix device_class and state_class of battery (dis)charge entities (#684)

Thank you! 💖

A big thank you to all my sponsors! Your support helps to keep this integration in great shape.

Full Changelog: 1.3.4b1...1.4.0

1.4.0 alpha 3

16 Apr 19:23
Compare
Choose a tag to compare
1.4.0 alpha 3 Pre-release
Pre-release

⚠️ Alpha release: expect that things can be broken ⚠️

This release is a large overhaul to further improve the efficiency of the integration, made possible by improvements in Home Assistant.

Most notably, the integration can now dynamically compute which registers must be queried from the inverter, depending if they are enabled or disabled in HA.

This has also made it possible to add more entities to the integration. While they have all been disabled by default for performance reasons/because they provide (almost) duplicate information, they might be of interest to some users.

Furthermore, the update cycle of inverter, power meter and battery entities have now been separated into three separate parts. This allows you to raise the update interval for only one of those three parts instead of all entities. This will be particularly useful for people wanting to update power meter values at high speed.

⚠️ If you have changed the polling frequency in the past, you will need to duplicate this into three separate automations now ⚠️

Improvements

  • Add inverter active power derating entities (#683)

Fixes 🐛

  • Fix detection logic for power meters (#671)
  • Fix device_class and state_class of battery (dis)charge entities (#684)

Full Changelog: 1.4.0a2...1.4.0a3

1.4.0 alpha 2

04 Apr 06:08
76b3751
Compare
Choose a tag to compare
1.4.0 alpha 2 Pre-release
Pre-release

⚠️ Alpha release: expect that things can be broken ⚠️

This release is a large overhaul to further improve the efficiency of the integration, made possible by improvements in Home Assistant.

Most notably, the integration can now dynamically compute which registers must be queried from the inverter, depending if they are enabled or disabled in HA.

This has also made it possible to add more entities to the integration. While they have all been disabled by default for performance reasons/because they provide (almost) duplicate information, they might be of interest to some users.

Furthermore, the update cycle of inverter, power meter and battery entities have now been separated into three separate parts. This allows you to raise the update interval for only one of those three parts instead of all entities. This will be particularly useful for people wanting to update power meter values at high speed.

⚠️ If you have changed the polling frequency in the past, you will need to duplicate this into three separate automations now ⚠️

Fixes 🐛

  • Fix detection logic for power meters (#671)

1.4.0 alpha 1

01 Apr 09:09
Compare
Choose a tag to compare
1.4.0 alpha 1 Pre-release
Pre-release

⚠️ Alpha release: expect that things can be broken ⚠️

This release is a large overhaul to further improve the efficiency of the integration, made possible by improvements in Home Assistant.

Most notably, the integration can now dynamically compute which registers must be queried from the inverter, depending if they are enabled or disabled in HA.

This has also made it possible to add more entities to the integration. While they have all been disabled by default for performance reasons/because they provide (almost) duplicate information, they might be of interest to some users.

Furthermore, the update cycle of inverter, power meter and battery entities have now been separated into three separate parts. This allows you to raise the update interval for only one of those three parts instead of all entities. This will be particularly useful for people wanting to update power meter values at high speed.

⚠️ If you have changed the polling frequency in the past, you will need to duplicate this into three separate automations now ⚠️

1.3.4 beta 1

19 Mar 09:41
26ed8fb
Compare
Choose a tag to compare
1.3.4 beta 1 Pre-release
Pre-release

Bug fixes 🐛

  • Update to pyModbus 3.6.6 to stay compatible with other integrations using pyModbus (#657, #658)
  • Prevent login race condition (#654)

1.3.3

29 Feb 13:24
3c46cb9
Compare
Choose a tag to compare

Bug fixes 🐛

  • Fix Urdu translation (Fixes #636)

1.3.2

24 Feb 09:08
Compare
Choose a tag to compare

Bug fixes 🐛

  • Fix On/Off switch naming (#621)
  • Migrate power and energy constants due to HA deprecation warning (#577)

Full Changelog: 1.3.1...1.3.2

1.3.1

23 Dec 09:07
bbf441d
Compare
Choose a tag to compare

Improvements 🚀

Bug fixes 🐛

  • Fixed translation of maximum charging / discharging power fields (#568)
  • Bumped minimum version of HA (#565)

Full Changelog: 1.3.0...1.3.1