> 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/user/guide/events-and-notifications/device-connection/device-lost-connection.md). # Device lost connection The **Device lost connection** rule is designed to monitor and notify users when a GPS device loses its connection with the Navixy platform. This loss of connection can occur due to several reasons, such as hardware issues (battery discharge, power disconnection, hardware failure, wiring problems) or communication issues (GSM network problems, poor coverage, insufficient funds, or provider outages). This rule helps users stay informed about the operational status of their tracking devices and enables quick responses to potential issues, such as equipment malfunctions, GSM jamming, or vehicle theft. It also aids in collecting valuable data for optimizing operations, such as identifying areas with poor coverage or detecting faults in the equipment or service provider. {% hint style="info" %} For real-time monitoring of device power status, use the [Device switch ON/OFF](/docs/user/guide/events-and-notifications/device-power/device-switched-onoff.md) self-reporting feature if it's supported by your GPS device. {% endhint %} ## Rule settings ### Offline time more than The **Offline time more than** setting allows users to define a custom timer that starts counting down after the GPS device goes into a red status (indicating loss of connection). The total disconnection period is calculated as follows: * **Default timeout (10 minutes)**: This is the standard period after which a GPS device is considered to have lost connection if no data is received from the device. * **Your custom offline timeout**: The additional time specified by the user in the **Offline time more than** field. For example, if a device loses connection at 10:10 AM, after the default timeout of 10 minutes, it is marked with a red status at 10:20 AM. If the user sets the custom offline timeout to 7 minutes, the notification is triggered at 10:27 AM. For common rule settings, see [Rules and Alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * The **Device lost connection** alert has a 10-second reset timer, which means the alert doesn't trigger more often than once every 10 seconds. If an event occurs while the rule is waiting for the reset, it is omitted by the platform, including in reports. * This rule is processed in the cloud and is not tied to any specific hardware, making it applicable to multiple GPS devices simultaneously. This flexibility allows you to manage several GPS devices within a single rule. * Different device models have varying transport-level timeouts. If you include multiple GPS device models in the same rule, the notification periods may differ based on the device's specific timeout settings. This variation occurs because the notification is triggered by a combination of the GPS device's default timeout and the custom offline timeout specified in the rule configuration. By using this rule, users can ensure they are promptly informed of any disruptions in GPS device connectivity, enabling them to take swift action to address potential issues. --- # 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/user/guide/events-and-notifications/device-connection/device-lost-connection.md?ask=&goal= ``` `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.