> For the complete documentation index, see [llms.txt](https://docs.brewfather.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brewfather.app/br/devices.md).

# Devices

This page is only active when at least one device is activated

The devices page lists all your devices and the latest data recieved from them. Activate devices on the [Settings](/br/settings.md) page.

You can also configure and remove devices.

![Total control over all your integrated devices](https://559214094-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LEzhWP2LGeXaKgS2qr4%2F-LUFkIuhBayMx-b07Z2i%2F-LUFkKnl1KqWA1YXjrqe%2Fimage.png?alt=media\&token=85ddcc17-8f37-4473-9305-d815c66b423f)

### Settings

#### Gravity offset

Offset needs to be written as a full number eg -8 instead of -0.008 when you want to adjust for example a gravity reading of 1.052 to 1.044.


---

# 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.brewfather.app/br/devices.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.