Issue with SoC drop and extreme reference consumption when combining Enode + OBD2 (Stellantis / Peugeot e-308)

When using both a cloud connection (Enode) and a direct OBD2 BLE dongle simultaneously in ABRP, a conflict occurs between the two data sources at the start of a trip. This causes a major error in the calibration of the reference consumption.

• ​The Cause: While parked, Enode reads the net (dashboard) SoC (e.g., 72%). As soon as the trip starts and the OBD2 dongle connects live, ABRP switches to the gross (real) SoC provided by the BMS via the OBD2 port (e.g., 67%).

• ​The Result: ABRP registers this ~5% discrepancy as a sudden, massive drop in battery capacity during the very first minute of driving. Because of this, the calibrated reference consumption instantly spikes to unrealistic values (such as 756 Wh/km), which completely ruins the route planning.