> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-rules/lct-threshold-detection-rule.md).

# LCT - Threshold Detection Rule

The Threshold Detection Rule for LCT devices monitors specific parameters and triggers an alarm when predefined threshold values are exceeded. This ensures real-time alerts for deviations, allowing for quick responses to maintain operational integrity and device performance.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXe9Iegzu7GdBIeAa-s5KxKH53jMSZB0r-GthB0hZcpkMmJY7rAdHD_ZZV7p0TuoqZETyLgrOJ2xxlLRnq2KPDi7iW2-Y2A5frFBbv2XRYQUF0HundRKY8A5WeE_tz83NgzVsNkxjg?key=Kl1KyU1gDzenB_F0xjN17rry" alt=""><figcaption><p>LCT Thereshold Detection Rule</p></figcaption></figure>

## Steps to Set Up Threshold Detection Rule for LCT:

1. **Access the Rule Page:**
   * Navigate to the **device list**, locate the desired LCT device, and open its **dashboard**.
   * Go to the **Rules** section, click on the **+** icon, and select the **Threshold Detection Rule**.
2. **Activate the Rule:**
   * Toggle the switch at the top to enable the Threshold Detection Rule.
3. **Insert Name:**
   * Enter a meaningful name to identify the rule.
4. **Set Alarm Level:**
   * From the dropdown menu, select the alarm level:
     * Critical
     * Major
     * Minor
     * Warning
5. **Select Parameter:**
   * Choose a parameter from the following list:
     * **2G Failed Connections:** Number of failed 2G connection attempts.
     * **2G On Time - Average:** Average time the device remains connected via 2G.
     * **2G Sliding Average Connection Establishment Time:** Average time to establish a 2G connection over a sliding window.
     * **2G Successful Connections:** Count of successful 2G connections.
     * **Battery - Remaining Capacity (mAh):** Remaining battery capacity in milliampere hours.
     * **Battery - Voltage (mV):** Current battery voltage in millivolts.
     * **Communication Sequence Tries:** Number of attempts for successful communication.
     * **ESP On Time - Average:** Average time ESP module is active.
     * **GPS On Time - Average:** Average time GPS module is active.
     * **LTE-M Failed Connections:** Number of failed LTE-M connection attempts.
     * **LTE-M On Time - Average:** Average time the device remains connected via LTE-M.
     * **LTE-M Sliding Average Connection Establishment Time:** Average time to establish an LTE-M connection over a sliding window.
     * **LTE-M Successful Connections:** Count of successful LTE-M connections.
     * **Modem On Time - Average:** Average time the modem remains active.
     * **NB-IoT Failed Connections:** Number of failed NB-IoT connection attempts.
     * **NB-IoT On Time - Average:** Average time the device remains connected via NB-IoT.
     * **NB-IoT Sliding Average Connection Establishment Time:** Average time to establish an NB-IoT connection over a sliding window.
     * **NB-IoT Successful Connections:** Count of successful NB-IoT connections.
     * **Temperature - Current:** Current temperature readings.
6. **Select Operator:**
   * Choose the operator for threshold comparison:
     * Greater
     * Equal
     * Less
7. **Set Alarm Trigger Threshold:**
   * Enter the numeric threshold value. The rule will trigger when the parameter exceeds, matches, or falls below this value, depending on the operator selected.
8. **Configure Notification:**
   * **Email:** Input up to 5 recipient email addresses for alarm notifications.
   * **None:** Select this option to generate and display the alarm on the platform without sending notifications.
9. **Click Save:**
   * Save the configuration to apply the Threshold Detection Rule.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-rules/lct-threshold-detection-rule.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.