> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy.md).

# Using Navixy

- [A device is showing as moving on the platform even though it is offline](https://navixy.com/docs/qna/using-navixy/a-device-is-showing-as-moving-on-the-platform-even-though-it-is-offline.md): Device continues showing its last known status until it comes back online and sends updated location information to the platform
- [Teltonika device shows "GPS not updated" status](https://navixy.com/docs/qna/using-navixy/teltonika-device-shows-gps-not-updated-status.md): Device operates in static navigation mode; review the relevant parameters and voltage thresholds to resume GPS position updates
- [Platform shows a full fuel tank when it is not actually full](https://navixy.com/docs/qna/using-navixy/platform-shows-a-full-fuel-tank-when-it-is-not-actually-full.md): Check the fuel sensor connection and calibration table; error codes 65454 or 65455 in raw data indicate a sensor communication failure
- [Device shows "GPS not updated" while it reports every 5 minutes](https://navixy.com/docs/qna/using-navixy/device-shows-gps-not-updated-while-it-reports-every-5-minutes.md): GPS not updated status appears when a device sends heartbeats without coordinates or when a time zone mismatch exists on the platform
- [Difference between fuel level and fuel level 2.0 reports](https://navixy.com/docs/qna/using-navixy/difference-between-fuel-level-and-fuel-level-2.0-reports.md): Fuel Level 2.0 uses machine learning to smooth noisy sensor data but cannot track drains; use Fuel Level for drain detection
- [Is there an anti-jammer device?](https://navixy.com/docs/qna/using-navixy/is-there-an-anti-jammer-device.md): No GPS hardware can block jammers, but LBS positioning provides a location radius to help narrow the area when a device stops transmitting
- [Reducing or increasing LBS radius on the platform](https://navixy.com/docs/qna/using-navixy/reducing-or-increasing-lbs-radius-on-the-platform.md): Adjust the LBS detection radius in Devices and Settings to expand or limit the area used for cell-tower-based location accuracy
- [Scheduling a valid geo link](https://navixy.com/docs/qna/using-navixy/scheduling-a-valid-geo-link.md): Set the validity timeframe in geo link settings to restrict the access window and ensure the link is only accessible during the set period
- [Speed does not match with device status in the point report](https://navixy.com/docs/qna/using-navixy/speed-does-not-match-with-device-status-in-the-point-report.md): Status in the point report reflects trip state based on parking detection settings, not the instantaneous GPS speed at that moment
- [No GSM signal level in device widget](https://navixy.com/docs/qna/using-navixy/no-gsm-signal-level-in-device-widget.md): GSM signal level shows as unknown in the widget when the device data frame contains no signal intensity field for that data packet
- [Raw Data](https://navixy.com/docs/qna/using-navixy/raw-data.md): Run raw data exports to inspect parsed telematics parameters, validate data quality, debug sensor configurations, and build custom reports
- [Exporting tracker raw data to a CSV file](https://navixy.com/docs/qna/using-navixy/raw-data/exporting-tracker-raw-data-to-a-csv-file.md): Export parsed telematics data in CSV format from the Raw data block; select the date range and parameter columns before running the export
- [Including parameters in raw data export](https://navixy.com/docs/qna/using-navixy/raw-data/including-parameters-in-raw-data-export.md): Select any integrated parameters for your GPS tracker model when exporting raw data; the export supports up to 1,000 parameter columns
- [Selecting date range and time zone in raw data export](https://navixy.com/docs/qna/using-navixy/raw-data/selecting-date-range-and-time-zone-in-raw-data-export.md): Filter raw data exports by date range (up to 30 days) and time zone to unify timestamps for downstream analytics and reporting
- [Typical use cases for raw data export](https://navixy.com/docs/qna/using-navixy/raw-data/typical-use-cases-for-raw-data-export.md): Export raw data for analytics pipelines, ML systems, sensor debugging, event verification, and custom report building outside the platform
- [Determining why a tracker stopped transmitting](https://navixy.com/docs/qna/using-navixy/raw-data/determining-why-a-tracker-stopped-transmitting.md): Export 30 days of raw data to review battery voltage and signal strength trends in the period before a device stopped transmitting
- [Why the platform may consider telematics data invalid](https://navixy.com/docs/qna/using-navixy/raw-data/why-the-platform-may-consider-telematics-data-invalid.md): Platform filters data with zero satellites or invalid coordinates (0,0) to prevent inaccurate location display and track quality issues
- [Specifying Teltonika AVL parameters in raw data export](https://navixy.com/docs/qna/using-navixy/raw-data/specifying-teltonika-avl-parameters-in-raw-data-export.md): Specify individual Teltonika AVL parameter IDs, comma-separated lists, or hyphen-delimited ranges in the raw data export filter
- [My device moves along the map without physically moving](https://navixy.com/docs/qna/using-navixy/my-device-moves-along-the-map-without-physically-moving.md): GPS drift causes inaccurate position display; a device may appear to move on the map while physically stationary due to signal fluctuation
- [My device is configured to send sensor data, but it doesn't display](https://navixy.com/docs/qna/using-navixy/my-device-is-configured-to-send-sensor-data-but-it-doesnt-display.md): Create a measurement sensor in Devices and Settings to map the incoming sensor parameter to a named field and enable display in the platform
- [My video device isn't showing the livestream](https://navixy.com/docs/qna/using-navixy/my-video-device-isnt-showing-the-livestream.md): Send configuration commands via Air Console to enable the livestream feature and set the correct streaming server address on the device
- [My device isn't sending data to the platform](https://navixy.com/docs/qna/using-navixy/my-device-isnt-sending-data-to-the-platform.md): Verify that the device is correctly configured using Air Console; for Teltonika, adjust the tracking priority and check the server address
- [Reading data from an Eye Sensor on the platform](https://navixy.com/docs/qna/using-navixy/reading-data-from-an-eye-sensor-on-the-platform.md): Create a measurement sensor and select the AVL input from Eye Sensor to read humidity, temperature, magnetism, or movement speed data
- [Send data from a non-integrated device (Navixy Generic Protocol)](https://navixy.com/docs/qna/using-navixy/send-data-from-a-non-integrated-device-navixy-generic-protocol.md): Convert device data to Navixy JSON format and send it over HTTP/HTTPS using the Navixy Generic Protocol for non-integrated hardware
- [Why does my history show too many stops?](https://navixy.com/docs/qna/using-navixy/why-does-my-history-show-too-many-stops.md): Adjust min\_speed and min\_parking thresholds in Parking Detection to reduce trip fragmentation caused by frequent speed fluctuations
- [Google Maps is not showing in my iOS app](https://navixy.com/docs/qna/using-navixy/google-maps-is-not-showing-in-my-ios-app.md): X-GPS Monitor iOS uses Apple Maps; upgrade X-GPS Mobile to v1.5.0 or later to access Google Maps in the mobile app
- [My vehicle didn't stop, yet the trip is split](https://navixy.com/docs/qna/using-navixy/my-vehicle-didnt-stop-yet-the-trip-is-split.md): Review Parking Detection settings and inspect raw data to find the cause; disable Split by stops in History to view the full track
- [Review all incoming device data at once](https://navixy.com/docs/qna/using-navixy/review-all-incoming-device-data-at-once.md): Open the Raw data export widget or IoT Analyzer to inspect all parsed incoming parameters from a device for up to the last 30 days
- [My Jimi JC tracker is configured but I can't see video playback](https://navixy.com/docs/qna/using-navixy/my-jimi-jc-tracker-is-configured-but-i-cant-see-video-playback.md): Send three SMS commands to the Jimi JC tracker to enable video uploads, retrieve the list of stored recordings, and trigger the upload
- [I can't see video events on my Jimi JC trackers](https://navixy.com/docs/qna/using-navixy/i-cant-see-video-events-on-my-jimi-jc-trackers.md): Send the UPLOADSW command to the device to configure event-based video uploads, then create a corresponding alert rule in the platform
- [Adjust incoming data with IoT Logic](https://navixy.com/docs/qna/using-navixy/adjust-incoming-data-with-iot-logic.md): Use IoT Logic to convert and adjust incoming device data with mathematical functions via the Initiate Attribute node
- [Why does my tracker show LBS location even though I've disabled LBS?](https://navixy.com/docs/qna/using-navixy/why-my-tracker-shows-lbs-location-even-ive-disabled-lbs.md): Old LBS location cached before the setting was disabled; the tracker must send new valid GPS points to replace the stored LBS data
- [Addresses aren't geocoded (shown only as coordinates)](https://navixy.com/docs/qna/using-navixy/addresses-arent-geocoded-shown-only-as-coordinates.md): System reaches geocoding limit (100k–500k daily calls); Basic plan allows 100k, Premium allows 500k geocoding requests per day
- [Maximum device count for a user](https://navixy.com/docs/qna/using-navixy/maximum-device-count-for-a-user.md): The platform supports up to 2 million devices per user account; the objects list shows up to 25,000 at a time due to browser rendering limits
- [Platform not displaying tracks even though trip history exists](https://navixy.com/docs/qna/using-navixy/platform-not-displaying-tracks-even-though-trip-history-exists.md): Disable Split by stops and Smart filter settings in History to remove all filters and display the raw location data from the device
- [Set up a fuel sensor in Navixy](https://navixy.com/docs/qna/using-navixy/set-up-a-fuel-sensor-in-navixy.md): Create a measurement sensor in Devices and Settings, then select fuel as the parameter type, set units, and choose the sensor category
- [Lock down device activation](https://navixy.com/docs/qna/using-navixy/lock-down-device-activation.md): Restrict device activation to specific devices using activation codes, or remove the activation option entirely via Menu Editor for end users
- [Accuracy and freshness of tracker data](https://navixy.com/docs/qna/using-navixy/accuracy-and-freshness-of-tracker-data.md): Tracker accuracy depends on GPS conditions; platform filters unreliable data with too few satellites or interference from jammers
- [How geofence exit events work](https://navixy.com/docs/qna/using-navixy/how-geofence-exit-events-work.md): Platform checks location updates against geofences in real time; a 60-second timer prevents duplicate entry and exit events
- [Not all devices are shown in the objects list](https://navixy.com/docs/qna/using-navixy/not-all-devices-are-shown-in-the-objects-list.md): Check service plan limits on the user account; the most restrictive active plan controls how many trackers appear in the objects list
- [Completed with errors status (Field Service)](https://navixy.com/docs/qna/using-navixy/completed-with-errors-status-field-service.md): Field service task shows this status when the employee visited checkpoints in the wrong sequence, not due to a task completion error
- [Short trips in history and long parking states](https://navixy.com/docs/qna/using-navixy/short-trips-in-history-and-long-parking-states.md): Disable Consider ignition state in Parking Detection to prevent inconsistent ignition signal from fragmenting trips into short segments
- [Measurement sensor alerts trigger later than expected](https://navixy.com/docs/qna/using-navixy/measurement-sensor-alerts-trigger-later-than-expected.md): Switch measurement sensors to virtual sensors to prevent data thinning from delaying alert triggers; thinned data skips intermediate values
- [Set up driver identification](https://navixy.com/docs/qna/using-navixy/set-up-driver-identification.md): Configure the tracker for RFID, iButton, or BLE data; populate the driver list in Field Service and map each driver to a hardware key
- [Supported trackers and dash cameras for video](https://navixy.com/docs/qna/using-navixy/supported-trackers-and-dash-cameras-for-video.md): Native video support for Jimi and Howen devices; MettaX, Streamax, Lightmetrics, and Howen VSS available as integrated video providers
- [Analog-digital input not showing in the Inputs widget](https://navixy.com/docs/qna/using-navixy/analog-digital-input-not-showing-in-the-inputs-widget.md): Manually map analog-digital inputs in Sensors and Settings by creating virtual or measurement sensors for each input parameter
- [Parking detection 0 km/h max idle speed](https://navixy.com/docs/qna/using-navixy/parking-detection-0-km-h-max-idle-speed.md): Set maximum idle speed above 0 km/h in Parking Detection to classify vehicles as parked; a value of 0 disables parking detection entirely
- [Creation and submission date are different for forms](https://navixy.com/docs/qna/using-navixy/creation-and-submission-date-are-different-for-forms.md): Task form creation date precedes submission; check-in form creation date follows submission due to platform database processing logic
- [Idling alert is not triggering](https://navixy.com/docs/qna/using-navixy/idling-alert-is-not-triggering.md): Set the idling duration threshold and verify an ignition input sensor exists; check manufacturer documentation for ignition pin mapping
- [How do I find the port for a given device?](https://navixy.com/docs/qna/using-navixy/how-do-i-find-the-port-for-a-given-device.md): Find device port and server address on navixy.com/devices; EU uses tracker.navixy.com, US uses tracker.us.navixy.com
- [Filter forms based on images](https://navixy.com/docs/qna/using-navixy/filter-forms-based-on-images.md): Image-based form filtering is not supported in Navixy; narrow results using business data fields such as object, date, task, and employee
- [Does Navixy support the JC450?](https://navixy.com/docs/qna/using-navixy/does-navixy-support-the-jc450.md): Navixy supports JC450 via Lightmetrics integration; GPS telematics on Navixy, video events managed in Lightmetrics with limitations
- [Mobile apps availability in Android Auto](https://navixy.com/docs/qna/using-navixy/mobile-apps-availability-in-android-auto.md): X-GPS Mobile, X-GPS Tracker, and X-Monitor do not support Android Auto integration; only direct mobile app use is available for GPS tracking
- [Zero saving value in fuel reports](https://navixy.com/docs/qna/using-navixy/zero-saving-value-in-fuel-reports.md): Fuel saving column compares standard consumption to actual usage; link the tracker to a vehicle and configure the standard consumption value
- [How to match icon colors with group colors](https://navixy.com/docs/qna/using-navixy/how-to-match-icon-colors-with-group-colors.md): Enable the Use group color option in the Change Icon menu to synchronize object icon color with the assigned group color automatically
- [Download DDD files from trackers](https://navixy.com/docs/qna/using-navixy/download-ddd-files-from-trackers.md): Download tachograph DDD files from supported trackers using Navixy Tacho Auth Client; vehicle ignition and active company card are required
- [Troubleshooting trip history issues](https://navixy.com/docs/qna/using-navixy/troubleshooting-trip-history-issues.md): Disable Smart filter and Split by stops in History; use Raw Data export to find data gaps and adjust tracker acquisition settings
- [Incorrect duration due to invalid date or time format (Tasks import)](https://navixy.com/docs/qna/using-navixy/incorrect-duration-due-to-invalid-date-or-time-format-tasks-import.md): Correct the date and time format in the task import file; unsupported symbols or AM/PM notation prevent the platform from parsing duration
- [Subuser vehicle visibility rules](https://navixy.com/docs/qna/using-navixy/subuser-vehicle-visibility-rules.md): Subusers see only tracked vehicles assigned within their account and unassigned vehicles; they do not have access to the full fleet view
- [Peak filtering level in fuel volume report](https://navixy.com/docs/qna/using-navixy/peak-filtering-level-in-fuel-volume-report.md): Adjust peak filtering level in the Fuel volume report to control how aggressively abnormal sensor spikes are smoothed from the chart
- [LBS Signals and false geofence events](https://navixy.com/docs/qna/using-navixy/lbs-signals-and-false-geofence-events.md): Reduce LBS-triggered geofence false positives by increasing the detection radius in device settings; LBS cell tower accuracy is typically 1–2 km
- [Navixy SMS gateway](https://navixy.com/docs/qna/using-navixy/navixy-sms-gateway.md): Use the built-in SMS gateway to send commands and alerts for a limited time and message volume; contact Support to configure a custom gateway
- [Missing Customer ID and Customer Name in RC-Walmart](https://navixy.com/docs/qna/using-navixy/missing-customer-id-and-customer-name-in-rc-walmart.md): Configure the External ID field with the full Recurso Confiable customer format to include Customer ID and Customer Name in RC-Walmart exports
- [How to copy calibration table across multiple devices](https://navixy.com/docs/qna/using-navixy/how-to-copy-calibration-table-across-multiple-devices.md): Copy calibration tables across multiple devices using sensor cloning, CSV import, or the API. Choose the best method for your fleet.
- [Event count inconsistency when selecting multiple devices](https://navixy.com/docs/qna/using-navixy/event-count-inconsistency-when-selecting-multiple-devices.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/qna/using-navixy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.