polestar_api icon indicating copy to clipboard operation
polestar_api copied to clipboard

Published 20 hours ago • verified publisher icon pypolestar

Integration pulling 2 months old data

Open kp-bit opened this issue 1 year ago • 14 comments

Suddenly today, the integration has started pulling data from 2 months ago. Token expiration looks ok and I've tried both reloading the integration and restarting HA. Anyone else experiencing this?

polestar

kp-bit avatar May 13 '24 18:05 kp-bit

Have similar issue Suddenly odometer shows negative growth in distance traveled Screenshot_2024-05-13-20-27-45-06_c3a231c25ed346e59462e84656a70e50 Screenshot_2024-05-13-20-28-26-49_4340b2429be81a0b24f71d6e160ae8de

motionist avatar May 13 '24 18:05 motionist

Same issue with 2 month old data. Also is showing my car is charging while it's sitting in my office parking lot not doing that. image

JoeRimo avatar May 13 '24 18:05 JoeRimo

Same problem here. Dropped 4000km just over 3 hours ago from the odometer and the manual trip meter (which I haven't reset for many months)

3shirts avatar May 13 '24 20:05 3shirts

Same problem, data pulled is now 2 months old.

mny-fin avatar May 13 '24 21:05 mny-fin

I also experienced this today, but values are now normal again. I think this is something on Polestar's side.

My guess is that it might have something to do with the P3.0.3 update that was reverted and they are doing some data recovery/migration/rollback to prepare for a new release.

wouterhardeman avatar May 13 '24 22:05 wouterhardeman

Not really buying the rollback theory, mine was back to correct battery update time and thus SOC yesterday but this morning, everything is 2 months old again.

kp-bit avatar May 14 '24 06:05 kp-bit

check on this page to see if the odometer is the same? https://www.polestar.com/uk/login/cars

i get the value from that website, the value that you post are from the polestar app, this use a another api call.

could be that polestar has rollback/restore data and still didn't update data from the car?

leeyuentuen avatar May 14 '24 06:05 leeyuentuen

for me, it look like it is a bug of polestar?

Screenshot_2024-05-14-14-45-25-47_40deb401b9ffe8e1df2f1cc5ba480b12 Screenshot_2024-05-14-14-45-31-19_c3a231c25ed346e59462e84656a70e50

leeyuentuen avatar May 14 '24 06:05 leeyuentuen

My data on that website is 2 months old but data in the app is correct.

kp-bit avatar May 14 '24 06:05 kp-bit

All my data look correct now, so apparently a backend issue... Closing issue.

kp-bit avatar May 14 '24 10:05 kp-bit

I still have this issue but I also see the incorrect number on the website so it does seem to be a backend issue. Curiously the app shows the correct number! Not sure why Polestar have two different sources of data.

3shirts avatar May 14 '24 12:05 3shirts

i'll keep this open due the issue is still exist

leeyuentuen avatar May 14 '24 18:05 leeyuentuen

Just to confirm I also see this behaviour. Correct value in the app, incorrect on the website and in the HA integration. Definitely an issue at Polestar

TotalGriffLock avatar May 14 '24 22:05 TotalGriffLock

Everything seems to be back to normal for me today. Out of curiosity, I'm wondering if those who are still experiencing issues might be running the P3.0.3 version of the Polestar software? As for myself, I'm currently on P2.14.3.

Also worth noting, I'm using version 1.5.7 of the integration, but I don't think that's the problem here.

wouterhardeman avatar May 14 '24 22:05 wouterhardeman