Missing fields in telemetry: charge_miles_added_rated, charge_miles_added_ideal

[rawmean]

Can you please add these fields to telemetry to make the information closer to once provided by vehicle_data endpoint?

[ThomasAlxDmy]

Can you look at the last definition and tell us what's currently missing from your perspective? Curious to also understand the use-cases

[rawmean]

Can you look at the last definition and tell us what's currently missing from your perspective? Curious to also understand the use-cases

I examined the fields in the vehicle_data.proto and do not see the equivalent of charge_miles_added_rated and 'charge_miles_added_idealwhich exist in thevehicle_data` endpoint. These two fields enabled us to compute information related to each charging session.

Since the endpoint for charging history is removed (there are charging_history endpoints currently available but one only returns supercharging info and the other one is related to the wall charger) these fields are helpful in creating charging session information.

Of course, one can add state to the dispatch code and record these values for each vin, but it would be great if the these values could be available in the fleet telemetry for reasons mentioned above.

Thanks