> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/references/devices.md). # Devices ## Devices Devices and sensors (a "thing") represent deployed hardware in the field capable of connecting to the internet via Gateway. Devices send data via **Uplinks** and optionally receive commands via **Downlinks**. ## **Sensor Identification** Devices are uniquely identified by the **Device ID** (**devEUI**), **device type**, and device version —parameters that cannot be modified by the user as they are provided by the system. Typically, a **Custom Name** is associated with the Device ID, which can be set by the user in the [Device Settings](/untitled/mymove-manual/settings/device-settings.md) page.

Data Explorer - Device info

## **Monitoring Types** Move Solutions devices and sensors are categorized into two distinct monitoring types based on their sampling properties, the physical parameters they measure, and their mode of operation. 1. **Dynamic Monitoring Devices**: These devices are designed to detect data over specific time intervals, such as dynamic variations and structural oscillations. They measure parameters like accelerations, vibrations, and other indicators of dynamic behavior within the infrastructure. 2. **Static Monitoring Devices**: These devices are intended for detecting static parameter data, such as variations and changes in stable conditions. They measure quantities such as tilt, static displacement, and other fundamental static properties essential for structural condition analysis. Communication Nodes also fall into this category. ## Move Solutions device types The use of a variety of sensors provides a detailed and comprehensive view of structural conditions. The sensors integrated into the Move Solutions system include: * ​[Accelerometer](https://move-solutions.gitbook.io/devices-documentation/devices/accelerometer) * ​[Vibrometer](https://move-solutions.gitbook.io/devices-documentation/devices/vibrometer)​ * ​[Dynamic Displacement Sensor](https://move-solutions.gitbook.io/devices-documentation/devices/dynamic-displacement-sensor)​ * ​[Tiltmeter](https://move-solutions.gitbook.io/devices-documentation/devices/tiltmeter)​ * ​[Communication Node](https://move-solutions.gitbook.io/devices-documentation/devices/communication-node)​ * ​[Gateway](https://move-solutions.gitbook.io/devices-documentation/devices/gateway)​ --- # 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://move-solutions.gitbook.io/untitled/references/devices.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.