Releases: wlcrs/huawei_solar
1.5.4
Fixes 🐛
- Force pyModbus version to "<3.8.5", as it contains a regression that breaks all communication with devices with slave-id 0 (cfr. #940)
Thank you! 💖
A big thank you to all my sponsors! Your support helps to keep this integration in great shape.
1.5.3
Improvements 🚀
This release adds:
- support for Huawei EMMA devices (unstable)
- auto-discovery of devices during initial setup, making it unnecessary to lookup the Modbus Slave ID's of each device.
- Sensors for temperatures of individual battery packs (by @TomHarm in #830)
- MPPT scan interval is now configurable (by @TomHarm in #830)
Fixes 🐛
- Fix serial connection (was broken in v1.5.0 and v1.5.1, cfr: #901)
- Update of some
device_classandentity_classvalues to remove warnings in logs (by @peetersch in #817) - fix unit of reactive power (by @mpw96 in #804)
- Fix writing TOU registers (cfr. #877 )
- Fix support for Huawei-inverters that were rebadged by EDF (cfr. #902) and other brands (was broken in v1.5.2, cfr. #906)
Dependency upgrades 📦
This integration relies on the Python library 'pyModbus' to communicate with your Huawei Solar installation via the Modbus protocol. Other integrations, like the native modbus-integration of Home Assistant do the same. Recently, the pyModbus project released a series of releases containing breaking changes. When this integration is used in conjunction with other integrations which rely on an incompatible version, this breaks your installation as only one version of pyModbus can be installed at any one time. This led to issues in HA2025.1 (cfr. issue #873).
This release upgrades the pyModbus version used to v3.8.3, which is in line with the version used by the native modbus-integration of HA 2025.2, restoring compatibility.
Note
If you use other (custom) integrations which rely on incompatible pyModbus versions, then these compatibility problems will persist until the other integration also upgrades their pyModbus dependency. Please contact the author of that integration if that is the case.
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.3
Contributors
Assets 2
1.4.1
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
Contributors
Assets 2
1.4.0
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.
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
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.
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
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.
Fixes 🐛
- Fix detection logic for power meters (#671)
1.4.0 alpha 1
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.