Yes. It’s a UK model and arrived set up for our unique mix where we use miles for range, trips and economy, but metric for distance to intersections and temperature, etc. This is normal for all car manufacturers.
The values are displayed correctly in the car and on the MercedesMe App, but in the data transferred into HA, (see object below), the ‘units’ value is miles.
If I use this entity in lovelace, the 187 (below) appears always as ‘187 km’. You cannot apply units to it or a suffix. It always shows km even though it is 187 miles. As I said I used node red to pick out the attribute and store it in a new entity, but this is cumbersome and inefficient.
{"_msgid":“cb0efcfb.b7e0d”,“payload”:“187”,“topic”:"",“data”:{“entity_id”:“sensor.wd70kwf_range_electric”,“state”:“187”,“attributes”:{“car”:“WD70KWF”,“vin”:“W1K2938902F022320”,“original_value”:“301”,“distance_unit”:“MILES”,“retrievalstatus”:“VALID”,“timestamp”:“2021-02-10T14:30:11”,“unit”:“MILES”,“precondActive”:false,“maxrange”:“197.6”,“distanceElectricalStart”:“2.2”,“chargingstatus”:“3”,“electricconsumptionreset”:“1.3”,“selectedChargeProgram”:“0”,“distanceElectricalReset”:“28.4”,“soc”:“95”,“chargingactive”:false,“electricconsumptionstart”:“0.6”,“unit_of_measurement”:“km”,“friendly_name”:“WD70KWF Range Electric”,“icon”:“mdi:ev-station”},“last_changed”:“2021-02-10T14:30:13.780541+00:00”,“last_updated”:“2021-02-10T14:30:13.780541+00:00”,“context”:{“id”:“7ebd67f348be674bed730dbc8cacc60d”,“parent_id”:null,“user_id”:null},“timeSinceChangedMs”:24062,“original_state”:“187”}}
