Fermentrack

Fermentrack runs on a Raspberry Pi beside the fermenters, reads every Tilt and iSpindel in range, and can push what it reads to other services on a schedule. Its Brewfather push target takes any URL, and the body it posts is one we read as it stands, so a Fermentrack that already logs to Brewfather can log to Beerwright by pasting our URL over theirs.

Setting it up

1. In Beerwright, open Settings → Fermentation devices, press Add a device, and copy the device URL.
2. In Fermentrack, open Push targets and add a Brewfather target. Paste the device URL into the Brewfather Logging URL field, choose the gravity sensor to push, and pick how often.
3. Save. Fermentrack pushes on the schedule you chose, and the device list in Settings shows when the reading last arrived.

Fermentrack’s Brewfather target is one hydrometer per target, so a Pi reading two Tilts needs two targets. Both can point at the same device URL, or each at its own; the section below says what each choice means.

What it sends

Each push carries the sensor’s name, its gravity as specific gravity, its temperature with the unit stated, and the battery if the sensor reports one. Numbers arrive as numbers. If a BrewPi controller is associated with the sensor, the chamber and room temperatures ride along as auxiliary fields; we keep them with the reading and chart the beer’s own two lines.

Fermentrack has a second, “generic” push format of its own, a nested document listing every sensor and controller at once. We do not read that one, and you do not need it: the Brewfather target does the job with a body we already understand.

Two hydrometers, one URL or two

Point both targets at one device URL and the moment the second sensor’s name is heard, that URL becomes a bridge: each sensor becomes a device of its own in Settings, with its own pin, and readings from a sensor you have not pinned yet are kept until you say which beer it is in. Pinning it attaches what it already sent since that beer started fermenting. The TiltBridge page describes the behavior in full.

Or mint one device URL per target and pin each device in Settings as you would any other. There is no wrong answer; the bridge exists so that one URL is enough, not so that you must use only one.

When nothing arrives

Nothing at all. Push targets in Fermentrack are disabled until you enable them, and each has its own schedule. Check the target’s status on the push-targets page; it records the last error it hit.

A reading arrives, then nothing for a long time. Fermentrack pushes the latest reading it holds, so if the sensor itself has stopped reporting to the Pi, the push carries nothing new and we treat a repeat as a repeat. Check the sensor on Fermentrack’s own dashboard first.

Two sensors on one chart. Both targets are pointed at one URL and the second sensor has not been pinned yet, or was pinned to the wrong beer. Open Settings, find the bridge, and pin each hydrometer to its beer. The readings that landed on the wrong batch can be moved from the batch page.

Related

• Fermentation devices
• Tilt
• iSpindel
• TiltBridge
• Anything that can post JSON