Battery status doesn't fit reality
I have tried to use the app on Android Auto for my VW ID BUZZ 2025 LWB PRO twice ( two seperate months ).
Both times I have concluded that the connection between my car and your app / server, was so vague that the data displayed on the screen was unreliable.
Several times the difference in what ABRP claimed to have registered from my battery, and the actual battery status was off by as much as 20 percent.
And more than once I have experienced that ABRP would claim that I would arrive at my destination with even more battery, than my actual status, without charging sessions.
I have previously used a different app called PUMP for IOS, which was able to communicate with the car without issues,
I don’t know If that can clearify any of the hurdles ?
Log in to comment and vote
Comments7
Linda ABRP
May 22, 2025
Hi
What kind of live data do you use?
User
May 22, 2025
I'm using enode.
Linda ABRP
May 22, 2025
Have you also given permission to get SoC via Android auto? If so this could be the problem.
User
May 22, 2025
Not as far as I am aware. To my knowledge only my VW app has connection with the vehicle besides enode
Linda ABRP
May 22, 2025
I can see that we don’t get that much data points from Enode and that’s probably why the SoC is not correct.
Unfortunately, there is nothing we can do about this as some cars do not work well with Enode.
User
May 22, 2025
And it wouldn't be a possibility to use tronity ?
I have previously used your, would I assume, biggest competitor PUMP, through tronity, and that never missed a beat ?
Linda ABRP
May 22, 2025
If you unlink Enode you should be able to see the Tronity option.