Enhancements:
- Export module enhancements
- Added/updated used api endpoints
- Additional queries for vehicles, device grouping and power chargers
- Added helper method to delete a modified file to support file based testing with device removals (mainly for vehicles)
- added new vehicle.py module to consolidate all methods for vehicle support. They will be imported by the api module:
- create_vehicle
- get_brand_list
- get_brand_models
- get_model_year_attributes
- get_model_years
- get_vehicle_attributes
- get_vehicle_details
- get_vehicle_list
- get_vehicle_options
- manage_vehicle
- update_vehicle_options
- Added new vehicle data class to manage vehicle definitions and attributes
- Added new vehicle fields to account cache for electric vehicle support of user account
- Introduced usage of charge status description for Solarbank 2+ devices, that no longer support various status codes.
- If charging status code 0 was found for solarbank 2 or later, a proper status description will now be set based on actual constellation of power and SOC values.
- The same descriptions as for Solarbank 1 devices will be used as appropriate
- A new description for charge_ac was added, which will indicate any battery AC charge from external PV or grid.
- Added new fields to solarbank device details
- relate_type
- group_info
- bat_discharge_power
- wifi_mac
- time_zone
- Updated monitor tool for vehicle support and additional solarbank fields
- Python dependency tool was changed by KUHLwasStolen from pipenv to poetry to provide more flexibility
- Updated README
Fixes:
- Improved calculation of grid export average power value of Powerpanels for first intervals
- Fixed proper declaration of admin role for devices listed in bind_devices response #207
- Relaxed solarbank 2+ max output limit in home load helper method to the maximum of the model type since the actual limit setting is no longer reported correctly in schedule plan, see Add support for 1200 Watt discharge
- Fixed some 0 value issues for Solarbank AC which can be assumed from other power field constellations
- Fixed some value calculations if solarbank multisystem is in use
Important
Multisystems still have significant consumption data reporting issues to the cloud, see Add support for multi-system Solarbanks. Full multisystem support can just be provided after Anker fixed the reporting issues and after further system exports of such constellations are provided by the community. Especially the schedule management and usage mode dependencies across those systems are unknown. Will all devices be switched to same usage mode and schedule, or can they still be managed independently?
Breaking changes:
- N/A
Full Changelog: v3.1.1...v3.2.0