Skip to main content

Incorrect vehicle track when using Generic Live Data / Enode

Bug Reports

Hello,

I'm using ABRP with both Generic Live Data and Enode for my Citroën ë-C3 (2025).

State of charge and other vehicle data appear to work correctly in both cases. However, the vehicle location data seems to be incorrect or inconsistent.

During a drive, the vehicle position repeatedly jumps between my current location and another fixed location, which often appears to be the starting point of my last trip or a previously reported location.

As a result, the recorded route in ABRP becomes corrupted and contains long straight lines and large triangular jumps instead of following the actual road. This makes the trip history and driving log unusable.

The issue occurs repeatedly, with location updates switching back and forth approximately every minute.

I've attached a screenshot showing the behavior.

Additional information:

  • Vehicle: Citroën ë-C3 (2025)

  • Data sources tested: Generic Live Data / Enode

  • State of charge and vehicle status data are reported correctly

  • The issue appears to affect only GPS/location data

Could you please investigate whether outdated or invalid coordinates are occasionally being reported or incorrectly merged into the vehicle track?

Thank you.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Samy & Giuli ·
Status: Completed8 comments

Log in to comment and vote

Comments8

  • Linda ABRP

    Team•

    Jun 18

    Hi

    Which third party app do you use? It seems like it don’t give us correct positions for your car.

    • Samy & Giuli

      •

      Jun 18

      Hi,

      In this case, I only used ABRP with the corresponding live data integration, either Generic or Enode, as described.

      When I disable both integrations and drive using only the data that ABRP receives through Android Auto, the problem no longer occurs and the vehicle position is displayed correctly.

      • Samy & Giuli

        •

        Jun 19

        One idea that I think would be really useful is the ability to choose which data ABRP receives from which integration.

        For example,As I've noticed/seen in abrp that the location data coming through the API/Enode is unfortunately quite inaccurate and unreliable. At the same time, battery-related data such as state of charge, charging information, and consumption data work extremely well.

        I've also read that Stellantis often provides the last known vehicle location from when the car was last turned on or off through its API. Based on the location data I'm seeing whenever the API/Enode integration is active, this seems very plausible and would explain the inaccurate positioning.

        Ideally, it would be possible to configure ABRP so that it only uses Android Auto for location data, while battery and charging data continue to come from the API/Enode integration.

        This would allow each data source to be used for the information it provides best, creating a win-win situation and improving the overall accuracy and user experience.

      • Linda ABRP

        Team•

        Jun 22

        What have you connected with the Generic link?

        • Samy & Giuli

          •

          Jun 22

          I have connected ABRP via Home-Assistant Stellantis integration using the Generic Link, but that is not relevant in this case since the issue still occurs even when I completely disable the Generic Link and allow ABRP to receive data exclusively through Enode.

          When ABRP receives data only through Android Auto, there are no issues with the tracking. The incorrect vehicle track appears only when live data is provided through the Generic Link or the Enode integration for Citroën vehicles.

          • Linda ABRP

            Team•

            Jun 24

            Some cars don’t get data very often from Enode and we only get one update from your home assistant that gets old. So in this case it’s best for you to only use Android auto.

            We are working on a integration with Home assistants so when it’s working we can get correct location from that one.

            • Samy & Giuli

              •

              Jun 24

              That sounds great!

              Just wondering is there currently any way to disable location tracking while still getting the "good" vehicle data through Enode or the Generic API?
              when I only use Android Auto I don't get information about charging sessions or other infos in ABRP.

              Is location data required for those integrations to function properly or could the vehicle data still be used without it?

              Also is this something you might consider supporting in the future so users could opt out of location tracking while still benefiting from the richer vehicle data provided by Enode or the Generic API?

              • Linda ABRP

                Team•

                Jun 24

                Right now you can only get all data or no data. Please make a request under Feature request for selecting which data you want. There are probably other users that also want a feature like that.