Battery drain in Xpeng G6 due to Enode connection

Hello,

The following problem in connection with "Enode" has currently been identified:

Since my vehicle does not support an OBD dongle, I use the "Enode" data link as the basic connection to the vehicle.

This queries the vehicle status via the owner's vehicle account with the manufacturer (in this case XPeng G6).

And this is obviously repeated several times 24/7.

Unfortunately, this led to me discovering later on, inexplicably and shockingly at first, that my vehicle lost 2% battery capacity every day within 24 hours, even if the vehicle was only parked.

In my case, this corresponds to exactly 1.75 kWh/day, i.e. 60% or 52.5 kWh capacity in one month.

The daily battery loss was meticulously documented.

The initially inexplicable battery loss in my NEW VEHICLE led to extensive system tests in the workshop, which ultimately did not reveal any faults in the vehicle systems/electronics or similar.

The loss seemed inexplicable because no other consumers were connected in the vehicle.

I then remembered the vehicle connection via ABRP with Enode and deactivated it.

From this moment on, the battery loss stopped (was also documented).

Through repeated tests, it is now certain that the enormous loss of capacity of the traction battery due to constant Enode queries to the vehicle via its customer account and the associated activation of the vehicle electronics ("waking up") is the direct cause, even if ABRP is inactive for days or the app is closed.

My request:

Please contact Enode and try to ensure that Enode ONLY performs vehicle queries - and thus constant activation of the vehicle electronics 24/7 -

if possible, ONLY when ABRP is ACTIVE and IN USE.

This means ONLY THEN when the app is opened and/or when ROUTE PLANNING is being carried out/is active.

In terms of programming, this should be possible.

In my /BEV case, the current permanent 24/7 activation/query mode of "Enode" via ABRP results in a battery loss of 1.75 kWh/day, which amounts to

639 kWh/year (1,75 kWh × 365 days) or

7.3 FULL battery charges/year

with 87.5 kWh net capacity, which is also completely unacceptable in terms of the associated electricity costs/year.

I hope you can take care of the problem and, if necessary, either

ALTERNATIVELY

remedy it /only via your own app programming (possibly ...