Skip to content

1.3.1

Latest
Latest
Compare
Choose a tag to compare
@thomluther thomluther released this 18 Jun 21:55
· 11 commits to main since this release
1.3.1
68515d1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

New release 1.3.0/1.3.1

Enhancements in 1.3.0:

  • Support for individual solarbank output power preset in dual solarbank systems:
    • New number entity to modify the device load preset
    • New sensor to indicate the active output power preset mode
    • Limits for appliance and device presets are now automatically adjusted based on number of installed solarbanks #48
    • Enhanced schedule services and added an optional device load preset, which also allows to specify the device load and appliance load in combination for the given interval. The difference will then be applied to the other solarbank automatically. This allows a single service call against one of the two solarbanks to adjust both individually
    • Note: Individual device load preset requires solarbank firmware 1.5.6 or later
    • The new entities will not be created for single solarbank systems or when the existing schedule structure does not support this feature yet.
    • After you updated both of your solarbanks to a supported firmware level but don't see the new entities yet, you need to reload the configuration of your Anker Solix integration to trigger a recreation of all entities.
  • New entity to report on available OTA updates for solarbank devices
    • This binary sensor will flag when there is a firmware update available for your solarbank
    • Unfortunately the cloud api does not provide information about the available firmware version
    • The sensor can be used for notifications when an update is available, which has to be performed through the mobile app
  • Updated the README and INFO with the 1.3.0 enhancements

Enhancements in 1.3.1:

  • Reduced Api calls for Solarbank Energy stats in Dual Solarbank systems #63
    • Energy stats are reported on System level only, but Api query must be done against a device of a system
    • Logic was changed to copy the energy data from devices that were already updated in previous Api query for same system
  • Bump ruff from 0.4.5 to 0.4.8 #67
  • Bump ruff from 0.4.5 to 0.4.9 #70
  • Bump actions/checkout from 4.1.6 to 4.1.7 #69

Fixes:

  • Missing preset entities when no schedule is defined bug dependencies #52
  • HA 2024.6 Warning: Detected blocking call to open inside the event loop #71

Attention:

It was observed that sending a single solarbank schedule time interval via the cloud Api may result in a weird schedule on the solarbank. While the cloud and the integration shows correct output preset values, the appliance has a 0W preset. This cannot be corrected via the cloud Api. Any interval update or addition will result in the 0 W preset for all intervals. This will cause that the solarbank does NOT discharge anymore although the settings show correctly in the cloud and the HA integration. This firmware issue may depend on your firmware and your inverter configuration vs. real inverter setup. I noticed this problem while having configured MI80 inverter (to allow min. of 100 W preset), but not having a MI80 really installed. You can correct this problem only via the Anker mobile app which seems to use a different process to modify and query the solarbank schedule than via cloud Api.

Assets 3
Loading