Skip to main content

URGENT – VW ID. Buzz GTX immobilised following ABRP/Enode connection – possible 12V battery drain

I have a 2026 Volkswagen ID. Buzz GTX 4Motion in the UK.

On Wednesday 28 October 2026, I subscribed to ABRP Premium and successfully connected my vehicle through Enode.

The vehicle had charged normally overnight on Tuesday and was disconnected from the charger on Wednesday evening. It was subsequently parked and unused.

At approximately midday on Thursday 29 October, the vehicle was completely immobilised:

  • Red "Electric Drive not working" warning immediately on waking

  • Multiple additional electrical faults

  • 12V battery warning displayed in both the vehicle and VW app

  • Unable to engage drive or enter Ready Mode

  • Vehicle no longer responding to remote app commands

  • Traction battery showing approximately 80% charge

VW roadside assistance attended. The technician found apparently normal 12V voltage and attempted external boosting/charging without success. The vehicle had to be recovered on a low loader to a Volkswagen dealer.

The dealer has now indicated that a discharged 12V battery was responsible for the failure.

Importantly, Volkswagen's "Optimised Battery Use" feature was enabled throughout.

I have found an existing ABRP discussion reporting apparent Enode-induced 12V battery drain in another ID. Buzz:

https://abrp.featurebase.app/p/enode-connection-enabledisable

Given the timing and similarity, I am concerned that Enode's polling behaviour may have prevented the vehicle from entering its normal low-power sleep state, causing excessive 12V battery discharge.

Could ABRP please escalate this to Enode and investigate:

  1. The frequency of API polling and vehicle wake-up requests between 28 and 29 October.

  2. Whether Enode can obtain logs showing unusual activity or repeated vehicle wake-ups.

  3. Whether Volkswagen vehicles are affected by the polling/battery-drain issues reported by other users.

  4. Whether polling can be suspended whenever the vehicle is not being driven.

  5. Whether disconnecting the integration fully stops all Enode requests.

This incident resulted in a complete breakdown and vehicle recovery, rather than merely reduced battery life.

I would appreciate a technical response and am happy to provide further information and VW diagnostic findings privately.

Thank you.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Status: Awaiting Clarification3 comments

Log in to comment and vote

Comments3

  • Mahde - ABRP

    Team•

    Nov 9

    Hello @ABRP User #3216186,

    We received this response from Enode regarding your issue:

    “We checked the end user's vehicle (asset e69bfcd9-f582-459a-9a40-52a10033cca1, user abrp_user_3216186_vehicle_104788925965, VIN WV2ZZZEB0VH010680) for 28 to 30 October.
     
    Most of our requests read data from Volkswagen's servers without contacting the car. To keep data current, we occasionally ask the vehicle for fresh data, which wakes it briefly. Your webhooks show this in real time: lastUpdated timestamps advance when the car sends new data and stay unchanged otherwise.
     
    We saw no unusual or repeated activity, and this vehicle was in line with the rest of the Volkswagen fleet. These requests use some extra 12V power, but in the cases we have seen, a parked vehicle usually takes a week to a few weeks before this causes 12V problems. This one had been parked for less than a day at about 80%. Volkswagen does not report the 12V level through this integration, so we cannot see it directly.
     
    The schedule cannot currently be paused while a vehicle is parked. Disconnecting stops all Enode requests, and none were made after the unlink on 30 October 09:35 UTC.
     
    If the user wishes to provide us with the dealer findings on whether the 12V battery was faulty would help us assess this further. However overall analysis on our side shows that everything in this instance was normal Enode activity.”

    There seems to be no fault from either Enode or ABRP that could’ve caused this issue. We suggest you check this with your dealer on what may have been causing the failure of your battery in this situation.

  • Mahde - ABRP

    Team•

    Nov 6

    @ABRP User #3216186,

    We have sent the request to Enode and they will respond back to us when they have investigated this!

  • Bo (ABRP)

    Team•

    Nov 4

    Thanks for reporting and sorry about your experience! We have not heard this from other VW owners, and we have many thousands of connected VW vehicles. However, we will still ask Enode to investigate your logs and see if the Enode connection could have caused it.