WeConnect-python
WeConnect-python copied to clipboard
Range drops significantly when i5 is finished charging but still plugged in
Describe the bug I’m pulling the range value and it seems when the car is fully charged, but still plugged in, the reported range decreases significantly until I have unplugged the car.
Interestingly its almost exactly the same decrease as if it was doing a conversion from km to miles but I’m not sure whether this is a coincidence or not. It seems like a strange bug, it does not affect the use but it is strange that it decreases when charging is complete.
To Reproduce Steps to reproduce the behavior:
- Plug in the car
- Wait until defined charging point reached
- Notice the range has decreased for no reason
- Unplug and the range is fixed
Expected behavior Range should be the same no matter what the state of charging is
Screenshots
- OS: Using https://github.com/mitch-dc/volkswagen_we_connect_id
I would guess it is coming like that from your car. What does the app show at the same time?
It's a bit of an MEB thing. Both the ID.3 and Cupra Born also do it. You'll notice that the ratio of error to correct value is exactly the same as the conversion from miles to km, so it seems to be the car getting confused about what units it should be returning data in.
Having a good old chuckle that the id.5 is still showing the same bug that both the ID.3 and Cupra Born have shown since day 1 and that VW still haven't managed to fix it 😄