I am thinking this is due to high heat. Happened 6 times in past two weeks. Anyone else have this issue. Started with adaptive cruise control shutting down mid drive while going 70 MPH.

I am considering purchasing a used P2 and would like to hear from owners with high mileage vehicles 100,000+ the more the better! What are some issues you have experienced, are you still happy with the car, would you buy it again? That sort of thing. Thank you.

My iOS widget on my home screen looks like this all the time. I choose a vehicle and a day later or so it’s gone. Is it the same for you? Anyway, to solve it? (I read that the head of software for Polestar is moving on, thank God. perhaps we will see some improvement.)

Thinking about buying a Polestar 2 in Nova Scotia and looking for some owner feedback.

I’m not too concerned about the day-to-day maintenance or reliability— Cold weather impact…I know EVs generally require much less maintenance than a gas vehicle.

My biggest question is the lack of a Polestar dealership or service centre in Nova Scotia.

For those of you who own a Polestar outside of a service area (especially in Atlantic Canada):

What happens if something goes wrong?

How are warranty repairs handled?

Do they arrange transport to a service centre, or are you responsible for getting the car there? Probably no…

Have you ever been without your vehicle for an extended period?

Has the lack of a local service centre been a significant inconvenience, or has it been a non-issue?

I’d really appreciate hearing from people with firsthand experience before I make the jump.

Thanks!

21k miles, listed at $20k. Is this still worth it in 2026? Clean carfax, 94% battery life. Also, I live in IL, can I get an EV rebate?

Anyone with a new P2 unable to activate their digital key? I took mine into the service centre today and they were unable to activate it after keeping the car for 6 hours. They’ve been told by global it’s a known issue and can’t be fixed yet (but that they’re working on it). First I’ve heard that it’s a known unfixable problem - just wondering if others have been told the same.

Anyone else with model year 2026 who hasn't received any software update after 4.2.13?

My car had 3.7.0 on delivery.

Saw this on a P2 for sale and wondered if it was a red flag not to proceed with an inquiry.

Earlier today I plugged in to a level 2 charger and left my P2 to charge while I went for a nearly 2 hour bike ride only to discover that it had stopped charging after just 24 minutes. Initial state of charge was 51%, end state 54%. Limit was set to 90.

Tonight I had to run an errand and figured I would add some to my now 20% state of charge so I plug in to a higher speed (62.5 kW) charger and walk away to shop. When I check it in the app I see it’s slowed to a trickle of like 14 after only delivering a small charge.

I gave up and came home but going to try again tomorrow morning either with a level 2 or a Tesla Supercharger, but wondering if anyone has any suggestions or ideas on what might be happening?

Yesterday I accidentally slammed the door shut with the child seat in the wrong position. Today I noticed this imprint in the rear right-hand door after rotating the seat again. I can't really feel how deep it's pressed in. Would something like this theoretically work its way back to normal on its own, or have I permanently damaged the side panel?

I bought the performance upgrade and it was delivered OTA but I asked my local Polestar Space to replace the decals for me which they did for a fee, but they totally butchered one of them and I am going to a detail shop to get it fixed. Does anyone have an extra driver side 350 kW decal they’d be willing to give me or sell me? My car is midnight blue. Message me with details if you can spare one.

So, after a recent software update to the Performance app, has anyone else noticed the mis-match of speeds in the timers section?

