This Home Assistant custom component integration utilizes the anker-solix Python library, allowing seamless integration with Anker Solix devices via the Anker cloud. It was specifically developed to monitor the Anker Solarbank E1600. Support for further Anker devices like solar micro-inverters (MI80) have been added to the Api library and are available through the integration. The Anker Power cloud also supports portable power stations (PPS) or home Power Panels which may be added in future once Api data structures for those devices are known.
🚨 This custom component is an independent project and is not affiliated with Anker. It has been developed to provide Home Assistant users with tools to integrate the Solarbank E1600 into their smart home. Initially the Api library as well as the integration has been developed for monitoring of the Anker Solarbank only. Meanwhile also Anker inverters can be monitored and future enhancements meanwhile also allow modifications to their device settings. Any trademarks or product names mentioned are the property of their respective owners. 🚨
This integration utilizes an unofficial Python library to communicate with the Anker Power cloud server Api that is also used by the official Anker mobile app. The Api access or communication may change or break any time without notice and therefore also change or break the integration functionality. Furthermore, the usage for the unofficial Api library may impose risks, such as device damage by improper settings or loss of manufacturer's warranty, whether is caused by improper usage, library failures, Api changes or other reasons.
🚨 The user bears the sole risk for a possible loss of the manufacturer's warranty or any damage that may have been caused by use of this integration or the underlying Api python library. Users must accept these conditions prior integration usage. A consent automatically includes future integration or Api library updates, which can extend the integration functionality for additional device settings or monitoring capabilities. 🚨
Because of the way the Anker cloud Api works, one account with e-mail/password cannot be used for the Anker mobile app and the cloud Api in parallel. The Anker cloud allows only one user request token per account at any time for security reasons. Each new authentication request by a client will create a new token and drop a previous token on the server. Therefore, usage of this integration with your mobile app account will kick out your login in the mobile App. However, starting with Anker mobile app release 2.0, you can share your defined power system(s) with 'family members'. It is recommended to create a second Anker account with a different e-mail address and share your defined power system(s) with the second account.
Attention:
System members cannot manage any devices of the shared system or view any of their details. You can only see the system overview in the app. Likewise it is the same behaviour when using the Api: You cannot query device details with the shared account because you don't have the required permissions for this data. However, a shared account is sufficient to monitor the overview values through the integration without being restricted for using the main account in the Anker app to manage your device settings if needed.
Since the initial version of this integration did not support many setting capabilities, it was advised to use a shared account for the integration to monitor your power device values and integrate them into your home energy dashboards. The system owner account could be used in the Anker mobile app to maintain full control capabilities of your devices. Starting with version 1.1.0, the integration supports most of the relevant parameter changes for your system and your solarbanks, including modifications of the solarbank schedule. To utilize those capabillities, you must use an owner account in the integration. Likewise you could use the shared account in the Anker mobile app.
For detailed usage instructions, please refer to the INFO
Note:
To export randomized example data of your Anker power system configuration, please refer to the anker-solix Python library and the tool export_system.py. You can open an issue there and upload a zip file with the exported json files, together with a short description of your setup. Make sure to add your device to a Power System via the Anker mobile app before exporting the configuration. Standalone devices will barely provide data through the cloud Api.
This integration will set up the following platforms and provides support for following devices:
Platform | Description |
---|---|
sensor |
Show info from Anker Solix Api. |
binary_sensor |
Show info from Anker Solix Api. |
switch |
Modify device settings via Anker Solix Api, temporary disable Api communication to allow parallel account usage in App |
select |
Select setting from available options |
button |
Trigger Device details refresh on demand |
number |
Change values for certain entities |
service |
Schedule services that can be applied to solarbank output preset entity |
Device type | Description |
---|---|
system |
Anker Solix 'Power System' as defined in the Anker App |
solarbank |
Anker Solix Solarbanks configured in the system |
inverter |
Anker Solix inverters configured in the system |
Attention:
While the integration may show standalone devices that you can manage with your Anker account, the cloud Api used by the integration does NOT contain or receive power values or much other details from standalone devices which are not defined to a Power System. The realtime data that you see in the mobile App under device details are either provided through the local Bluetooth interface or through an MQTT cloud server where all your devices report their actual values (for the time they are prompted in the App). Therefore the integration cannot be enhanced for more detailed entities of stand alone devices.
Use this button:
Or following procedure:
https://github.com/thomluther/hacs-anker-solix
Anker Solix
integration.Unfortunately, HACS does not automatically install the optional entity images that must be located within the web accessible www
folder, which is located in your HA installation configuration folder. Please see Optional entity pictures for instructions to copy the image files manually.
Installation Notes:
configuration.yaml
).custom_components
directory (folder) there, you need to create it.custom_components
directory (folder) create a new folder called anker_solix
.custom_components/anker_solix/
directory (folder) in this repository.If you want to use the optional entity pictures that are shown in the example screenshots in the INFO, you need to copy the images
folder from the integration installation path to the www
folder of your Home Assistant installation configuration folder. If you operate a Home Assistant OS device, you can preferably use file management Add Ons such as Studio Code Server or File Explorer to copy this folder after the installation:
CONFIG
folder of your HA installation (where your configuration.yaml is located)custom_components/anker_solix/
folder and copy the images
subfolder containing the entity picturesCONFIG
folder and navigate to or create the www/community/anker_solix
folder structure if not existingPaste the images
folder into the created anker_solix
community subfolder
Once the images are available in www/community/anker_solix/images/
, they will be picked up when the integration is (re-)creating the entities, like on first creation or re-load of the configuration entry.
Make sure to reload your HA UI browser window without cache to get the entity pictures displayed correctly.
For detailed instructions on how to configure and use the integration, please refer to INFO.
Note: When you make changes to the integration folder content, you need to restart Home Assistant to pick up those changes for the container or virtual environment where Home Assistant is being started. This is applicable as well when the integration is updated manually or via HACS.
If you have a problem, review existing issues or open a new issue with detailed instructions describing the problem. You may need to enable Debug Output for your Integration configuration. Review your debug output before you post it. While sensitive login information is masked, your unique device information as returned from the Api is not masked (serial numbers, IDs etc). You may want to change that globally before providing a debug output.
If you have questions, observations, advises or want to share your experience, feel free to open a new discussion topic.
If you want to contribute to this please read the Contribution guidelines. As a starter, you may want to add more translations for your native language.
If you like this project, please give it a star on GitHub