> For the complete documentation index, see [llms.txt](https://docs.moasure.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moasure.com/en/moasure-one-and-moasure-2-series/settings/device-management/add-device.md).

# Add Device

Add a Moasure device to your account.

You can register multiple Moasure devices to one account and switch between them whenever you measure.

### Before you start

* Make sure **Bluetooth** is enabled
* Ensure the Moasure device has sufficient charge
* Keep the device nearby (within a few metres)
* If prompted, allow the app’s **Bluetooth and Location permissions**

### Add a Moasure device

1. Open **Settings** by tapping the cog icon in the bottom-right corner.
2. Tap **Account & Device Management**.
3. Under **Device Management**, tap **Device**.
4. Tap **Add Device**.
5. Follow the on-screen instructions to pair your device.

You can learn more about pairing in the **Connect Moasure** guide.

### Troubleshooting

* Device not found? Turn Bluetooth off and back on, then try again
* Still unable to pair? Restart your phone/tablet and the Moasure device
* Make sure you’re using the latest app version
* Check the device is not already registered to another account

{% embed url="<https://vimeo.com/1024305336?share=copy#t=0>" %}


---

# 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.moasure.com/en/moasure-one-and-moasure-2-series/settings/device-management/add-device.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.