> 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-reminder-alarm-rule.md).

# LCT - Reminder Alarm Rule

The Reminder Rule for the LCT device is designed to send email notifications at a specific date and time. This rule helps users stay informed or perform scheduled actions related to the device. The email content can be customized through the Reminder Text field, allowing users to include detailed information or instructions. Additionally, the Reminder Subject can be modified, with the default subject format being:

```
"Reminder from {{device_data.name}}/{{device_data.serial}}"
```

Here, {{device\_data.name}} and {{device\_data.serial}} dynamically insert the device's name and serial number, respectively, for easy identification.

To display event details, use the following template tags:

* {{device\_data.time}} : Displays the event time as hh:mm:ss
* {{device\_data.date}} : Displays the event date as dd/mm/yy
* {{device\_data.datetime}} : Displys the full event date and time as dd/mm/yy - hh:mm:ss
* {{device\_data.name}} :  Dispays the device name
* {{device\_data.serial}} : Displays the device serial number

This rule is ideal for scheduling maintenance, updates, or other time-sensitive actions related to the device.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXe9Fa1CtGSbaYWEm6smTNFWgif5ygQQq0eiDAnzl4Xw0000qyxuG19nrdm_25SW6zNuwg78Ts4wCJ379CarBhMhvvIUCuWjtZ-j12sea0Yooh7OsCTBF5lhOk7FuA2paubyBC6WbQ?key=Kl1KyU1gDzenB_F0xjN17rry" alt=""><figcaption><p>LCT Reminder Rule</p></figcaption></figure>

## Steps to Set Up the Reminder Rule for LCT:

1. **Go to Device:**\
   Navigate to the **device list**, locate the desired LCT device, and open its **dashboard**.
2. **Access Rules Section:**\
   Open the **Rules** section of the device dashboard, click on the **+ icon**, and select the **Reminder Rule**.
3. **Activate Rule:**\
   Toggle the switch to activate the rule.
4. **Insert Rule Name:**\
   Enter a meaningful name for the rule.
5. **Set Date and Time:**\
   Use the dropdown calendar to select the **date** and **time** for the reminder.
6. **Modify Subject (Optional):**\
   Change the subject if needed. The default is: **"Reminder from {{device\_data.name}}/{{device\_data.serial}}"**.
7. **Add Reminder Text:**\
   Input the desired reminder text in the provided field.
8. **Add Email Addresses:**\
   Enter up to **five email addresses** to receive the reminder notification.
9. **Save Configuration:**\
   Click **Save** to apply and activate the reminder rule.

<br>


---

# 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://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-rules/lct-reminder-alarm-rule.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.
