Consumable open API

#1

It would be nice to have a open REST-API for the Solix products. Its would be a real deal to have an API to get values of your Solix products into Home Assistant or other systems.

I guess the entire ecosystem would really benefits from having an API. Especially the Smart Home Community is heavily using solar panels and some other stuff and you can make them really happy to grant them the ability to reliable consume your data (even when its only read only). To bad an API is not standard for such products since the demand is there.

What are your thopught about that anker? I mean you already have an “closed” API for your app, so whats the reason behind the decision to not activly open it and get all developers onboard?

38 Likes
#2

Hi @Marco_Franke,

Thank you for your suggestion! :smiley:

2 Likes
#3

Hi,
I would love to see this feature too.
Best,

1 Like
#4

I upvote this idea as well! Really would love to see these values exportable via APIs for home assistant

1 Like
#5

This would be amazing! It’s exactly what I am looking for with my Solix F3800

2 Likes
#6

I upvote this idea as well. Are there any plans to have a basic read-only api which can be easily consumed? Current solutions on github are more or less a work around. I would like to include the data of the solar modules into my grafana/prometheus board.

1 Like
#7

Definitely a must .
Integrating it to domotic solution like Jeedom or HA would help us idendify usage and needs, like for example is my configuration good, am i running too many power high-consuming devices at the same time, should i use a smartmeter or buy a second battery , etc.

getting through API a few values like kWh generated, battery level and energy sent to house is badly needed …

(and from a very personal point of view, it would avoid losing time in the many-but-discutable tools and other mqtt stuff people are nicely trying to write to circumvent the lack of a decent service like an API :smiley: )

4 Likes
#8

Hi, I would like to have that, too.
A local api of the devices to get some data would be great as well.

As an company that uses e.g. mqtt for your customer systems you should be open to provide data of your customers to your customers.

I don’t find it very pleasing in the current time.

1 Like
#9

Local REST API would be fine!

2 Likes
#10

Definitevly a must nowadays to offer an API for integration of power products into smart homes that need to orchestrate various devices for various use cases and scenarios.
Having an integration interface is a buying criteria for products for many people who care to be independent or need combine Anker devices with existing products.

#11

Count me among those who want API access. We’re using F3800 for a commercial application, and would really like to build in basic device control (AC output on/off, Battery level readout) into our own app.

#12

Upvote!
I am currently researching which energy storage to buy for my small solar system and having a local API to get the data out is one of the most important selling points for me.
Currently there is no solution (that I know of) that offers this. If the Anker had an open API this would be a killer feature.

Please implement. :+1:

#13

this is a pain.
No API but the app is not doing any statistics.
how much Loss in battery , would a second battery help, which gain, etc etc
A simple case : if smart meter says 100w, battery is full, and i got 250w sun, i am losing 150 - then, if the day after is not sunny but cloudy, a second battery would have been usefull. How often does it happen, for which energy overall ?

And on top of that, a wonderful feature would be “use smart meter but ensure a minimum of N Wh” . Just to do some “lissage” for the variation in smartmeter values.

#14

and since i am complaining and this lack of API and information get on my nerves …

  • should not we change “setted” to “set”
  • display charge and discharge instead of having to clic
  • change “charged” and “discharged” on “real time” graphic by “charging” and “discharging” …

(just wondering, if this makes no sense, sorry)