Skip to content

3.2.1

Choose a tag to compare

View all tags
@thomluther thomluther released this 24 Aug 11:20
· 78 commits to main since this release
3.2.1
c36d6a0

Fix Release 3.2.1

Enhancements: 📢

  • Dynamically update output preset number entity limits if they are changing #332
    • Output preset limits may change depending on solarbank model and actual device settings, such as maximum inverter output power, or the defined inverter model for Solarbank 1 devices
    • If a Solarbank device setting was changed in the mobile App and caused a modification of the min or max limit given in the schedule plans, the number entity limits have never been updated during the active Api session
    • This enhancement will now always update the entity limits with the min and max load values as reported in the active schedule plan.
    • This will prevent that number modifications via HA frontend or number entity actions can set values beyond the limits being applied by the device
    • It will ensure that the presented entity state value is really being applied. Otherwise it would cause confusion if values would be accepted by the device schedule plan, but capped by the solarbank device without feedback/confirmation to HA users via the entity.
    • The preset value limits for Anker Solix schedule actions remains unchanged

Note

Since the action number field limits are fix, they must define the outer possible limits for all device types supported by the action. A value capping may still occur if the action setting is beyond the device model specific limits once the action is being applied, but this capping will be reflected in the resulting number entity state. However, if that value is still beyond the actual device limits which may be smaller, capping will still be applied by the device itself, which is NOT reflected back to the number entity. The entity shows only the active setting given in the schedule plan as you can also find it in the Anker mobile app.

Important

This change will NOT fix issue #309 to allow output preset > 800 W. That is an Anker cloud or device problem which seems to be specific for SB3, because the active device limits in the schedule plan are not longer reflecting the applied limits, but 800 W although device setting is 1000 or 1200 W. However, the reported device limits in the schedule plan must be taken as active entity limits, to avoid confusion with number entity settings as described above.

Breaking changes: 💥

  • SB1 users may notice an increase in the minimum limit of the output preset entity to 150 W, since that is now adopted to the actual limit applied by the device and depends on the defined inverter type.

Fixes 🔨 and other changes: 🔧

  • Integration broke after update to 3.2.0 #337
    • Old HA releases do not know the new device class energy distance
    • Updated minimum HA release to 2025.3.0 which introduced the energy distance device class and units
    • The new min version will prevent integration can be updated on older HA releases which do not have all requirements
  • Fixed exception when pressing device refresh button #333
    • Problem was introduced with new vehicle details refresh button
  • Solarbank not longer delivering negative battery power values since update to 3.2.0 #338
    • Problem was introduced by utilization of new battery discharge fields and is fixed again 😇

Full Changelog 3.2.0...3.2.1 and link to previous release notes 3.2.0

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.

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.

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