flespi users can now get OEM data through High Mobility platform to flespi. This topic will be used to post changes in high-mobility protocol
The full guide on how to set up simulated data flow is here
Added parsing for the parameters: engine.ignition.status, position.source, gps.signal.level and position.altitude
parsing updated: time_to_complete_charge => can.full.charge.time status => can.vehicle.battery.charge.state plugged_in => can.vehicle.battery.charging.cable.connected.status estimated_range => can.vehicle.battery.remaining.range average_speed => can.average.speed time_to_next_service => can.service.time time_to_next_oil_service => can.oil.service.time charging_current => can.vehicle.battery.charge.current charging_rate => can.vehicle.battery.charge.rate estimated_mixed_powertrain_range => can.vehicle.mixed.powertrain.range primary_energy_level => can.vehicle.primary.energy.level distance => can.trip.mileage end_odometer => trip.stop.mileage start_coordinates => trip.start.latitude + trip.start.longitude end_coordinates => trip.stop.latitude + trip.stop.longitude dashboard_lights.brake_fluid_warning => can.brake.fluid.low.indicator.status dashboard_lights.tire_pressure_low => can.tpms.indicator.status engine_time_to_next_service => can.maintenance.before.engine.hours distance_to_next_service => can.maintenance.before.mileage
