Skip to main content

Nissan Ariya SoC data (Enode) is stuck while driving

Bug Reports

When I deviate from a planned route the software recalculates arrival from the initial start percentage ( and it shows) instead of the actual percentage. I noticed this occasionally happens during driving on a planned route without deviating, mostly after 20 minutes or so. It means that advise when to recharge is pointless

Where does this happen?
Posted by Paul Rademakers ·
Status: In Review13 comments

Log in to comment and vote

Comments13

  • Katya S. changed status to Awaiting Clarification
    Team•

    Feb 20, 2025

    Pinned

    Hi @Paul Rademakers,

    I’ve checked your recent drives where the SoC value still is reported as static by Enode / Nissan. We’re in touch with Enode regarding this and we’d like to know if;

    When this happens, does the Nissan app report the same value as ABRP/Enode or does it report a correct/different one for SoC?

    • Paul Rademakers

      •

      Feb 21, 2025

      Hi Katya,

      The Nissan app reports a different / correct value compared to ABRP. Both values are identical at start of a trip but start to differ while driving. Without a clear cause the value while driving of ABRP goes back to the value at the start and recalculates a different predicted end-state SoC during the trip. I had multiple trips where while driving Nissan SoC was under 10% where ABRP stated that is was 97% and end state would be 85%. I got lost and had to change to Nissan navigation to find immediately a charger. Not very convenient

      Does this help You?

      KR Paul Rademakers

      • Katya S.

        Team•

        Feb 25, 2025

        Thank you, we definitely agree this is not convenient and it is not how things are supposed to work. I’ve let our contact at Enode know and they’ll investigate further.

  • Bo (ABRP)

    Team•

    Jan 20, 2025

    Looking at the live data received from your car, it seems like the SoC is updated very seldom. Does it typically show the right value when comparing ABRP and the car?

    • Paul Rademakers

      •

      Jan 21, 2025

      Hi Bo, no. Do I have to update it manually?

      • Bo (ABRP)

        Team•

        Jan 22, 2025

        I will open a case for your car with Enode and see if they can improve it, otherwise I would get an OBD BLE adapter if I were you - we just recently added support for the Ariya.

  • Bo (ABRP)

    Team•

    Jan 20, 2025

    The Nissan connection via Enode seems to produce static SoC values with large jumps a few times per drive. We are investigating it, but if you want to improve the quality of live data while driving, I recommend you to get an OBD BLE dongle in your car and add this live data connection in ABRP. We just released support for the Ariya.

  • Katya S.

    Team•

    Jan 28, 2025

    Hi @Paul Rademakers,

    Could you clarify what you mean by ‘initial start value’?

    • Paul Rademakers

      •

      Jan 28, 2025

      Your colleagues noticed that the soc value seems to be static , instead of actual

      • Katya S.

        Team•

        Jan 29, 2025

        Ok, so there’s a duplicate ticket. I’ve finally found the ticket we opened with Enode regarding this, and we’re awaiting their reply.

  • Paul Rademakers

    •

    Jan 28, 2025

    Hi,

    I mean the soc at start of a trip. I noticed that this value is showing occasionally back again during a trip instead of the soc of that moment. The charge point info is than wrong, the app notifications where to charge at recommended soc has no meaning anymore

  • Paul Rademakers

    •

    Mar 15, 2025

    Hi ,

    Please provide update on submitted ticket. The issue of static SOC info to or from Encode still not resolved although we have new 5.7 release. I have added dongle in my Ariya which communicates perfectly with my Android phone on SoC and Nissans own navigation service communicates with SoC. But ABRP display says no connection, so I could be caused by Android Auto? Shop this helps. KR Paul

  • Katya S.

    Team•

    Apr 8, 2025

    Hi @Paul Rademakers,

    Here’s the latest reply from Enode;

    “The root problem is that Nissan returns outdated information from their vehicles. Here is a raw API response from their API, and you will see that we requested the data at 16:34, but the battery data returned was last fetched from the vehicle at 13:49!

    (screenshot showing example)

    For this reason we grade Nissan reliability 1 or 2 in our     capability table, and we might downgrade the Ariya model to 1 due to behaviour like this. Unfortunately this is inherent to the Nissan and there is no mitigation that we can do. Hope that explains what you saw.”

    We’ve since replied but haven’t heard back. It is possible that the data can still be handled correctly but the issue is unfortunately on our table.