Enhancements:
-
MQTT Enhancements for couple of devices
- Added AS200 Alternator Charger data fields and controls
- Added A1729 C200X DC PPS data fields and controls
- Added A1727 C200 DC PPS data fields and controls
- Added A1725 C200(X) PPS data fields and controls
- Updated A1726/A1728 with temp unit control
- Updated A1782 F3000 Solarbank PPS data fields and controls
- Added A17E1 E10 Home Backup device with basic data fields
- Added AX170 Power Dock for E10 Home Backup devices with basic data fields
- Revised control of A1761 C1000 from Max Load setting to max AC charge
- There is no known PPS that has a load power control (outgoing limit control)
- This was required to harmonize PPS value names and controls
- Limit have been reduced from 2000 W to 1000 W max AC charge according to User Guide specs
- Prepared descriptions for Power Cooler Everfrost 2 40L A17A4
- Revised some field names for harmonization
-
Revised description capabilities for controls that follow 1 or more other control parameters
- The VALUE_FOLLOWS descriptions are now evaluated last, to utilize other control values that are already validated
- The VALUE_CONVERTER can now be used to describe dependencies of 1 or more control parameters, or optionally other states
-
Revised MQTT decoder capabilities to support embedded MQTT messages
- Various flavors/formats of embedded messages have been seen for AX170 power dock and Power Panel system types
- The embedded messages from other devices are now decoded in the mqtt_monitor, if they are described as embedded messages
- No data fields will be extracted yet from the embedded messages, since they belong to another device, and this other device may provide 'read only' MQTT capabilities, since it is not directly subscribed to the Anker MQTT server.
- It is unclear whether MQTT commands can be published to a device that does not publish any messages to the MQTT server, eventually those devices have no MQTT server connection, but just local communication to the 'hub/controller' device in the system.
-
Added support for Product codes
- Product codes are 3-4 chars in the device SN and those are now extracted
- If various features are documented for a device model, those are created in the device cache as well, based on the actual product code
- The device features can be used to disable certain (MQTT) control capabilities if not supported by the particular HW
- The EV Charger MQTT controls have been revised to remove HW feature dependent controls from the MQTT device instance
-
Updated export module
- Leave product code part of device SNs unchanged during randomization, otherwise the correct HW features cannot be filtered from randomized system exports.
- Added 2 generator (extender) related Api queries to export module
- Ensure to delete existing Api client caches before creating and exporting the randomized caches, otherwise PowerPanel or HES artifacts could still be included in the caches
-
Updated monitor tool
- added all description changes
- added MQTT message step forward capability and toggle back to replay mode
-
Added additional power_service/v2/* endpoints to api types
- They may be used for the 4th generation of balcony power systems
-
Added new Api device fields for new Solarbank SOC limits introduced with App version 3.19
- The usage and control of those new fields is still unknown
- The actual Solarbank systems do not provide yet capabilities to modify those new settings
- They may require Solarbank firmware updates as well
-
Updated set_sb2_home_load method to support a new 'charging_type' parameter and field in custom_rate_plans of the Solarbank 2+ schedules
- At this time, it is unknown what the purpose of this new field is and therefore it is not supported yet
- Revised Solarbank2Timeslot class to support new slot field 'charging_type'
- Changed method to curate existing but uninitialized charging_type fields in time slots to 0
-
Updated README for supported devices
Fixes and other changes:
- Changed MQTT client connection timeout from default 5 seconds to 15 seconds
- Changed Solarbank 2 inverter output limit Api control to issue device attribute change even if that may not have any effect
- This may help to get proper Api value refreshed quicker in the get_power_limit query after the real device change was done through MQTT
- Fixed MQTT command value options map creation to support value ranges with float steps
- Fixed MQTT command value validator to support partial step at end of range and limit values to defined max/min value
- Fixed unit for average power exported values
- Various other fixes in the code base
Breaking changes:
- Continuous renaming of MQTT data fields may be required as values are understood, validated and merged across the various devices
Full Changelog: v3.6.0...v3.6.2