Battery state of charge 1% on AAOS in Renault Megane e-tech
Hello, for me it always shows only 1% of the SoC and the battery size is too large by a factor of 100.
What am I doing wrong?
I have already deleted the car and added it again, but nothing changes.
Enclosed also a screenshot
Thank you very much,
VG
Matthias
Log in to comment and vote
Comments44
Bo (ABRP)
May 26, 2025
PinnedThanks for reporting! The Megane reports 6553.5 kWh battery size and we don’t really have a way of getting the correct size. We are looking into potential solutions.
Timothy Smith
May 28, 2025
I've got the same issue but it is okay with Enode data until I open the Android Automotive app and then it overwrites the figure with 1%. Is there a way you can Hotfix the code to prefer the Enode data for SOC at the moment or at least let us chose what data to use for which item, that way at least people with Premium can have it show correctly even if the Battery Capacity is showing as a increase by a factor of 100 (Maybe Hard Code the Battery Capacity for the moment too for each version so it at least works, majority being the 60kWh version).
I've just paid for a month premium because it used to work for me and Now it's basically useless and I'm out the subscription cost.
Mine is a 2002 Megane e-tech (No Heatpump version and is still getting updates)
Bo (ABRP)
May 30, 2025
We have just implemented a workaround for this in ABRP 6.0.2 which is not yet publicly released. Are you interested in testing it in your vehicle? If so, please send us an email at contact@iternio.com and we will add you as an internal tester.
Timothy Smith
Jun 2, 2025
I would be happy to test this for you. I'll send an email through to you now.
Frédéric Becquart
May 10, 2025
Hello,
I have the same problem with my Renault Megane eTech.
Is there a solution ?
I have to use Megane application instead of ABRP (my favorite one ;-) )
Bo (ABRP)
Jun 2, 2025
We have added a workaround for the issue in the Megane in ABRP 6.0.2 - let us know if this solves the issue for you!
Seb
Jun 2, 2025
Hello , still the same for me, with ABRP 6.0.2 , not solved.
André Parnelöv
Jun 2, 2025
I tried the 6.0.2 version, but still have the same issues (battery and percentage)
jesus gomez
Jun 2, 2025
Same as before with 6.0.2 (3410). Not fixed
David Bradnum
Jun 2, 2025
Updated the app in the car to v 6.0.2 today, and unfortunately still see the incorrect battery capacity and therefore incorrect SoC. Please let me know if there is any further information I can provide or anything I can do to help you resolve this.
Bo (ABRP)
Jun 3, 2025
Could you please go to the settings menu in ABRP in Automotive and select “Send a bug report”? This helps us get some more details on what your car reports.
David Bradnum
Jun 3, 2025
Sure - have just done so, a minute or two ago. Wasn't quick enough to capture the report id that appeared on screen, but presumably you can link with my user id.
Bo (ABRP)
Jun 4, 2025
Thanks - I have just pushed a version 6.0.2 (2) for internal testing. If you want to join the test, send an email with your Google account email to contact@iternio.com and we can add you.
Timothy Smith
Jun 3, 2025
I'm having the same issue. Have tried it Monday and Tuesday just in case there was a delay. I also cleared the Cache and Storage plus uninstalled and reinstalled the app on both phone and Android Automotive. Still showing wrong Battery Size and SOC. I'll hit the report Bug button in the car tomorrow (Wed) when I'm back in it. Unfortunate as I was looking forward to using it today (Wed) for a trip.
Wouter Verbeke
May 1, 2025
I have the same problem. I have a 2023 Megane EV60-7.4kw and it has been working perfectly. Since a couple of weeks, ABRP thinks i hava a 6553.5kWh battery, what i asume is a factor 100 wrong. ABRP thinks i can drive from Belgum to the south of France using 2% battery (i wish 😇)
David Bradnum
May 5, 2025
I also have the same problem with misreported battery capacity of 6553.5kWh, on a late 2022 Megane Etech EV60.
I know that ABRP live data was working properly on the car about 1-2 months ago, so something has definitely changed somewhere.
Philippe Gaborit
May 13, 2025
Hello,
On my Renault Megane (July 2024), I have exactly the same problem as described above. I also have a problem with data retrieval on the driver's screen (behind the steering wheel): the arrival time is 2 hours out of sync with the time on the main screen and the remaining distance is displayed in meters instead of km.
Bo (ABRP)
Jun 5, 2025
There is now an ABRP 6.0.2 (3) on Google Play for you internal testers - we think the issue has been solved properly now.
Jesús Gómez
Jun 5, 2025
You are on the correct way, but unfortunately it's not full fixed. Battery capacity still 6553.5 kWh ( FF in hexadecimal?), and SoC not accurate (in my car ABRP shows 63% but the car shows 65%)
As result of the improper capacity, calculated trips are incorrect. I calculated a trip from Irún (north of Spain), to Geneva (Switzerland), and the total SoC consumed was a 3%
Here are some screenshots, one of these the report sent
Jesús Gómez
Jun 5, 2025
If I don't bad remembering, this slight error in SoC, occurs with enode integration too
Bo (ABRP)
Jun 5, 2025
Thanks - yes, the reported capacity is -1 in 16 bits, divided by 10 for some reason :)
However I think we correctly delete it when received from the car but it remains in the backend for a while. We will try and remove it from the backend.
The SoC not fully matching the display is unfortunately something we have to live with, most OEMs report one number through Automotive/Auto and a different number for display. The display number most likely is “fixed” to make it appear better somehow.
Bo (ABRP)
Jun 5, 2025
There is now a 6.0.2 (4) internal test build available on Google Play for internal testers. This will replace false battery capacity with a fixed 60 kWh number and should solve all remaining issues. Let us know!
Jesús Gómez
Jun 5, 2025
Seems to work ok, at least calculating trips
I will report if I find some trouble
Thanks :-)
Jesús Gómez
Jun 5, 2025
When will the patch be public to all users?
Bo (ABRP)
Jun 6, 2025
We have sent it for review now to Google Play. It will be published as soon as it is approved as “6.0.2 (live data update)”.
Jesús Gómez
Jun 7, 2025
Thank you Bo, but maybe i have found an issue?
When calculating a trip, it remains in “calculating trip…”. It calculates the trip, indicates deviations, etc… but does not calculate charging stops. It is a very weird thing because sometimes does good, but the most of the times not.
In photo a trip which does not require charging, and calculates the final SoC. I noticed this, the final SoC, reaching the destination, because in this state (calculating trip…), it does not do zoom out and does not show buttons for send bug report, only possible go backwards
I don't know if this happened before, because I was using Google maps, because ABRP was not working (the 1% SoC bug, this week fixed)
Seb
Jun 5, 2025
The SOC is fixed ! Thank you. I try to plan a trip , and the estimate battery % at the end of the trip is very very optimistic. Using only 30% for 260 km 🤔🤔
Bo (ABRP)
Jan 8, 2025
Thank you for the feedback! I cannot find the Automotive data in our raw data logs, perhaps they have been expired. Has live data in the Automotive app ever worked from your Megane?
jesus gomez
Jan 8, 2025
No, never, first time I tried it through automotive directly. Live data through enode, yes, I tried it several months ago and it worked, in automotive and in android auto.
jesus gomez
Apr 19, 2025