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

# iSpindel

Set up and configure your iSpindel to log gravity and temperature to Brewfather.

Go into the settings page in [Brewfather app](https://web.brewfather.app/), enable iSpindel. You will then get a **Server Address** and **Server URL** that you need to copy into the iSpindel configuration page.

Set your iSpindel in configuration mode, you can then access your iSpindel by Wi-Fi.

In the iSpindel configuration page enter any **name** you want, set **Service Type**: **HTTP**, **Port**: **80**, **Update interval**: **900**, copy the Server Address and Server URL from the Brewfather settings. (If the port/server address fields do not show, try this: hit the HTTP button twice.)

Make sure your polynomial contains your fully calibrated formula. And make sure your Wi-Fi settings are correct. Click Save.

Your iSpindel should then log every 15 minutes.

After the iSpindel has done its first logging to Brewfather, it will appear in the device list located in your Batch > Fermentation > Readings > **Devices**. Click on the Devices button and attach your iSpindel to the batch. The next time your iSpindel logs, it will show up in your batch!

**Never log more than once every 15 minutes**, requests logged more often than that will be ignored. It is **very important that your update interval is 900 or higher**, otherwise your logging will be ignored.

## Gravity units

Brewfather can read iSpindel gravity as either **Plato** or **SG**. Plato is the default: Brewfather converts the reported Plato value to SG for display and logging. If your iSpindel formula outputs SG directly, wait until the device has sent its first reading, open the batch's **Fermentation > Readings > Devices** list, and use the iSpindel **Plato** / **SG** gravity-unit button to switch that device to **SG**.

The old **\[SG]** name suffix is still supported as a legacy fallback, but the device-list toggle is the preferred way to correct the unit because it does not require renaming or reconfiguring the iSpindel. A saved device setting overrides the name suffix.

{% hint style="danger" %}
If you get no gravity reported: Check that the formula is not too long. There's a max character length. Instead of "tilt\*tilt*\**tilt" put \*tilt^3" etc.

If it still fails: **Upgrade to the latest iSpindel firmware** or try to use the second degree polynomial formula for your iSpindel
{% endhint %}

### Multiple devices

Having multiple iSpindels logging to Brewfather is simple, just set them all up logging to the same URL, but make sure they have unique names in the iSpindel configuration.

## Related docs

* [iSpindel Calibration](/integrations/ispindel/calibration.md)
* [Devices](/devices.md)
* [Settings](/settings.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/ispindel.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.