[Changelog] high-mobility protocol

baja

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

baja

Added parsing for the parameters: engine.ignition.status, position.source, gps.signal.level and position.altitude

baja

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

baja

protocol updated to support MQTT V2. Please migrate from MQTT v1 till February 2026.

baja

parsing updated:

Added support for new capabilities: doors, hood, trunk, windows
Added new parameters:
- can.fuel.volume
- can.doors.lock.status
- can.hood.status
- can.trunk.status
- can.front.left.window.status, can.front.right.window.status, can.rear.left.window.status, can.rear.right.window.status
- can.engine.oil.service.status
- can.brake.fluid.change.date
- can.brake.fluid.status
- can.oil.service.date
- can.vehicle.check.date
- can.vehicle.check.mileage
- can.vehicle.check.status
Changed estimated_range mapping from can.vehicle.battery.remaining.range to can.vehicle.remaining.range

baja

New parameters:

can.vehicle.battery.charge.limit (percentage) - vehicle battery charge limit setting
can.abs.active.status (boolean) - ABS active status
can.passenger.airbag.status (boolean) - passenger airbag activated status
trip.braking.count (number) - brake applications count for the trip
trip.code (string) - unique trip identifier code

baja

New telemetry parameters:

EV energy consumption: can.trip.battery.power.consumption (consumption rate since trip start, kWh/100km) and can.vehicle.battery.power.consumption (since reset)
single.charge.range — maximum electric range with 100% battery
Eco-driving scores: can.eco.acceleration.score, can.eco.constant.score, can.eco.coasting.score (percentage) and can.eco.bonus.range (km) — additional range gained by eco driving
Per-door lock states: can.front.left.door.lock.state, can.front.right.door.lock.state, can.rear.left.door.lock.state, can.rear.right.door.lock.state, plus can.trunk.lock.state
Interior illumination: can.interior.light.front.status, can.interior.light.rear.status and per-seat reading lamps can.reading.lamp.front.left.status, can.reading.lamp.front.right.status, can.reading.lamp.rear.left.status, can.reading.lamp.rear.right.status

More accurate message timestamps: High-Mobility delivers each property with its own timestamp, and a single payload may mix fresh and historical data — e.g. a trip-end report carries trip start properties timestamped hours earlier. Previously all properties were registered as one message with a single timestamp. Now the channel registers a separate message per distinct timestamp (1-second granularity), so every parameter lands at its true position on the timeline.

Commands: the provision_device command now supports an optional tags field — custom key-value pairs attached to the vehicle in the High-Mobility fleet clearance API.