Skip to content

3.2.4

Choose a tag to compare

View all tags
@thomluther thomluther released this 16 Sep 22:37
· 64 commits to main since this release
3.2.4
94b5522

Fix Release 3.2.4

A lot of you have been bothered with cloud issues last couple of days where entities became unavailable for some time (#353)
In most cases, the next refresh cycle will work again and update the entities. Sometimes you may need to reload the integration.
As it turns out, actually there are many timeouts for a specific endpoint to query unread messages of your Anker account, which is run every 10th update cycle per default (10 minutes). Testing has shown that retries on this endpoint may work, but several retries may be necessary. And very often the requests time out for this endpoint without any kind of response or error from the cloud.
Ignoring the timeouts or http gateway error responses for this endpoint seems to restore stability for the integration in many cases.

This release provides the code change as described in my comment.

General improvements on the underlying request code will be made to better handle generic timeout errors and implement a single retry for timeouts or 502 & 522 status responses, which indicate that the server may be temporarily be busy and does not respond.
While such a change cannot eliminate cloud issues, sporadic busy conditions may get masked.

Hopefully Anker will fix this cloud service issue soon, since that may have been introduced with recent cloud changes for support of latest devices🤷.

Enhancements: 📢

  • None

Breaking changes: 💥

  • None

Fixes 🔨 and other changes: 🔧

Full Changelog 3.2.3...3.2.4 and link to previous release notes 3.2.3

Notes: 📋

  • The device sensor for battery energy is just a theoretical value and calculated by the Api library from calculated (or customized) battery capacity and SOC. Changes of this entity should NOT be considered for the energy dashboard or helper sensors, since this battery energy sensor can never reflect the battery efficiency or capacity loss over time. Furthermore the SOC value may be inaccurate as well since that is difficult to determine for LiFePo batteries.
  • I do NOT recommend to use the Anker Solix integration daily energy statistic sensors directly in your energy dashboard, even if that is possible since they are classified as total_increasing sensors. The reasons for that are described in the discussion how to integrate the Solarbank into you energy dashboard. There you can also find the recommended approach for creating the required entities for easiest and most flexible energy dashboard integration.

Tip

Anker relaxed the restriction of a single active login token per account. You can now use you owner account in the App and the integration in parallel without disabling the Api switch. See Switching between different Anker Power Accounts to modify your hub configuration entry.

Contribution: 🙌

  • YOUR HELP is required if you have new Anker Solix systems or if new features are introduced by Anker and you want them being integrated into HA
  • I have no chance to test any Anker devices or explore the cloud Api requests and responses for new devices or features. Since the Api is not official, no documentation exists and the Api library can only be enhanced with your support and willingness to explore and test the Api queries:
  • Enhancements may only be possible when exclusive owner access to the system is available.
    • But since the system belongs to you and the Api usage is not officially supported, it is up to you to test and verify Api capabilities

Appreciation: ✨

If you like this integration and you want to show your appreciation for the countless hours spent to enhance and maintain it, I would be happy for a coffee.
"Buy Me A Coffee"

Assets 3
Loading