VW ID.7 enode connection - no trip data
I have noticed that I see only occasional and even so mostly incomplete trips in ABRP. Chargings are mostly recorded and seem correct. I have Premium subscription but use Enode connection, not an OBD dongle. When I start driving, I don’t use the ABRP app, e.g. to plan and then start the drive because I assume the car send data over Enode independently. I suspect ID.7 simply does not send the data, i.e. the API does not function correctly. Does anyone know what is the case?
- Where does this happen?
- ABRP version number (found at bottom of settings menu)
Log in to comment and vote
Comments7
Sep 19, 2025
PinnedHi @Petteri Ruotsalainen,
I’ve reviewed the activities, and there does seem to be an issue with receiving data for driving activities. I’ve submitted a ticket with Enode regarding this.
I can see that we successfully logged trips back in July. Were you using Enode then as well, or have you switched live data methods since?
Petteri Ruotsalainen
Sep 19, 2025
Enode only. Can you also confirm that vehicle data retrieval does not need to be triggered through ABRP, e.g. by navigating a trip planned in ABRP.
Katya S.
Sep 23, 2025
Thank you, we’re awaiting a response from Enode. Yes, you do not need to use navigation in ABRP for activities to be logged. However, if you are, we will send a “nudge” to Enode every other minute to ensure we get data frequently.
Petteri Ruotsalainen
Oct 3, 2025
Enode not responding? Still no trip data.
Katya S.
Oct 6, 2025
Hi! I nudged them regarding our pending tickets last week, and they replied to this ticket during Saturday:
“I've checked the data we receive from VW for this vehicle and can confirm I can see this behaviour reflected there.
When this vehicle is in motion (as evidenced by the battery level dropping steadily between updates), VW does not return a live location for the vehicle. We see other EV OEMs do this for data privacy reasons as well (e.g. Volvo). The updates are successful from a technical perspective, but the location data is deliberately stripped out until the next time that the vehicle is stationary.
On this basis I believe there is nothing wrong with the data that Enode is sharing with ABRP - we are accurately sharing the information that is available from VW.
If this has changed recently compared to data this user has seen before, it may be the case that VW has changed their implementation. We ensure that all historical location data is wiped from our platform for data privacy reasons, so I cannot check or confirm if this has changed by comparing against older data unfortunately.
You could ask the user to verify this by checking the vehicle's location in the first-party VW app when the vehicle is being driven. My expectation is that the first-party app will not show a live location either. However, if you see evidence that contradicts this, please ask the user to take a screenshot and share it with you to pass on to us so we can investigate.”
So, based on Enode’s findings, it seems that VW has suddenly changed what data they provide.
However, as Enode support suggested, we’d like to verify and I’d like to ask you - could you check if you’re seeing the correct location of the vehicle in the VW app, while driving?
If the location is updating correctly in the VW app, please make a screenshot and provide it here so that I can pass it on to Enode.
Petteri Ruotsalainen
Oct 18, 2025
Hi. Unfortunately it seems Enode is correct. VW app does not show car location while driving. I guess should ask VW about this.
Petteri Ruotsalainen
Oct 11, 2025
Hi. Tested this yesterday. Looks like Enode is correct. Car position was not updated during 5 min commuting trip nor during a 4 hour drive, with VW navigation active. Two location point were somehow captured in ABRP MyDrives. This makes a Premium ABRP account pointless, I guess only options are to get VW change their implementation (not holding my breath) or investing in OBD BT dongle?