Guide to retrieving data from Xpeng cars and publish in Home Assistant

Overview

This is a guide and a bit of code for retrieving Xpeng data from enode.com to be able to present these in Home Assistant. This solution will retrieve all data from the enode server but please note that Xpeng currently doesn't upload all possible fields. For example, odometer data are currently not available. But maybe some day. Also note that the cars' position is only updated when the car is switched off and not while driving or in neutral. Everything will update automatically every 5 minutes.

Show car location on map

In order to show the current position of the car on a map you have to create a formatted device tracker in your configuration.yaml. After reloading yaml the new device_tracker can be used to show the car's position. Add the following code (all variables names are the ones from the NodeRed code):

template:
- sensor:
    - name: "Xpeng Location Formatted"
      unique_id: xpeng_location_formatted
      state: >
        {{ states('device_tracker.xpeng_xpeng_location') }}
      attributes:
        latitude: >
          {{ state_attr('device_tracker.xpeng_xpeng_location', 'latitude') or states('device_tracker.xpeng_xpeng_location').split(',')[0] | float }}
        longitude: >
          {{ state_attr('device_tracker.xpeng_xpeng_location', 'longitude') or states('device_tracker.xpeng_xpeng_location').split(',')[1] | float }}
        source_type: gps
        friendly_name: "Xpeng"
        icon: "mdi:car-electric"

Prerequisites

Xpeng

Have your user name and password for your Xpeng account ready.

Enode

All communication with enode.com uses Curl commands which can be issued from the command prompt within Windows - this is also quite effective for initial testing. Alternatively these Curl commands can also be run from Home Asistant from Terminal.

You will need to create a Developer account on ENODE.COM on https://developers.enode.com/api/reference#introduction. The free user account will only let you access the sandbox area. Contact Sales on https://enode.com/contact and ask them if your account can be upgraded to a production account. With a bit of luck you will get access to a number of free devices.
With your Client ID you can create a Client secret according to this guide: https://developers.enode.com/api/reference#api-credentials. Keep your ClientID and Client Secret in a safe place - we will need this later on.
Next step is to retrieve an access token. To do this you have to send the following curl command to the enode server at https://oauth.production.enode.io/oauth2/token and replace ClientID:ClientSecret with your data.

curl https://oauth.production.enode.io/oauth2/token -X POST -u ClientID:ClientSecret -d "grant_type=client_credentials"

The server will reply with a token that will expire after an hour.
Within an hour (or you will have to update your token first) you can add your car to this Client; this is a bit tricky and also involves running Curl commands Open a command prompt from within Windows and run the following command and replace {YOUR_ClientID} with the ClientID you received when creating your enode account and {YOUR_ACCESS_TOKEN} with your current access token.

curl https://enode-api.production.enode.io/users/{YOUR_ClientID}/link -X POST ^ -H "Authorization: Bearer {YOUR_ACCESS_TOKEN}" ^ -H "Content-Type: application/json" ^ -d "{ "vendorType": "vehicle", "scopes": ["vehicle:read:data", "vehicle:read:location", "vehicle:control:charging"], "language": "en-US", "redirectUri": "https://localhost:3000\" }"

The above is one command! The ^ at the end of each line simply instructs the command prompt to continue input. Enode.com will reply with a link to a landing page that you can click on. The landing page will prompt you to authorize your car being added to this client. You will need your Xpeng user name and password for this!

Home Assistant

My solution relies on a Home Assistant installation with both MQTT and Node Red, so ensure that you have both installed and configured. Remember to update the NodeRed code to point to your local MQTT broker information. My code assumes Localhost which points to my broker's IP, username and password.

Next steps

After having done all the initial setup steps and verified that you are able to receive data from Enode.com, you can download my Node Red flow and import it in Node Red. Remember to replace the YOUR_CLIENT_ID:YOUR_CLIENT_SECRET in the "Update token" Exec Node with your data. If auto-discovery is enabled, the new Xpeng device should automatically pop up in your list of MQTT devices. All the entities should also be visible in the new MQTT device. From there on use the sensors where you need them.

Changelog

V2: Removed QoS and Retain settings in MQTT publish

OldSmurf56/xpeng