Closed leeyuentuen closed 5 months ago
I've put a max limit to prevent to high value
Odometer has changed to unknown
open the entity and change the unit of measurement from m to km
i saw that i need to put the limit higher then 1000000
OK, confirmed. Switch to KM works as expected. Also if i change to Mi, and back.
Confirmed. Works with m
and km
. Does not work with cm
, though ;) Is there really a need for a limit?
@m0wlheld As you see on the opening post image, sometimes, weird responses from Polestar make the graph go high
@m0wlheld As you see on the opening post image, sometimes, weird responses from Polestar make the graph go high
Speaking of which: The API currently reports 0 km (infact 600m) for the Odometer. It's the same for this HA integration and for the Polestar site. So - not a bug here.
It gets even better: Currently the API is reporting 2^31m, so the Odometer display 2.147.484 km ... looks like they are trying fix something.
It gets even better: Currently the API is reporting 2^31m, so the Odometer display 2.147.484 km ... looks like they are trying fix something.
in the log? or showed in the gui that make spikes?
It‘s reported wrong by the remote Polestar API. You cannot fix it.
It‘s reported wrong by the remote Polestar API. You cannot fix it.
but this you saw the value on your home assistant gui? normally i have skip this high value
this should be wrong data from polestar prevent this issue
maybe set max limit of 1.000.000