From my understanding MG haven't published their API for anyone to use, there is a reverse engineered API implementation for MQTT via home assistant but that's all I know of.
The question was about the charger, not the car.
I'd read that it does support the MG API, like it supports the VW API, Ford API, Etc to directly communicate with the car to find out the SOC.
Think he means if it supports the API used by the energy companies, for things like Octopus Energy Go.
If you are wanting a home charger that can be controlled by Octopus then either the Ohme or the Zappi.
I can't imagine the logic of that, apart from "It's our API, we're not giving away our trade secrets!". Sigh. The whole point of an API is iter-operability; the "I" in "API" stands for Interface.
Doesn't have to be public though.
Sure. But in this case, it means that customers are missing out on handy functionality, and what advantage is keeping that API private to SAIC? None that I can see, but what do I know.
the SAIC API exposes, a lot of information and abilities of the car such as remote locking, starting, opening and closing windows, GPS location, so I imagine part of it is security amongst other reasons.
The Ohme, Zappi and Wallbox are on the Octopus IOG list.
