Fuel & alertsFuel events
Fuel events — reading results
Per-sensor statistics, detection configuration, and the events table columns after Generate Fuel Events.
After Generate Fuel Events succeeds, the right-hand Fuel Events Result area lists one section per fuel sensor returned for the vehicle and range.
Per-sensor summary
For each sensor you typically see:
- Sensor name and a count of Events (events emitted for that run).
- Metric cards (labels are uppercase in the UI), for example:
- FUELREADING — count of fuel readings considered.
- MOTION READING — motion readings considered.
- SEGMENTS — segments considered.
- EVENTS EMITTED — number of events emitted.
Exact values come from the API for the selected window.
Configuration (expandable)
Open Configuration to see the detection settings applied for that calculation, for example:
- Min Filling / Min Theft (liters)
- Max Capacity (liters)
- Detection Timeout (minutes)
- Grouping Timeframe (minutes)
- Detect in Motion (speed threshold, km/h)
These explain why events were grouped or split the way they were.
Events table
When the API returns events for a sensor, a table lists one row per event with columns:
| Column | Meaning |
|---|---|
| Type | Event type (for example refuel, theft, drain), shown as a colored badge. |
| Start Time / End Time | Date and time of the event window. |
| Duration | Minutes and seconds. |
| Volume Change | Liters, with a + or - prefix where applicable. |
| Max Speed | Maximum speed during the event (km/h). |
| Confidence | Shown as a percentage (0–100%) derived from the API value. |
If a sensor has no events in the period, the UI states that no events were recorded for that sensor.