> 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.md). # Level Meter Full Device Guide Book

This guide provides a detailed exploration of the Level Meter (LM) device, highlighting its features, configurations, and practical applications. Designed to deliver precise monitoring of material levels within containers, the LM device combines advanced functionality with user-friendly configurations for efficient asset management. **Key Focus Areas:** * **Comprehensive Device Overview:** Understand the LM device's hardware, measurements, and operational parameters. * **Configuration and Customization:** Step-by-step instructions for setting up thresholds, transmission intervals, and other device-specific settings. * **Adaptive Rules and Alarm Management:** Learn how to integrate adaptive configurations and set alarms to ensure timely responses to critical conditions. * **Application Scenarios:** Explore how the LM device optimizes operations, improves resource allocation, and enhances operational safety. This guide equips you with the knowledge to integrate the Level Meter seamlessly into your operations, ensuring optimal performance and resource efficiency. --- # 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.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.