> 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-power/external-power-cut.md). # External power cut The **External power cut** rule is designed for wired vehicle GPS devices that depend on the vehicle’s electrical system. This rule is crucial for fleet management, as it monitors the power supply to the GPS device and alerts users when the external power is disconnected. Upon detecting a power cut, the GPS device automatically switches to its internal battery (if available) to maintain functionality and report to the Navixy platform. The platform logs these events and notifies users according to the rule’s settings. ## Rule settings This rule is entirely dependent on the device's capabilities and hardware configuration. There are no specific settings to configure within the rule itself. For common settings, see [Rules and Alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * **Reset timer.** The **External power cut** alert has a 5-minute reset timer, meaning that the alert doesn't trigger more frequently than once every 5 minutes. If an event occurs during the reset period, it is omitted from the platform and isn't included in reports. * **Device-detected event.** This event is triggered directly by the device based on its configuration. Your device and its configuration must support this functionality to use the rule. * **GPS-independent event alert.** The platform registers and displays the event even if it is received in a message without valid coordinates, ensuring that users are informed regardless of the event's location. The Inside/Outside settings for geofences are ignored in such cases, as the platform prioritizes displaying potentially critical events. --- # 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-power/external-power-cut.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.