> 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/integrations/rapt.md). # RAPT Brew Log RAPT device readings in Brewfather using a RAPT Brew data stream. {% hint style="info" %} RAPT's v2.0 update introduced a limit on how many devices can stream data from its platform for free. Check your [RAPT Brew account](https://brew.rapt.io/) for the current limit. {% endhint %} Log fermentation readings from a **RAPT Pill** or **RAPT Temperature Controller** in Brewfather using a [RAPT Brew](https://brew.rapt.io/) data stream. Follow the data stream instructions below to log your device in Brewfather. You do not need to link an API key for device logging. If you previously used the RAPT integration, use the integration ID already shown in your Brewfather settings when configuring a data stream in RAPT Brew. ## Send device readings to Brewfather ### 1. Enable the integration in Brewfather Open **Settings > Power-ups**, enable **RAPT Brew**, and copy the **ID** shown below the instructions. Older Brewfather versions label this power-up **RAPT**. ![RAPT Brew in Brewfather settings, with the new logo, setup instructions and integration ID.](https://771697612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LEzhWP2LGeXaKgS2qr4-887967055%2Fuploads%2Fgit-blob-f06ff87451410f7ca2bace54fa83a02cdefd79ca%2Frapt-brew-brewfather-settings.jpg?alt=media) The screenshot shows an example ID from a test account. Copy the ID from your own Brewfather account. ### 2. Create a data stream in RAPT Brew Open [RAPT Brew](https://brew.rapt.io/) and go to **Manage Account > My Integrations**. Under **RAPT Brew Data Stream**, click **Create Stream** and select **Brewfather**. ![Create Stream in the RAPT Brew Data Stream section.](https://771697612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LEzhWP2LGeXaKgS2qr4-887967055%2Fuploads%2Fgit-blob-6f2caf3333c67ade73cc30bde12ae2ed2499264d%2Frapt-brew-create-stream.png?alt=media) If the wizard offers to link your Brewfather account, you can skip that optional step when setting up device logging. ### 3. Enter the integration ID Enter a **Name** for the stream and paste the ID from Brewfather into **Integration ID**. Click **Next**. ![Stream details with Name and Integration ID fields.](https://771697612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LEzhWP2LGeXaKgS2qr4-887967055%2Fuploads%2Fgit-blob-68a58ec1ac83650191fb837a28177dc0493db1e8%2Frapt-brew-stream-details.png?alt=media) The integration ID is separate from your Brewfather User ID and API key. ### 4. Select your device Select the **RAPT Pill** or **RAPT Temperature Controller** whose readings you want to log, then save the stream. Create a separate stream for each device you want to use with Brewfather. Use a logging interval of **at least 15 minutes**, in line with Brewfather's device logging guidelines. ### 5. Check the readings and attach the device to a batch Open the stream in RAPT Brew and use **Send a test**, or wait for the device's next scheduled reading. ![Send a test in RAPT Brew, showing a delivered response using sample data.](https://771697612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LEzhWP2LGeXaKgS2qr4-887967055%2Fuploads%2Fgit-blob-68887d50c5f1061dc59d649ca5a7f6ab2f0cd3e9%2Frapt-brew-test-stream.png?alt=media) Check the delivery details and open **Devices** in Brewfather to confirm that your device appears with the expected readings. If the test reports that it sent sample data, wait for a real device reading before attaching it to your batch. In your Brewfather batch, open **Fermentation > Devices** and attach the device. Subsequent readings can then be logged to that batch. {% hint style="info" %} A successful HTTP delivery alone does not confirm that a reading was added to a batch. The device must be attached to the batch, and readings sent too frequently may be ignored. Confirm the readings in Brewfather. {% endhint %} ## Supported readings and settings Available readings depend on the device and the data sent by RAPT Brew: | Field | Description | | ---------------------- | --------------------------------------------- | | **Gravity** | Specific gravity from a hydrometer. | | **Temperature** | Current temperature. | | **Target Temperature** | Controller target temperature, when supplied. | | **Battery** | Battery level, when supplied. | | **RSSI** | Wi-Fi signal strength, when supplied. | Click the device name under **Fermentation > Devices** in your batch to configure **Gravity Offset** or **Temp Offset** where applicable. See [Devices](/devices.md) for details. The **(configure webhook)** link in Brewfather's Power-ups settings enables optional forwarding from Brewfather to another service. It is not needed to receive readings from RAPT Brew. ## Troubleshooting * **The device does not appear in Brewfather:** confirm that the RAPT Brew power-up is enabled, the stream uses the integration ID from that same Brewfather account, and the device has sent a reading. Check the stream's delivery details in RAPT Brew. * **The device appears, but the batch has no readings:** attach it under **Fermentation > Devices** in the batch, then wait for the next reading. Allow at least 15 minutes between readings. * **A test reports success, but values do not update:** check whether RAPT Brew sent sample data and inspect the delivery response for an error. Allow at least 15 minutes before testing again, and confirm the latest real reading in Brewfather. RAPT manages device connectivity and stream settings within RAPT Brew. For help with those features, contact RAPT support. For help with readings received by Brewfather or attaching a device to a batch, contact [Brewfather support](/contact.md). ## Related docs * [Devices](/devices.md) * [Settings](/settings.md) * [API](/api.md) * [Webhook forwarding](/integrations/webhook.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 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/integrations/rapt.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.