v2.5.0

What's Changed

• Improved README, thx to @aretokas in #75
• Just try getStationList and if it fails fallback to stations as Huawei Fusion Solar is not willing to help. See #78
• Postman Collection, thx to @aretokas in #76

New Contributors

• @aretokas made their first contribution in #75

Full Changelog: v2.4.1...v2.5.0

v2.4.1

What's Changed

• Use thirdData/stations for systems using https://au5.fusionsolar.huawei.com as thirdData/getStationList is deprecated. This fixes #68. Thx @arohl
• Move handling unavailable entity state up. This fixes #69. I think..
• Sort keys to fix Hassfest validation

Full Changelog: v2.4.0...v2.4.1

v2.4.0

What's Changed

Ignore devices that are disabled

You can disable devices through the Home Assistant interface. The entities related to these devices will not be available anymore.

Retrieving the data from the API will also take these disabled devices into account. So their information won't be requested. If you disable all devices from the same device type it will also speed up the process of retrieving that data.

See #65

Others

• Return nothing if entity is not available by @tijsverkoyen in #64

Full Changelog: v2.3.5...v2.4.0

v2.3.5

What's Changed

• Battery energy sensors as total_increasing by @GiorgioUghini in #54
• Use info logger level instead of warning to keep logs clean by @catalinbordan in #58

New Contributors

• @GiorgioUghini made their first contribution in #54
• @catalinbordan made their first contribution in #58

Full Changelog: v2.3.4...v2.3.5

v2.3.4

What's Changed

• Cleanup incomplete by @AndersHoglund. Which should resolve the positive and negative glitches for real (I hope ;-)). Massive thanks to @AndersHoglund to have the patience and pointing out my mistakes.
• Power Sensor active power is in W instead of kW, Thanks to @GiorgioUghini

New Contributors

• @AndersHoglund made their first contribution in #52

Full Changelog: v2.3.3...v2.3.4

v2.3.3

What's Changed

• Proper implementation to fix positive glitches. Thanks @AndersHoglund to point out my stupid mistake!

Full Changelog: v2.3.2...v2.3.3

v2.3.2

What's Changed

• Fix invalid translation keys in translation files. See #45
• Ignore new value of '0.00' when retrieving data from the Kiosk. Should fix: Huawei Kiosk invalid data, positive glitch. Thx @AndersHoglund

Full Changelog: v2.3.1...v2.3.2

v2.3.1

What's Changed

• Fixed: #37, thx @mingwenz

Full Changelog: v2.3.0...v2.3.1

v2.3.0

What's Changed

Default HACS repo

This repo is now a default HACS repo 🎉
@attaxia updated the README.md to reflect this, thx!

Don't update state while in Rate limiting mode

In the previous release a system was introduced to manage the rate limiting. But when the rate limit had ben reached the entities got in an unknown / unavailable state.

The integration now only updates the state when data is received. If the rate limit is reached and there was a previous value, the previous value will be shown.

Remark: in the logs there will be still a warning when the API responds with a rate limit error.

See #35
Should fix #29

Use translations instead of readable entities

I did not know this feature when I created the integration. But recently Home Assistant has made some changes to improve the [translation of entities states](https://developers.home-assistant.io/blog/2022/12/01/entity_translations/ for more information). So this was implemented.

Some entities will not be available anymore:

• xxx-readable_battery_status
• xxx-readable_ch_discharge_model
• xxx-readable_meter_status
• xxx-readable_ inverter_state

See #22

Use more unit enumerators

Home Assistant has introduced more unit enumerators.
See #23

New Contributors

• @attaxia made their first contribution in #33

Full Changelog: v2.2.0...v2.3.0

v2.2.0

What's Changed

Specific UpdateCoordinator for retrieving real time values

We can access each endpoint only 1 per minute. The getDevRealKpi call has a devTypeId argument which is required, but this makes that we need to do a call to the same endpoint per device type.

The DeviceRealKpiDataCoordinator will do the call per device type with a delay of 1 minute in between each device type group. This means that the more different device groups you have the less realtime the data will be.

Fixed issues:

• #25
• #26

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