Releases: wlcrs/huawei_solar
1.5.0 beta 2
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.
Fixes 🐛
- Update of some
device_classandentity_classvalues to remove warnings in logs (by @peetersch in #758) - fix unit of reactive power (by @mpw96 in #804)
- Fix writing TOU registers (cfr. #877 )
Dependency upgrades 📦
This integration aims to use a compatible pyModbus version which allows it to be used together with the native modbus-integration of Home Assistant. As of HA 2025.1, Home Assistant was upgraded to use pyModbus v3.7.2 instead of v3.6.9, which had breaking changes. This is causing issues for users which use this integration alongside that native modbus-integration: #873.
As the pyModbus project has already released v3.8.2, which once again has breaking changes, this integration was upgraded to use that latest version. At the time of writing these release notes, a PR already exists against HA core to upgrade pyModbus there from v3.7.2 to v3.8.2, bringing everything back into sync.
Note: if you use other (custom) integrations which rely on incompatible pyModbus versions, then you can expect compatibility problems. Please contact the author of that integration and ask him to upgrade the pyModbus version used.
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.0b1
Contributors
Assets 2
1.5.0 beta 1
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.
Fixes 🐛
- Update of some
device_classandentity_classvalues to remove warnings in logs (by @peetersch in #758) - fix unit of reactive power (by @mpw96 in #804)
Dependency upgrades 📦
This integration aims to use a compatible pyModbus version which allows it to be used together with the native modbus-integration of Home Assistant. As of HA 2025.1, Home Assistant was upgraded to use pyModbus v3.7.2 instead of v3.6.9, which had breaking changes. This is causing issues for users which use this integration alongside that native modbus-integration: #873.
As the pyModbus project has already released v3.8.2, which once again has breaking changes, this integration was upgraded to use that latest version. At the time of writing these release notes, a PR already exists against HA core to upgrade pyModbus there from v3.7.2 to v3.8.2, bringing everything back into sync.
Note: if you use other (custom) integrations which rely on incompatible pyModbus versions, then you can expect compatibility problems. Please contact the author of that integration and ask him to upgrade the pyModbus version used.
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.0b1
Contributors
Assets 2
1.5.0 alpha 1
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_classandentity_classvalues 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
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.