Request a Feature

Jens Keller

I agree - manually tweaking the "Reference consumption" is mandatory to get an acceptable estimate for the real consumption in not-intermediate outside temperature conditions, i.e. to even get the correct charging stops calculated especially for long routes (not only charging times).

For example, for my MG5 Long Range I get acceptable results with
- 170 Wh/km@110km in optimal summer conditions (25°C outside temperature)
- 220 Wh/km@110km/h in average winter conditions (0°C outside temperature)

Your default value for the "MG5 long range beta" is currently 182 Wh/km@110km/h, which gives good results only around 18°C outside temperature.

Using the "auto learn" feature for consumption with an OBD does not help much, as it provides a long term average. Resetting it every month or so might be a workaround, so that the "current" month averave can be evaluated, but this is tedious, inaccurate and not everybody has an OBD connected all the time.

You mentioned in another request that estimating battery temperature is hard, but using at least the outside temperature should be easy. You might even add a configurable value for "outside temperature weight for consumption calculation", so experienced users can set values manually, while you learn optimal values from collected user trips, and maybe even factor in these manually set values.

By the way, the described consumption deviation occurs regardless if you activate "real time weather" or set a fixed value for the trip manually.

Thanks for constantly implementing various optimizations!