> 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/craftbeerpi.md).

# CraftBeerPi

Community plugins for posting CraftBeerPi fermentation data to Brewfather.

[CraftBeerPi](https://craftbeerpi.gitbook.io/) is an open-source brewing controller software that runs on a Raspberry Pi, providing automated control of mashing, boiling, and fermentation processes.

The plugins listed below are **community-maintained** and are not official Brewfather integrations. They were created by Brewfather users to bridge CraftBeerPi with Brewfather's logging capabilities.

{% hint style="info" %}
These plugins were built for **CraftBeerPi v3**. If you are using CraftBeerPi v4, check the respective GitHub repositories for compatibility notes or look for updated forks.
{% endhint %}

### Available Plugins

Logging to **Custom Stream**: <https://github.com/jnosek/cbpi_Brewfather/>\
Posts fermentation data from CraftBeerPi to Brewfather's [Custom Stream](/integrations/custom-stream.md) endpoint.

For **Tilt Hydrometer** find it here: <https://github.com/mowbraym/brewfather>\
Forwards Tilt Hydrometer readings collected by CraftBeerPi directly to Brewfather.

For **iSpindel** go here: <https://github.com/ZeSlammy/Brewfather_iSpindel> or <https://github.com/netanelbe/Brewfather_iSpindel> or <https://github.com/mowbraym/Brewfather_iSpindel>\
Sends iSpindel data collected by CraftBeerPi to Brewfather. Multiple forks are available with varying feature sets.

## How the Integration Works

CraftBeerPi collects sensor data (temperatures, gravity readings from connected hydrometers, etc.) and these community plugins forward that data to Brewfather. The two main approaches are:

* **Custom Stream** -- The plugin posts fermentation data to Brewfather's [Custom Stream](/integrations/custom-stream.md) endpoint. You enable Custom Stream in **Settings > Power-ups** and use the generated URL in the CraftBeerPi plugin configuration.
* **Device-specific forwarding** -- For Tilt or iSpindel data collected by CraftBeerPi, the plugins forward the readings to the corresponding Brewfather device endpoint. Enable the relevant device integration (Tilt or iSpindel) in **Settings > Power-ups** and use the generated URL or ID.

In all cases, data should not be logged more than once every 15 minutes per device name.

## Related docs

* [Custom Stream](/integrations/custom-stream.md)
* [Devices](/devices.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/craftbeerpi.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.