Release 3.3.2

🔧 Fix missing schedule control elements of combined SB1/SB2 systems 🔨

Enhancements: 📢

• None

Breaking changes: 💥

• None

Fixes 🔨 and other changes: 🔧

• Fix missing schedule control elements of combined SB1/SB2 systems #359, #360
  • Bug was introduced with 3.3.0 and schedule related Api query reductions for multisystem support
  • Different SB1 / SB2 schedules will both be queried again for combined/cascaded Solarbank systems to make control entities available in integration
  • Did further simplifications for schedule update methods across various system constellations
• Adjusted device and appliance preset limits for dual SB1 systems to use limits provided in schedule
  • Your system output preset number entities can now have a reduced limit for systems with dual SB1
  • The output preset limits in the schedule related Actions are not affected by this change. It remains at 3600 W, which is the maximum limit for a multisystem
  • The SB1 system preset limit that can be applied to the schedule is still 800 W * SB1 count in system
  • If a preset beyond any device limits is applied via schedule Actions, they will be presented in the Integration number entities, but they will be CAPPED by the device itself.
• Changed device output preset number from slider to box type to be consistent with recent system output number entity change
  • This entity is only available in systems with 2 SB1 devices, which allow individual output control

Full Changelog 3.3.0...3.3.2 and link to previous release notes 3.3.1

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:
  • via the Api library
  • via the Anker Solix action Api Request in HA developer tools actions
• 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
• MQTT device data requires decoding of binary data for your owned device type and constellation before they can be consumed
  • To get started, follow the MQTT data decoding guidelines in the Api library

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.