Missing or incorrect readings

Start by checking the same tracking unit in your provider’s portal. Nomora cannot refresh a device that has stopped reporting or supply a sensor value the provider does not expose.

No tracking data on a booking

1. In Settings → Telematics, check the provider connection and that its integration is enabled.
2. Load the provider’s units and verify the booking vehicle is linked to the correct one.
3. Check the booking’s assigned vehicle and rental dates. An unassigned class booking has no vehicle tracker to report from.
4. Check Telemetry Timezone if the provider report appears shifted by a few hours.

If the account cannot load units, test or reconnect the credential. A working account with no readings for one unit usually needs that unit’s mapping or device reporting checked.

The odometer has not changed

Open the vehicle’s Mileage section and click Sync Mileage. Check that the provider has a usable odometer, not just a route distance or a zero counter.

Automatic sync only moves the stored odometer forward. This protects a dashboard reading you entered from a tracker with an uncalibrated lower counter. A manual Sync Mileage can use a lower tracker reading, except with FleetComplete, which only moves forward in either mode. Compare the reading with the physical dashboard before using sync to correct a difference.

If the provider counter is wrong, correct or calibrate it with the provider. Use Add Reading for a verified manual vehicle reading. For a rental’s recorded pickup or return mileage, correct that rental’s handover reading separately.

The distance looks too large or too small

Check the organization’s distance unit and compare like-for-like values. A tracker value in kilometres and a Nomora value in miles should differ. A trip distance also should not equal the vehicle’s lifetime odometer. Nomora already converts imported kilometre readings; do not convert them a second time.

If multiple tracking providers are linked, confirm which unit each report uses. Correct a wrong vehicle-unit match before recording more rentals.

Fuel is missing or says N/A

Check the provider capability table. Mapon, FleetComplete, and GPS Live do not supply fuel to Nomora’s rental report. Wialon and Linqo require fuel values in the underlying report or trips.

Record the observed fuel or charge level during pickup and return. Those handover readings are separate from the tracker’s fuel consumption report.

Customer location is missing or stale

The customer location alongside remote access is the Wialon unit’s last known position. Check its timestamp rather than assuming it is live. If the tracker has no position or has not reported recently, check power, connectivity, and reporting in Wialon.

If the whole remote-access area is missing, check compatible vehicle setup, permission for this booking, the rental time window, and any required signatures or inspections. A valid customer link alone does not grant location or lock controls.

What to send support

Include the booking or vehicle, provider name, unit identifier, date range, and exact error. For a wrong reading, include the corresponding value and timestamp from the provider portal. Keep API keys and account passwords out of the message.