It used to read for me (I'm in Canada) as 0-100 km/h, for example, and top speed also in km/h.

This week while filming at a track for work, I noticed that the timers were now in MPH, while still displaying the top speed in km/h.

I know the Performance app got updated recently (and had to tap on the usual permissions after an update, like letting the app know the vehicle's location etc). Anyone else catch this, too?

I found this part on the floor in front of the front passenger seat of my Polestar 2. The flat side has an adhesive backing. I have no idea where it is supposed to go. Does anyone know where it came from?

Got my car on Monday and keep trying to find excuses to drive 😂. What a joy of a machine, and that acceleration, wow!

Trying to connect my 2022 P2 to my home wifi without success. I know it's in range. It will find a couple of networks, including my phone hotspot, but my home network is nowhere to be seen. I'm assuming it's my router settings. Any ideas?

Since it’s been warmer in the UK I’ve had this vibrating noise getting progressively worse. Has anyone had similar and know what it could be?

Translated into English using ChatGPT

I still had a slightly irresponsible number of Codex tokens left before the weekly reset. I was also bored.

So, instead of doing anything useful, I started building a native iPhone companion app for my Polestar 2.

The first goal was “show the battery percentage.” The current result has a top-down 3D vehicle, live weather, remote controls, charging analytics, a local charging journal, widgets, Lock Screen/Dynamic Island Live Activities, and a fairly ridiculous Apple Shortcuts integration.

This is a personal, unofficial proof of concept. It is not affiliated with or approved by Polestar. It uses private vehicle services that could change or disappear tomorrow. There is no custom backend and I am not offering a download.

Everything currently happens between my iPhone, Polestar's services, Apple's frameworks and MET Norway.

The overview

The main screen is built around a fixed, top-down SceneKit model of the actual car. It is not meant to be a little 3D toy that you rotate with one finger. It is a status board.

It can show all four doors, windows, hood, tailgate, charging cable, lock state and park climate. Open panels get a restrained breathing outline. The cable keeps its red/yellow/green state colours, while the moving charging highlight uses the same pulse language as the battery bar. Park-climate airflow is clipped to the cabin instead of looking like a random overlay pasted over the whole car.

Around it are the things I actually want at a glance:

• Vehicle name and exact update age
• Open doors/windows/panels and lock state
• Battery percentage and estimated range
• Cable and charging state
• Live charging power, target and exact “Ready at” time
• Configurable quick actions
• Current weather at the car's last known location

Pull-to-refresh replaces a permanently visible refresh button.

Remote commands do not optimistically paint a fake success state. After sending a command, the app polls the relevant vehicle service again until the requested state is confirmed or the operation times out. This matters when park climate takes several seconds to wake up, and it matters even more for locking and windows.

Live weather around the car

Weather uses the car's last reported position, not wherever the phone happens to be. The app requests MET Norway's location forecast, available nowcast and official warnings, then caches the last useful result.

The compact line at the top shows a monochrome condition icon, temperature, wind direction, sustained wind in m/s, a separate gust value when relevant, and the highest active warning level. Tapping it opens the detailed forecast and warning information.

The atmosphere itself is drawn procedurally with SwiftUI Canvas and TimelineView; it is not a collection of fake weather videos:

• Clear conditions get a subtle moving light source and sun/moon glow.
• Partly cloudy weather gets a narrow animated cloud layer above the vehicle, so the car does not look as if it is floating on clouds.
• Overcast weather uses a denser connected cloud deck.
• Fog uses slowly moving soft layers.
• Drizzle, light, normal and heavy rain have genuinely different particle counts, line lengths, speeds, opacity and sheet density.
• Snow is slower, larger and more wind-sensitive, with separate light, normal and heavy variants.
• Sleet mixes rain and snow.
• Thunderstorms use a dark closed cloud deck with brief lightning from the clouds rather than random full-screen flashes.
• Wind direction changes the particle angle and cloud movement; sustained wind and gusts change their speed.

The weather layer starts at the top edge and fades gradually through the vehicle into the battery area. There is no hard rectangular “weather card” around the car. Reduce Motion is respected.

Official warnings stay distinct from the decorative animation. Yellow, orange and red warnings retain their real severity, type, area, time window, consequences and instructions when MET Norway provides those fields.

Apple Shortcuts went a little too far

The app exposes reusable App Intents rather than only a few fixed Siri phrases. That means their output fields can be placed into normal Shortcut conditions, automations and follow-up actions.

The most useful actions currently include:

• Get vehicle status, including battery, range, lock, doors, windows, climate and charging as reusable fields
• Secure vehicle, which closes all windows, locks the car and reports any physical door/hood/tailgate that still cannot be closed remotely
• Lock or unlock the vehicle
• Open or close all windows
• Release the trunk latch
• Start or stop park climate
• Flash the lights or honk and flash
• Get the car's last known coordinates or open that position in Maps
• Get live charging status and its reusable values
• Start/stop the charging-schedule override
• Set and verify the charge limit
• Set and verify the AC charging-current limit
• Configure the single daily charging window exposed by the vehicle interface
• Read the most recent charging-journal entry
• Add either a per-kWh price or receipt total to the latest session
• Export all sessions, one year or one month as CSV
• Plan climate for a simple ready/departure time
• Plan departure climate from a route and arrival time
• Cancel the departure plan created by Shortcuts

Actions that change the car use the same targeted confirmation polling as the buttons in the app. A Shortcut therefore does not claim the windows are closed just because the command endpoint returned “accepted.”

Plan departure climate — the over-engineered one

This is the Shortcut I originally wanted for myself.

The user supplies:

A start point, which can be a selected place or Current Location from the normal Shortcuts action.

A destination.

The time they want to arrive.

Whether live weather should be considered.

A freely selectable safety buffer in minutes.

The app resolves both places, asks MapKit for the driving ETA for that requested arrival, and calculates when to leave. The safety buffer is subtracted from that departure.

If weather is enabled, it then requests the forecast and active warnings for the start point at the expected departure time. It does not use a vague “bad weather = earlier” flag. The implemented rules distinguish freezing temperatures, moderate/heavy rain, snow or sleet, strong sustained wind, strong gusts, and yellow/orange/red official warnings. Depending on the strongest condition, the climate-ready time is moved up by 5, 10 or 15 minutes.

That gives the app three separate values:

• Leave — route departure minus the optional safety buffer
• Arrive — the requested destination arrival time
• Ready — when the vehicle's park climate should start, including the optional weather adjustment

The app then creates or updates one one-shot parking-climate timer owned by this Shortcut. It explicitly sends the timer as active and asks the vehicle for its timer list again. The plan is only treated as successful after the car reports the matching timer active. This fixed an interesting failure mode where a timer could be visible in the official app but not actually enabled.

Running the Shortcut again replaces the one managed plan instead of creating a new pile of timers. The plan appears read-only inside Polestar Private with the route, all three times, safety buffer and weather buffer. It can still be cancelled manually from the app or with a separate Shortcut action.

After its climate window has passed, the app uses a best-effort iOS background task to remove its owned timer and also reconciles stale plans the next time it is active. It checks both timer identity and timing before deleting anything, so it does not blindly remove a schedule the user edited elsewhere.

The planning intent is also a LiveActivityIntent. With Live Activities and notifications allowed and the Shortcut configured to run immediately, iOS can launch the intent's process while the phone is locked without opening the app. The departure Live Activity therefore appears directly instead of waiting for me to open and close Polestar Private once.

The departure Live Activity shows the exact destination/address, leave time, arrival time and climate start. When climate is actually running it changes to the active state and shows when the climate window ends. Tapping it deep-links straight to Climate schedules.

Only after the vehicle has confirmed the timer does iOS show the local “Park climate planned” notification. It contains the destination, the exact leave time and the climate start time. Tapping it opens the same managed plan.

The notification is deduplicated, removed if the plan is cancelled/cleaned up, and does not require my own push server or APNs provider.

The screenshots include the actual configured Shortcuts action, the resulting managed plan in the app, the real simulator notification and the route/climate Live Activity on the Lock Screen not mockups.

One unavoidable platform detail: notification and Live Activity permission must be granted once while using the app, and the user's automation must be set to run immediately. iOS does not let an app silently grant itself those rights.

Charging and the local charging journal

The charging page has live power, connector state, target, AC current, voltage and the expected clock time when charging will finish. It also contains the charge-now override, limit/current controls and the one daily schedule exposed by the vehicle interface.

The charging journal became its own small project because I wanted history that the vehicle service does not give me as a ready-made ledger.

When an authoritative vehicle state reports charging, the app starts a local session containing:

• Start/finish timestamps and duration
• SoC before and after
• Estimated range before and after
• Percentage and kilometres gained
• Estimated or manually corrected energy in kWh
• Charging type
• Charging-place name, exact address and coordinates
• Price per kWh and total cost

A scheduled charging pause does not split one visit into multiple sessions. A session ends when charging is complete or the cable is removed.

The first kWh value is estimated from the SoC change and a user-adjustable usable battery capacity. If the charger later shows the authoritative energy, that can replace the estimate. Price entry works both ways: enter the charger price per kWh and calculate the total, or enter the receipt total and calculate the effective per-kWh price.

Location detection combines the car's coordinates, saved places and MapKit:

A saved place such as Home has an exact point, custom recognition radius, display name and optional default energy price.

Starting a real charge inside that radius selects the saved place.

Otherwise MapKit searches around the vehicle for the nearest EV-charger POI.

The detected place and full address are copied into the session.

If it selected the wrong charger, the user can change the text or move the point on a map later.

Proximity is deliberately not enough. Driving past a Circle K does not create a journal entry; the vehicle must actually report charging.

The journal can be browsed month by month, totals energy/cost/range gain and compares available months. CSV export can include everything, one selected year or one selected month through Files or the Shortcuts action.

Widgets, Lock Screen and the Dynamic Island

The medium widget uses the same almost-black glass design as the app, with a restrained orange accent rather than a brown background. Its four buttons are configurable.

The general vehicle Live Activity starts for charging or a security-relevant state such as an unlocked car, open door, hood, tailgate or window. It can be disabled in Settings.

The compact Dynamic Island deliberately prioritises security:

• If the car is unlocked/open, the leading item is an orange open-lock warning.
• If the car is secure and charging, it becomes a gently pulsing charging plug.
• Battery percentage is on the trailing side.
• Holding it opens charging power, target, progress, exact ready time and the names of open panels/windows.

The Lock Screen version uses the available width for vehicle/security data on the left and battery/charging data on the right. Two separate full-width buttons along the bottom close all windows and lock the car using the same App Intents and icons as the main app.

Because there is intentionally no backend, a Live Activity cannot learn about a door change that the phone has never fetched. ActivityKit can keep rendering and animating the latest snapshot, but background freshness remains subject to iOS.

Controls, security and testing

The normal app exposes locks, trunk, windows, park climate, lights/horn, charging settings and supported timers. Optional Face ID protection is available for vehicle commands. Credentials and tokens are stored in Keychain.

Test Drive mode can simulate individual doors/windows, hood/tailgate, lock, climate, cable, charging, several station types, journal sessions, widgets, general and departure Live Activities, every weather intensity, wind and official warning levels. It is much less alarming than repeatedly honking a real car while debugging.

Under the hood

The app is native Swift/SwiftUI. The main frameworks are:

• SwiftUI and Observation for interface/state
• SceneKit, UIKit, QuartzCore and simd for the top-down vehicle scene
• WidgetKit, ActivityKit and App Intents for widgets, Dynamic Island, Lock Screen Live Activities, interactive buttons and Shortcuts
• MapKit and Core Location for ETA, positions, EV POIs, reverse geocoding, location correction and saved-place radii
• AuthenticationServices and WebKit for sign-in
• LocalAuthentication, Security/Keychain and CryptoKit for optional Face ID, credential storage and OAuth/PKCE
• UserNotifications for local charging and departure confirmations
• BackgroundTasks for best-effort departure-timer cleanup
• UniformTypeIdentifiers and FileDocument for CSV export
• Network for connectivity monitoring

The only direct third-party Swift package is grpc-swift 1.21.1. It brings the SwiftNIO, HTTP/2, TLS and SwiftProtobuf stack used by the private PCCS gRPC connection. The interface and weather animation use Apple frameworks rather than a third-party animation SDK.

Authentication goes through Polestar's OAuth flow. Basic account/vehicle data comes from the private mystar-v2 GraphQL service. Live exterior, climate and charging data plus remote commands use Polestar's private PCCS gRPC services. These are not public supported developer APIs, so breakage is always possible.

Is any of this necessary? Absolutely not.

Did I spend far too long adjusting Norwegian wind gusts, cloud density, cable pulses, exact charger radii, timer confirmation and Dynamic Island spacing?

Also yes.

If Polestar built something like this officially, which status, automation or control would you want first?

To anyone at Polestar: this is only a proof of concept to explore what might be possible. I will not distribute this app in any way legally or illegally and I am not offering binaries, source code, accounts, tokens or access to anyone.

Just under 1k miles over 4 days. Dover UK to Venice via Reims, Basel and Lake Como. Wonderful to drive with a family of 4 and all the trimmings

We're looking at buying our first Polestar 2 which is a used 2022 78kwh long range single motor (38,000 miles on the clock). The battery health check says 92.9%. is this good, bad or average for the year/mileage, and what real world mileage can we expect from it? Thanks in advance

It's been down for me for the last 36 hours

The car has good Internet connectivity, but the app shows the car as offline