This is great, but somewhat complicated. HA in the car already exposes some of these sensors across the HA implementations (like location), could HA in the car be updated to expose all the same sensors that car stats viewer exposes?
As I understod it, it already does, but since you cannot get into the app settings in the car anymore ( after complain from google ) you cannot enable them. I thought this was only a temporary change but I seams permanent.
I would like to contribute on top of already excellent post by @scriven33
Changes:
- introduce binary_sensor for charge port
- extra attributes
- unique_id (so you can personalize in the UI)
template:
- trigger:
- platform: webhook
webhook_id: VERY_SECRET_ENDPOINT_THAT_IS_OPEN_TO_THE_INTERNET
local_only: false
unique_id: polestar_webhook
binary_sensor:
- name: "Polestar 2 Charge Port Connected"
state: "{{ trigger.json.chargePortConnected }}"
icon: mdi:ev-plug-type2
unique_id: p2_charge_port_connected
sensor:
- name: "Polestar 2 Altitude"
state: "{{ float(trigger.json.alt) if trigger.json.alt is defined }}"
availability: "{{ trigger.json.alt is defined }}"
unit_of_measurement: 'm'
icon: mdi:altimeter
unique_id: p2_altitude
- name: "Polestar 2 Latitude"
state: "{{ float(trigger.json.lat) if trigger.json.lat is defined }}"
availability: "{{ trigger.json.lat is defined }}"
icon: mdi:latitude
unique_id: p2_latitude
- name: "Polestar 2 Longitude"
state: "{{ float(trigger.json.lon) if trigger.json.lon is defined }}"
availability: "{{ trigger.json.lon is defined }}"
icon: mdi:longitude
unique_id: p2_longitude
- name: "Polestar 2 Temp"
state: "{{ trigger.json.ambientTemperature }}"
icon: mdi:thermometer
unit_of_measurement: '°C'
unique_id: p2_ambient_temperature
- name: "Polestar 2 Battery Level"
state: "{{ trigger.json.batteryLevel | float(0) / 1000 }}"
icon: mdi:battery
unit_of_measurement: 'kWh'
device_class: energy
unique_id: p2_battery_level
- name: "Polestar 2 Ignition State"
state: "{{ trigger.json.ignitionState }}"
icon: mdi:car-key
unique_id: p2_ignition_state
- name: 'Polestar 2 Current Power'
state: "{{ trigger.json.power | multiply(1/1000000) }}"
unit_of_measurement: 'kW'
icon : mdi:speedometer
device_class: power
unique_id: p2_current_power
- name: "Polestar 2 Gear"
state: "{{ trigger.json.selectedGear }}"
icon: mdi:car
unique_id: p2_gear
- name: 'Polestar 2 Speed km/s'
state : "{{trigger.json.speed | float(0) * 3.6 }}"
unit_of_measurement: 'km/h'
icon: mdi:car-speed-limiter
unique_id: p2_speed
- name: 'Polestar 2 SOC'
unit_of_measurement: '%'
state: "{{ trigger.json.stateOfCharge | float(0) * 100 }}"
icon : mdi:car-electric
device_class: battery
unique_id: p2_soc
- name: "Polestar 2 Timestamp"
state: "{{ trigger.json.timestamp | multiply(1/1000) | timestamp_local }}"
icon: mdi:clock-time-eight-outline
device_class: timestamp
unique_id: p2_timestamp
Automation to update location:
alias: "Polestar: CSV Location"
description: ""
trigger:
- platform: state
entity_id:
- sensor.polestar_2_latitude
condition:
- condition: not
conditions:
- condition: or
conditions:
- condition: state
entity_id: sensor.polestar_2_latitude
state: unavailable
- condition: state
entity_id: sensor.polestar_2_longitude
state: unavailable
alias: Any will do
alias: Neither Latitude or Longitude can be Unavailable
action:
- service: device_tracker.see
data:
gps:
- "{{ states('sensor.polestar_2_latitude') }}"
- "{{ states('sensor.polestar_2_longitude') }}"
dev_id: polestar
mode: single
1 Like
I would like to contribute on top of already excellent post by @scriven33
Those are some great modifications. Thanks for updating my work - mine was very much early stages and needed cleaning up, as I knew it could be done better.
I prefer the sensor for the Charge Port Connected, as it states True, which I think is more true to life.
Your modifications also allowed me to remove some of the additional templates I created as well.
Are you on the International Polestar Forum? If so, you might want to post your mods on there as well.
Not an active user there.
Feel free to link from there to here 
(thus avoiding duplication)
I just want to leave this here:
It seems some heros have developed exactly what we are all looking for, but for the Volvo environment. I think it would just be a matter of branching this to Polestar and we’re all set (with a rock solid integration not relying on 3rd party integrations and intermediary apps).
Perhaps someone here could port it? Alternatively help me petition the creator to help branch their creation to the Polestar environment!
Cheers
//S
AFAIK we do not share the same backend
Do you have access to your car information through a webpage ? Like volvo’s do ?
Clearly there is an API since companies like Tibber can develop functionalities towards it (Polestar Smartladdning – Ladda din Polestar smart ⚡️ Tibber), but it’s likely not public.
The only access I have, as you well know, is through the Polestar App.
edit: my thought was the Polestar API likely shares a similar internal structure to the VCC API.
A new version of Car Stats Viewer has been released, although it isn’t on all of the tracks. New functionality in the API, but the old one works as before.
Hi @scriven33
I am using your templates and stuff in Home Assistant. They mostly work great but I don’t seem to get any Lat Long or Altitude data. I’ve checked ABRP is working and the blue connection icon shows in CSV. Any ideas?
Have you enabled the option in CSV in the car to send that information? I am sure it is a toggle (not with the car right now).
Seeing this makes me sad that Polestar doesn’t offer the same things for us. The platforms are the same but the backends are different, so this wont work for us. Look at all the things they get directly with the Volvo API:
VEHICLES_URL = “https://api.volvocars.com/connected-vehicle/v1/vehicles”
VEHICLE_DETAILS_URL = “https://api.volvocars.com/connected-vehicle/v1/vehicles/{0}”
WINDOWS_STATE_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/windows”
CLIMATE_START_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/commands/climatization-start”
CLIMATE_STOP_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/commands/climatization-stop”
LOCK_STATE_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/doors”
CAR_LOCK_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/commands/lock”
CAR_UNLOCK_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/commands/unlock”
RECHARGE_STATE_URL = “https://api.volvocars.com/energy/v1/vehicles/{0}/recharge-status”
ODOMETER_STATE_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/odometer”
LOCATION_STATE_URL = “https://api.volvocars.com/location/v1/vehicles/{0}/location”
TYRE_STATE_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/tyres”
ENGINE_STATE_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/engine-status”
BATTERY_CHARGE_STATE_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/battery-charge-level”
FUEL_STATE_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/fuel”
STATISTICS_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/statistics”
ENGINE_DIAGNOSTICS_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/engine”
VEHICLE_DIAGNOSTICS_URL = “https://api.volvocars.com/connected-vehicle/v2/vehicles/{0}/diagnostics”
I’m jealous.
I’m going to try to host my own test version of CSV and then push to HA, guess that’s our best bet today.
This works pretty well. I have added a Charger Status indicator to my EV page, and I’m calculating the estimated SOC based on how many kWh were added to the starting battery level and divided by the battery capacity.
At home, when plugging in the charger before locking the car, the data gets sent to HA properly. When done charging, unlocking the car will get the information sent to HA.
The left battery bar is the estimated SOC, the right bar is the actual data coming from the car. I took the screenshot after going out to the post office, but they did match when the car first reported its level back.
2 Likes
I tried this setup via tibber (free account without energy contract), works pretty good!
Similar solution via bash script has already been mentioned above:
1 Like
How does Tibber obtain the information? Does it have a connection to the Polestar API?
Yes, tibber has access to a non public API for the Polestar account 
You have to pair the polestar account in the tibber app.
Hmm. I’ll have to give this a go. Thanks
Hi,
I will get a polestar 2 this week, I don’t have any home assistant configured, but I’ve got my own rpis working with some stuff… This integration for the moment only shows data of the polestar right? I can also publish this into some grafana/prometheus stack, right?
Other point, this week, I don’t know how, in duckduckgo, I found this link:
https://api.polestar.com/
I don’t know if you know it, but… feels like we only need to know the endpoints…
Thanks for everything,
D.
The API location is well known. If it was that easy it would have been found by now. A lot of people, particularly in Europe want car information.
The only way to connect are outlined in this thread and on the German and English fan forums. What you do with the data is up to you.
Realistically, the only open way is via the Tibber method, as while CSV is very good, it is restricted on numbers because of the workarounds to get it I. The car.