Skip to content

Fermentation devices

Put a wireless hydrometer in the fermenter and we chart gravity and temperature all the way down, on the batch page, next to the recipe that predicted them.

A batch's fermentation panel, with gravity and temperature charted from the first day to the last.A batch's fermentation panel, with gravity and temperature charted from the first day to the last.

Seven ways in are supported by name, and each has its own page:

  • Tilt, through the Tilt app’s Cloud URL or a TILTpi.
  • TiltBridge, through its Generic Target, for Tilts with no phone beside them.
  • RAPT Pill, through the RAPT portal’s custom webhook.
  • iSpindel, through its own HTTP service.
  • GravityMon, the firmware most iSpindel hardware runs now, on its own or through a GravityMon Gateway.
  • BrewPiLess, through its remote logging, with the body it already sends to Brewfather.
  • Fermentrack, through its Brewfather push target, one per hydrometer.

The endpoint is ordinary HTTP, so anything that can post JSON works too, and anything already posting to Brewfather can be pointed at us without changing its body.

Fermentation charts come with the Beerwright plan: you need it to set up a device and to see the chart. If your plan lapses, your device keeps posting and we keep storing every reading, so they’ll all be there when you come back. See Plans.

In Settings → Fermentation devices, press Add a device. A name is optional; it is only there to tell two fermenters apart. We create a device URL and show it with a copy button, and pasting that URL into your device is all the setup there is. Each device page explains where to paste it.

Then give it a little while. A Tilt’s default cadence is fifteen minutes, so “No readings yet” a minute after setup is not a fault. The device list shows when each device last reported, which is the quickest answer to “is it working?”

The Fermentation devices section of Settings, where a device URL is minted and each device shows when it last reported.The Fermentation devices section of Settings, where a device URL is minted and each device shows when it last reported.

Anyone who has the URL can post readings to your account. There is no separate username or key. Posting readings is all they can do with it, though. The URL can’t be used to read a recipe, a batch or anything else. If a URL gets out, press Revoke on the device and set up a new one. The old URL stops working right away.

You can hold up to ten device URLs at once.

By default a reading lands on whichever batch is currently fermenting or conditioning. That works for one fermenter, but with two we can’t tell which beer a reading belongs to. If you’re running two, pin each device to its batch with Readings go to, and its readings will only go to that batch. The same control can point a device at a journal, for a ferment that has no batch behind it.

You can also do it from the batch. While a batch has no readings yet, its fermentation panel has a Choose a device menu listing your devices and where each one is sending readings now. Pick one and it is pinned to that batch.

If a reading arrives when no batch is fermenting, we keep it, so a device that starts posting on brew day doesn’t lose anything. You’ll find those readings under Unclaimed readings in Settings, where you can move them to a batch or delete them.

When a hydrometer comes out of the fermenter, set Readings go to to Nowhere (idle). The device keeps its URL, so there is nothing to set up again, and we don’t store anything it sends while it is idle. Settings still shows when it last reported, so you can tell it is alive. When it goes into the next beer, pick that batch.

A device pinned to a batch goes idle by itself when you move that batch to Packaged. It stays pinned through Conditioning, so a lager keeps its readings while it lagers.

Some setups post more than one hydrometer to the same URL: a TiltBridge hearing every Tilt in the room, or the Tilt app with two Tilts behind one Cloud URL. The first time we hear a second name on a URL, that URL becomes a bridge and each hydrometer becomes a device of its own in Settings, listed under it, with its own pin and its own revoke. From then on, we keep a hydrometer’s readings unassigned until you pin it to a beer. When you do, the readings it has already sent since that beer started fermenting move over with it.

Each batch keeps its most recent 15,000 readings, about five months at a Tilt’s cadence and longer than any fermentation.

A device left following whichever batch is fermenting, or dropped into the next beer before you pinned it there, files readings where you did not mean them. You fix that from the chart on the batch page.

Drag across the chart to zoom into the readings you mean, and double-click to zoom back out. The two buttons under the chart act on whatever is in view. Delete what’s in view removes those readings. Move what’s in view moves them to another batch you pick. Moving deletes nothing, and both charts update right away.

Zoomed in far enough, to ninety readings or fewer, List readings shows them one per row with a checkbox, and the buttons act on the rows you check. That is the way to take out three bad points without touching the hour around them.

Deleting is permanent: readings are not part of the undo history, and we cannot bring them back. Your device keeps recording new ones.

If a device is posting readings, we can also email you when something changes. Settings → Notifications has a switch called Fermentation alerts, off until you turn it on. While it’s on, we check the last few days of every batch receiving readings each night, and send at most two emails about each batch, ever.

Email When
A fermentation has stalled Three days with no real drop in gravity, under 0.002, while still above 1.020.
A fermentation looks finished Two days holding the same gravity, within one point, on a batch below that mark.

We send each one once per batch, instead of every night, because a week of emails about the same stuck fermentation would just get filtered. If a device stops reporting for two days, we assume a dead battery instead of a stalled beer, so a Tilt that stopped reporting doesn’t trigger an alert.

These are the same thresholds the batch page uses, so the email and the chart always match.

The email names the beer and links to its chart. It doesn’t include any gravity readings or anything from your recipe, so open the chart in the app to see the details.

Something wrong on this page? Tell us.