> 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/locating-an-lm-device-on-the-giot-platform.md).
# Locating an LM Device on the GIoT Platform
The serial number is printed on the tracker. This number is uniquely assigned to each tracker and can be used as the tracker ID for searching in the LM application.
## LM - Read Device Serial Number on Device and Platform
{% hint style="success" %}
**All trackers are uniquely identifiable by their default serial number, which is displayed both on the platform and on the device itself.**
{% endhint %}
1. Enter the Serial Number into the search field and press the Enter key or the icon to the left of the search field.
2. The next dialog will display the found tracker(s).\
To configure an already registered tracker or assign it to a group, you must first locate it in the LVM Dashboard. by Clicking and selecting the desired device.
3. Access the device Dashboard, Configuration, Rules, Alarms, Events, Time-series and Properties
Locate the device on the Platform
---
# 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/locating-an-lm-device-on-the-giot-platform.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.
