> 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/obdii-device-plugunplug.md). # OBDII device plug/unplug The **OBDII Device Plug / Unplug** rule is designed to provide immediate alerts whenever an OBDII GPS device is connected or disconnected from the vehicle’s OBDII port. This rule ensures that users can take prompt action to maintain continuous tracking and device functionality. For instance, when the GPS device is unplugged, it switches to its internal battery, which has a limited lifespan. Immediate notifications upon disconnection allow users to respond quickly, ensuring uninterrupted tracking and data transmission. ## 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 **OBDII Device Plug/Unplug** alert has a 5-minute reset timer, meaning the alert doesn't trigger more frequently than once every 5 minutes. If the event occurs while the rule is in the reset period, it is omitted by the Navixy platform, including in reports. * **Multiple devices.** **Multiple devices:** Users can select multiple GPS devices to monitor under this rule. The only requirement is that the selected devices must support OBDII port plug / unplug events. This flexibility allows users to monitor this event type across various vehicles or devices conveniently. * **GPS-independent event alert.** The system processes these events regardless of whether GPS data is available. The event is still logged and displayed, even if it occurs outside defined geofences. --- # 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/obdii-device-plugunplug.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.