BMS to SoC Table for Skoda Enyaq

[stwa2020]

Hello All,

I've discovered that the BMS/SoC value calculation I received from WiCAN differs by more than 5% from the value I can see in the App or in the car.

I use a WLAN LTE router with OpenVPN to receive SoC and odometer information in IOBroker while I am driving. I also have a script that updates a table every time the SoC changes. This table contains the BMS, App SoC and information on whether the car is charging.

This is what the table for the 60 kWh battery looks like. It's not finished yet as I'm still collecting data.

Charge

Discarge

There is already a difference of up to 5% between charge and discard, and together with the BMS-to-SoC calculation, the value can differ by up to 8% between the BMS and App or Car SoC.

Has anyone created such a table yet ?

I know there are additional values that will alter the BMS-to-SoC ratio, but I would like to get as close as possible.
I created such a table because the API request can get lost when the app developer or Škoda decides to make changes that block the API requests or stop offering this function.

I'll also add an ESP with a GPS module to send GPS location information to my IOBroker via MQTT or has anyone found a way to read this information via MeatPi ?

[meatpiHQ]

@stwa2020 what's the vehicle model it's possible that we need to make a new profile for your exact model.

[stwa2020]

@meatpiHQ It's not the profile of the Škoda Enyaq 60, but rather how the BMS formula is used to calculates the SoC. It works, but linearly. I've used CarScanner and it does the same thing. A fixed value is used in the formula to calculate the SoC, but this value changes during charging and discharging, and the BMS values can still change by +/-5%, even when the app and the car show 0% or 100% SoC. Therefore, it's not linear, and in the worst case, there can be a difference of up to 8% between the app and the car. This behaviour is less visible during charging, and perhaps not many people pay attention to it.