> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/devices-documentation/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/devices-documentation/move-solutions-devices/devices.md).

# Devices

## **Devices and Sensors Overview**

Devices and sensors represent the hardware installed in the field and are capable of connecting to the Internet via a Gateway. Communication between the sensor network and the Gateway occurs through **LoRaWAN**. Devices send data via **Uplink** and optionally receive commands via **Downlink**. Devices can be managed in the **Device Settings** section.

## Sensor Identification

Devices are uniquely identified by their **Device ID (devEUI)** and **Device Type**, 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 **Settings** page.

## Monitoring Types

Move Solutions' devices and sensors are divided into two distinctive monitoring categories, characterized by their sampling properties, the physical parameters they detect, and their mode of operation.

* **Devices for Dynamic Monitoring:** Dynamic devices are designed for detecting data over a specific period of time, such as dynamic changes and structural oscillations. They measure parameters such as **accelerations**, **vibrations**, and other indicators of dynamism within the infrastructure.
* **Devices for Static Monitoring:** Static devices are designed for detecting precise data of static parameters, such as variations and changes in stable conditions. They measure values like **tilt**, **static displacement**, and other static properties essential for analyzing structural conditions. **Communication Nodes** also fall into this category.

## Types of Devices

The use of a variety of sensors provides a detailed and comprehensive view of the structural conditions. The sensors incorporated into the **Move Solutions** system include:

* [Accelerometer](/devices-documentation/move-solutions-devices/devices/accelerometer.md) 
* [Dynamic Displacement Sensor](/devices-documentation/move-solutions-devices/devices/dynamic-displacement-sensor.md)
* [Vibrometer](/devices-documentation/move-solutions-devices/devices/vibrometer.md)
* [Tiltmeter](/devices-documentation/move-solutions-devices/devices/tiltmeter.md)
* [Communication node](/devices-documentation/move-solutions-devices/devices/communication-node.md)
* [Gateway](/devices-documentation/move-solutions-devices/devices/gateway.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://move-solutions.gitbook.io/devices-documentation/move-solutions-devices/devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.