search

pypolestar / polestar_api

Polestar API - Home Assistant Component
MIT License
137 stars 25 forks source link

"estimate_range" and "estimate_full_charge_range" entity values #87

Closed ohaue closed 9 months ago

ohaue commented 9 months ago

Version 1.5.4

The entity "estimate_range" and the entity "estimate_full_charge_range" seems to always have the same value. Looks to me as if the "estimate_full_charge_range" has the "estimate_range" value.

I don't know if this is a 1.5.4 issue. It used to be correct before.

leeyuentuen commented 9 months ago

one is the actual estimate range, the other one is if you have fully charge your car.

so if you can drive 200km on 100%, this is your full charge range, but if you still have 20%, you can only drive 40km on your current battery level

ohaue commented 9 months ago

image

leeyuentuen commented 9 months ago

Screenshot_2024-01-10-19-09-48-52_c3a231c25ed346e59462e84656a70e50

ohaue commented 9 months ago

OK - must be a failure on my Polestar end :-)

image image

leeyuentuen commented 9 months ago

i'll take a look, maybe there is some wrong code or something

Ottmar0815 commented 9 months ago

Same issue here.

leeyuentuen commented 9 months ago

The full range value is based on the normal range and calculated with the battery percentage

I can't reproduce this issue, but maybe try this beta maybe that should be the issue: https://github.com/leeyuentuen/polestar_api/releases/tag/1.5.5

ohaue commented 9 months ago

Works for me now in 1.5.5: image

VdR1960 commented 9 months ago

I can confirm this to be fixed with the 1.5.5. release.

leeyuentuen commented 9 months ago

https://github.com/leeyuentuen/polestar_api/releases/tag/1.6.0