Skip to main content

Vehicle

Battery Events#

These events are calculated from the voltage level measured via the OBD-II connector and are fired by the trigger battery_event in the Obd Manager.

TagDescriptionFields
vehicle/battery/unknownThe battery state is unknown.reason
vehicle/battery/chargingThe battery has started charging.-
vehicle/battery/dischargingThe battery is discharging.level
vehicle/battery/overchargingThe battery is overcharging compared to normal.-
vehicle/battery/charging_slowThe battery charges slowly.-
vehicle/battery/critical_levelThe battery voltage has reached a critically low level.level

FIELD DEFINITIONS

NameTypeDescriptionExample
reasonTextThe explanatory cause for the event.-
levelNumberBattery level as a percentage.90

Engine Events#

These events are fired by the trigger rpm_engine_event in the Obd Manager and are only intended for ICE-type cars.

TagDescriptionFields
vehicle/engine/not_runningThe engine is currently not running. This event is usually seen during start-up.reason
vehicle/engine/runningThe engine is now running.-
vehicle/engine/stoppedBefore the engine was started, now it is stopped.reason

FIELD DEFINITIONS

NameTypeDescriptionExample
reasonTextThe explanatory cause for the event.-

Communication Events#

These events are fired by the trigger communication_event in the Obd Manager and used with EV-type cars that are unable to produce Motor Events.

TagDescriptionFields
vehicle/communication/inactiveCommunication with the vehicle is currently inactive. This event is usually seen during start-up.reason
vehicle/communication/establishedCommunication with the vehicle is established.-
vehicle/communication/disconnectedCommunication with the vehicle is disconnected.reason

FIELD DEFINITIONS

NameTypeDescriptionExample
reasonTextThe explanatory cause for the event.-

Motor Events#

These events are fired by the trigger rpm_motor_event in the Obd Manager and are intended for EV-type cars.

TagDescriptionFields
vehicle/motor/not_runningThe motor(s) is currently not running. This event is usually seen during start-up.reason
vehicle/motor/runningThe motor(s) is now running.-
vehicle/motor/stoppedBefore the motor(s) was running, now it is stopped.reason

FIELD DEFINITIONS

NameTypeDescriptionExample
reasonTextThe explanatory cause for the event.-

Position Events#

TagDescriptionFields
vehicle/position/unknownThe vehicle's current position is not confirmed.reason
vehicle/position/standstillThe vehicle's position is known and stationary.-
vehicle/position/movingThe vehicle has started moving.-

FIELD DEFINITIONS

NameTypeDescriptionExample
reasonTextThe explanatory cause for the event.no_fix

Motion Events#

TagDescriptionFields
vehicle/motion/steadyThe accelerometer readings detect a steady device (there is no movement).-
vehicle/motion/shakingThe accelerometer readings detect a shaking motion.-
vehicle/motion/joltingThe accelerometer readings detected a sudden jolt in the device.-

Geofence Events#

These events are triggered by the geofence_event trigger in the Tracking Manager after first acquiring a GPS signal after startup (entering the on power state). The geofence_slug is a URL-safe version of the geofence's name.

enter|exit gets triggered while driving when the vehicle enters/exits a geofence.

TagDescriptionFields
vehicle/geofence/<geofence_slug>/enterThe vehicle went from being outside a geofence to inside a geofence.fence_id
vehicle/geofence/<geofence_slug>/exitThe vehicle went from being inside a geofence to outside a geofence.fence_id

inside|outside events are triggered once for each geofence when the device wakes up, and is a snapshot of the current state.

TagDescriptionFields
vehicle/geofence/<geofence_slug>/insideThe vehicle is inside a geofence.fence_id
vehicle/geofence/<geofence_slug>/outsideThe vehicle is outside a geofence.fence_id

FIELD DEFINITIONS

NameTypeDescriptionExample
fence_idNumberId of the geofence that triggered the event3306