> 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-configuration/lct-temperature-monitoring-configuration.md).
# LCT- Temperature Monitoring configuration
It involves tracking the temperature of a device. The system continuously measures and records temperature values. If the temperatures exceed or fall below the setted range, the system sends an alarm alert.
Temperature Monitoring configuration
## Steps to Set Up Temperature Monitoring:
1. **Open the Device:**
* Navigate to the device dashboard and select the desired device.
2. **Go to Configuration:**
* Access the Configuration tab to manage the device's settings.
3. **Find the Temperature Monitoring Setting:**
* Locate the Temperature Monitoring option in the configuration list.
4. **Toggle the Switch:**
* Enable temperature monitoring by toggling the switch to the ON position.
5. **Set Temperature Thresholds:**
* Use the cursor to adjust the minimum and maximum temperature values that will trigger events.
6. **Save the Configuration:**
* Click Save to apply the changes and activate temperature monitoring.
---
# 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-configuration/lct-temperature-monitoring-configuration.md?ask=&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.
