> 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/level-meter-full-device-guide-book/level-meter-greater-than-giots-function/lm-rules.md).

# LM - Rules

LM Rules are pre-configured IoT smart rules specifically designed for the capabilities of the Level Meter (LM) devices. These rules are triggered by device events and can generate alarms or take specific actions based on predefined conditions.

Rules such as Battery Level Alarm, Email Alarms, and Geofence Alarm ensure comprehensive monitoring and alerting for LM devices.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcTsbEA0c_klytSfbevlnTTPqPRbiXPZDhd5cK4CI338TfX5MFqldAowpSVTm1kcJYUHhsk1HhrTog5lD9ROiMg6IZdc6dHh-_mn7Kt1J-c-svDig1TWK31_d_RnqAm3UiefpGIJw?key=6Q0L8l71kf0rf1QHDmG1DmN7" alt=""><figcaption><p>LM  Rules Page- Add Widget</p></figcaption></figure>

## Steps to Access LM Device Rules

1. **Navigate to the Device Dashboard**:
   * Open the Cockpit Menu, go to the Devices section, and locate the LM device by name or serial number.
2. **Open the Device Page**:
   * Select the device to access its detailed page.
3. **Go to the Rules Section**:
   * In the LM device page, click on the Rules tab to view all rule widgets associated with the device.
4. **Add or Modify Rules**:
   * Use the + Add Widget icon to add new rules or modify existing ones.


---

# 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/level-meter-full-device-guide-book/level-meter-greater-than-giots-function/lm-rules.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.