Dashboard for SAIC Electrical Vehicles (MG4)

.gitignore

/check.sh
/export.sh
/node_modules/
/scripts/
/package-lock.json
/dashboardTmp.png
/dashboardTmp2.png

README.md

Please visit github repository for the lastest updates.

See Nodered flow page

Goals

My main goal is to integrate my MG4 in Node-red to use car's data with my automation workflow. Moreover, SAIC's ISmart mobile app is limited that why I have developed this dashboard.

Features

Dash-MG4: flow.json

• Support of Multi-language supported (default: French)
• Dashboard with car's components status
• Localization of my car on a map (daily, weekly, monthly and custom journeys)
• Compute charge cost and duration using electricity pricing limplementation (EDF in France)
• Override Saic MQTT gateway configuration
• Charts for:
  • Tyres pressure
  • Battery voltage
  • Consumption + cost
  • Temperature
  • Battery capacity
  • Charge calendar
• Remote actions
  • set remote temperature, A/C mode, target SOC
  • enable A/C, lock, boot ...

MG4 Gateway: flow_gateway.json

• Manage MQTT SAIC Gateway instance.

Miscellaneous

These features are not includes in theses flows but they have been integrated:

• Alerting (opened windows or doors at night, tyres pressure ...)
• Closing automatically car at night
• Starting automatically A/C
• Integration with Google Home Ok Google MG4 -> Your car is in the avenue Champs-Elyseés, 7 near Mc Donalds restaurant ...

Dependencies

I use Saic MQTT gateway project to query data from MG's car.

Dashboard integrates:

• MQTT input to query data from local Moquitto
• nodered-dashboard-ui providing ui components
• node-red-contrib-web-worldmap as map provider
• node-red-contrib-ui-svg to integrate MG top view from official MG website
• EDF pricing data file to compute cost
• Persistance in SQLite database (in beta, to remove for production)

Installation guide

No warrantly, No support, No security requirements

Schema

Raspberry Pie

• Dietpi on Raspberry

Saic MQTT gateway

• Install Mosquitto
• Install from source the latest python version

# Slow process
https://raw.githubusercontent.com/tvdsluijs/sh-python-installer/main/python.sh | sudo bash -s 3.xx.x

• Install Saic MQTT gateway

# Default folder: /home/dietpi/.node-red/saic/
mkdir /home/dietpi/.node-red/
git clone --depth 1 https://github.com/SAIC-iSmart-API/saic-python-mqtt-gateway.git
mv saic-python-mqtt-gateway saic
cd saic
pip3 install -r requirements.txt

• Launch manually SAIC Gateway for testing

# Launch gateway
python mqtt_gateway.py -m tcp://localhost:1883 -u "${saic email}" -p "${saic password}" --mqtt-user "mosquitto"  --mqtt-password "${mqtt password}"

• Use MQTT Explorer to get path of data (ex: saic/xxx/vehicles/yyy)
  • xxx: account ID
  • yyy: vehicule ID

NodeRed

• Install Nodejs

dietpi-software install 9
# or
dietpi-software reinstall 9

• Install NodeRed
• Enable Saving context data to the file-system
• Create a folder /data/ for mg.db sqlite database or change MGDB node to define database path
• Import flow.json: Dash-MG4
• Import flow_gateway.json: MG4 Gateway to manage SAIC Gateway instance in NodeRed
• Configuration:
  • open SAICMQTTFx/credentialsSAIC node:

server: https://tap-eu.soimt.com (for europe)
gateway: https://gateway-eu.soimt.com (for europe)
email: (email address of your MG ISmart account)
password: (password of your MG ISmart account)
ABRP_TOKEN: (bxxxx-xxx-xxx-xx-xxxx see ABRP integration)
ABRP_API_KEY: (xxx-xx-xx-xxx-xxxxx see ABRP integration)
GATEWAY_FOLDER: (absolute path of your gateway installation folder if you want to use **flow_gateway.json**)
VIN: (vin of your vehicle)

• open SAICMQTTFx/credentialMQTTFx node:

MQTT_URL: (xxxxxx:1883)
MQTT_USER: (mqtt user)
MQTT_PASSWORD: (mqtt password)
MQTT_CLIENTID: (mqtt client id)

• Deploy them
• Watch Saic MQTT gateway outputs & see debug trace in Nodered
  • you have to see before MQTT gateway events
  • after that MQTT input in NodeRed will integrates data
• Open http://${ip}:1880/ui/

Contribution

This flow is provided as it.

Feel free:

• to improve it
• to fix some bugs
• to share your work ;)

Disseminating knowledge is the human duty, sharing it about so that all can benefit.

Translation

• Edit saicInternationalFx subflow
• Duplicate actionFR and rename actionXX
• Translate everything in XX
• Implement electricity functions
• Edit label node and add XX in global.get("saic").language_supported (ex: XX=ES for spanish)

In Action

• Test, test and test

• Share with me actionXX && global.get("saic").language_supported contents

• I will release a new version of this dashboard and you are the official maintainer of this language

• Well done !

License

GNU GPLv3

Thanks

dashboard.png

MQTTExplorer.png

flow.json

flow_gateway.json

main.png

package.json

saic.puml

translation.gif

I have integrated MG4 in Nodered to be a part of my home automation.
Currenty using nodered, I get mg4 informations from Google Home and I have many features not shared:

• alerting (ntfy, SMS)
• monitoring
• time to go
• integration with google calendar
• automatic defrost
• ...

To my mind, Nodered integration it's a easy, short term, quick solution for home automation but it's a mess to share and to maintain.

MQTT publish it's not very stable because of SAIC services and vehicle hibernation.
The magic thing is saic gateway and mqtt broker.

I don't know if it's possible to export a flow to standalone nodejs project.

After a decade of developing embedded systems I've started developing for the node-red ecosystem and prefer, overall, building extensions to complicated flows. I think there are ways to export a flow (one way is just a subflow) but it's more likely to be beneficial to extract the comms layer to a custom node. Consider emulating, for example, Zigbee2Mqtt-like functionality. Then the dashboard can be maintained solus.

MQTT publish it's not very stable because of SAIC services and vehicle hibernation.

it's an interesting use case as there are some actions you would want not to be re-tried after a failure (e.g. unlock). but many that you might want re-tried for a defined timeout. There should be a way to achieve this within the logic but I haven't yet investigated deeply enough.