Known issues & legacy fields - Telemax Docs

This page documents known quirks in the Telemax API response format. These are not bugs — do not “fix” them on the client side.

Units reference

Fields where the unit is not obvious from the field name:

Field	Unit	Notes
`Speed`	km/h
`Odometer`	km
`Voltage`	V (volts)	Vehicle battery voltage
`FuelLevel`	% (0–100)	Integer percentage
`FuelVolume`	litres (float)	Nullable — `null` for vehicles without a volumetric sensor. V2 only.
`DrivingTime`	seconds	Time within the current trip
`IgnitionTime`	seconds	Trip duration since ignition on
`EngineHours`	hours (decimal)	e.g. `150.75` = 150 h 45 min. This is a plain number, not an ISO 8601 duration string.
`Fatigue`	ISO 8601 duration	e.g. `"PT2H30M"` = 2 hours 30 minutes
`distance` (TripDto)	metres	Trip distance. Note: `Odometer` uses km — these are different units.
`distance` / `realDistance` (GetNearest)	metres	Distance from the query point
`radius` (GetNearest param)	metres	e.g. `5000` = 5 km radius
`Lat` / `Lng`	WGS84 decimal degrees
`Course` / `Direction`	degrees	N = 0°, E = 90°, S = 180°, W = 270°
`secondsAgo`	seconds

Synthetic IDs

The Id field on position, point, and trip objects is a synthetic identifier — it is not a database primary key and will change if the underlying data changes.

PositionDto.Id — computed from UtcTime and DeviceId. Two requests for the same vehicle at different times return different Id values.
PointDto.Id — assigned externally, not from a persistent store.
TripDto.Id — synthetic trip identifier.

Do not persist or compare these IDs across sessions.

Timestamp format

All timestamps serialise as: 2025-05-01T14:32:00 (no fractional seconds, no Z suffix).

Field suffix	Timezone
`UtcTime`, `StartMovingTime`, `LastMovementTime`, `startedTime`, `endTime`	UTC (despite no `Z`)
`UserTime`, `StartMovingTimeUser`, `LastMovementTimeUser`	User’s configured timezone (offset not included in the string)
`*Formated` fields	User’s configured date-time format string (e.g. `"15/01/2024 12:30:00"`)