Live data SOC switches between source with differing values, affecting route planning

So my car (Peugeot e-5008) shows a tampered SOC on the dashboard and in Android Auto. I know it is “corrected” to provide some sort of user experience improvement, because I can read the actual SOC using my OBD reader.

At full charge, the SOC reported by OBD is between 90 and 97% (depending on temperature), while the dashboard always shows 100% at full charge. As I start a trip, the SOC from the OBD decreases as expected while the dashboard SOC stays at 100 for an unrealistically long time, until it suddenly decreases to sort of match the OBD SOC.

I say sort of matches, since there is almost always a difference between the two values, of up to 5%. The difference depends on temperature and the SOC ( the difference is least around 50% SOC), and it can be both positive and negative.

My Abrp live data streams data from CarScanner, which reads the OBD SOC. Sometimes it also reads from Android Auto. Because the two values often differ, ABRP thinks the SOC switches back and forth, which negatively influences the route planning while driving. Sometimes a new route is suggested because of this.

I suggest to provide an option to block specific data streams (like Android Auto SOC) if a more reliable source is available (like OBD SOC).