stevedee
Standard Member
There is a 'reverse engineered' project on Github to access data using the MG API called: saic-python-client-ng
Much of the work and coding examples relate to other MG models, which was a surprise to me when they didn't really work with the S5.
So I had to iterate through a collection called 'cars' to reveal the data names used in the S5 API.
A few simple things I've found so far (which may or may not be new to you) include:-
- although the Model is returned as: MGS5 EV, the Series is: MZS3E S
- the colour of our car is called: Piccadilly Blue, but the API returns the name: Soul Blue ...a name I much prefer.
Does this mean its Soul Blue in Asia and has been renamed by those funny marketing people in Europe?
- the API returns 2 version of range: BMS (based upon chemistry & SoC), and IMCU (based upon driving history & climate).
- I can see the system 12V battery voltage and confirm that it is charging when the traction battery is charging.
- I can see other stuff like the coordinates for current position, tyre pressures, plug state, and cabin temperature.
It will be interesting to see if this comms method is any more reliable than using iSmart.
I would also like to create some client-side Javascript code for checking SoC, but need to be absolutely sure it will run securely.
Much of the work and coding examples relate to other MG models, which was a surprise to me when they didn't really work with the S5.
So I had to iterate through a collection called 'cars' to reveal the data names used in the S5 API.
A few simple things I've found so far (which may or may not be new to you) include:-
- although the Model is returned as: MGS5 EV, the Series is: MZS3E S
- the colour of our car is called: Piccadilly Blue, but the API returns the name: Soul Blue ...a name I much prefer.
Does this mean its Soul Blue in Asia and has been renamed by those funny marketing people in Europe?
- the API returns 2 version of range: BMS (based upon chemistry & SoC), and IMCU (based upon driving history & climate).
- I can see the system 12V battery voltage and confirm that it is charging when the traction battery is charging.
- I can see other stuff like the coordinates for current position, tyre pressures, plug state, and cabin temperature.
It will be interesting to see if this comms method is any more reliable than using iSmart.
I would also like to create some client-side Javascript code for checking SoC, but need to be absolutely sure it will run securely.