v2.5.2

What's Changed

Increased update interval for yearly total to once per hour

The getKpiStationYear has traffic limiting. We can only call 25 times / day. In the documentation the following is found:

Traffic limiting is performed based on the number of plants managed by
northbound API users. Number of northbound API calls per user per day =
Roundup (Number of plants/100) + 24

Only one concurrent request is supported per minute.

If the access frequency exceeds the limit, the interface returns error code 407. Example:

• If a user manages 20 plants, the maximum number of API calls per day = Roundup (20/100) + 24 = 1 + 24 = 25.
• If a user manages 120 plants, the maximum number of API calls per day = Roundup (120/100) + 24 = 2 + 24 = 26.

For now I have set it to 1 update per hour to be on the safe side.

Full Changelog: v2.5.1...v2.5.2

v2.5.1

What's Changed

Inverter efficiency line graph

The Inverter efficiency will now show a line graph in the history graph instead of a bar chart.
Thx @kzajac83 for noticing this issue.

Improved docs

The readme was improved by @arohl. Thx!

Others

• Removed usage of deprecated constants.

New Contributors

• @arohl made their first contribution in #82

Full Changelog: v2.5.0...v2.5.1

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