> 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/device-switched-onoff.md).

# Device switched ON/OFF

The **Device switched ON/OFF** rule allows users to monitor when a GPS device is powered on or off. This rule is particularly helpful for managers who need to ensure that employees are using GPS devices according to prescribed policies during work hours. It provides valuable insights into device usage patterns, helping to prevent device misuse and ensuring that the devices are functioning properly.

{% hint style="danger" %}
This rule applies only to devices that have the capability to report their power status. In other words, the GPS device must be able to send notifications to the platform when it is powered on or off. If a device lacks this functionality, the rule cannot be applied, as the Navixy platform would not receive the necessary data to trigger notifications, but you can still use the device independent [Device lost connection](/docs/user/guide/events-and-notifications/device-connection/device-lost-connection.md) rule.
{% endhint %}

## Rule settings

### Tracker switched ON

The **Tracker switched ON** rule triggers a notification when a GPS device is powered on, provided the device has the necessary reporting functionality.

**Key Points:**

* **Purpose:** Monitors when a GPS device is powered on, helping you keep track of when devices return to operation.
* **Reset Timer:** The **Tracker switched ON** alert includes a 60-second reset timer, which prevents multiple alerts from being sent within a single minute, reducing unnecessary notifications.
* **Configuration:** The rule requires minimal setup and supports multiple GPS devices as long as they have the capability to report power-on events.

### Tracker switched ON/OFF

The **Tracker switched OFF** rule triggers a notification when a GPS device is powered off or loses connection, provided the device can report this event and triggers again when back on.

**Key Points:**

* **Purpose:** Notifies you when a GPS device is turned off or loses its connection, allowing you to respond to potential issues quickly.
* **Reset Timer:** This alert includes a 10-second reset timer, ensuring that alerts aren't triggered more frequently than once every 10 seconds, preventing excessive notifications.
* **Configuration:** Similar to the **Tracker switched ON** rule, this rule also requires minimal configuration and can be applied to multiple GPS devices that support power-off event reporting.

For common settings, see [Rules and Alerts](/docs/user/guide/events-and-notifications.md).

## System operation details

* The **Tracker switched ON/OFF** rule operates based on the hardware events generated by the GPS device when it is turned on or off. These events are transmitted to the platform and processed for notification.
* The rule is flexible and can be applied to multiple GPS devices simultaneously, provided they support the ON/OFF event feature.
* If the platform identifies a hardware event of this type without valid coordinates, the event is still counted as valid and displayed, ensuring that no crucial events are missed.
* The system allows you to track these events regardless of whether they occur inside or outside defined geofences, as the geofence logic is bypassed for these specific events to ensure comprehensive monitoring.

This rule is instrumental in maintaining the operational integrity of your fleet, ensuring that all GPS devices are functioning as expected, and enabling quick responses to any unexpected changes in GPS device status.


---

# 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/device-switched-onoff.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.
