gauge-simpleAirlock

Connect a Plaato Airlock to Brewfather using open-plaato-keg instead of the original Plaato app and cloud.

circle-exclamation

Quick guide

  1. Start an open-plaato-keg server and note its local IP address. See the open-plaato-keg setup and deployment docsarrow-up-right and the full steps in 1. Start the open-plaato-keg server.

  2. Connect to the Airlock Wi-Fi network PLAATO-XXXXX, open http://192.168.4.1, and save your Wi-Fi, Auth Token, server host, and port 1234. See the PLAATO Airlock Setup Guidearrow-up-right and the full steps in 2. Connect the Airlock to open-plaato-keg.

  3. In Brewfather, enable Settings > Power-ups > Plaato Airlock and copy the Logging URL. See Settings and the full steps in 3. Enable Plaato Airlock in Brewfather.

  4. In open-plaato-keg, open Configure > Airlock Setup, select the Airlock, paste the Brewfather Logging URL, and save the Brewfather settings. See the PLAATO Airlock Brewfather Integration Guidearrow-up-right and the full steps in 4. Link the server to Brewfather.

  5. Wait for the Airlock to appear on the Devices page, then attach it to your batch from Fermenting > Readings > Devices. See the full steps in 5. Verify the device in Brewfather.

External references

Before you start

  • A working Plaato Airlock

  • A 2.4 GHz Wi-Fi network

  • A device on your local network running open-plaato-keg, such as a Raspberry Pi, Docker host, or home server

  • Access to the Plaato Airlock power-up in Brewfather

  • An active batch in Fermenting when you are ready to attach the device

1. Start the open-plaato-keg server

Set up and start the server by following the upstream project documentation:

Quick example:

After the server starts:

  1. Note the server IP address on your local network.

  2. Make sure the Airlock can reach the server on port 1234.

  3. Open http://<server-ip>:8085 to confirm the web UI is reachable.

2. Connect the Airlock to open-plaato-keg

Follow the upstream PLAATO Airlock Setup Guidearrow-up-right for the original Airlock onboarding flow. The summary below matches that guide.

  1. Power on the Plaato Airlock.

  2. On first boot or after reset, it creates a temporary Wi-Fi network named PLAATO-XXXXX.

  3. Connect your phone, tablet, or computer to that Wi-Fi network.

  4. Ignore any "no internet" warning and stay connected.

  5. Open http://192.168.4.1 in a browser.

  6. Enter the Airlock configuration values:

    • WiFi SSID: your 2.4 GHz home network name

    • WiFi Password: your network password

    • Auth Token: a unique 32-character hexadecimal value

    • Host: the IP address of your open-plaato-keg server

    • Port: 1234, or your configured KEG_LISTENER_PORT

  7. Save the configuration and let the Airlock reboot.

  8. Open http://<server-ip>:8085, go to Configure > Airlock Setup, select the Airlock, and give it a unique name.

  9. Confirm the Airlock appears on the server dashboard and starts reporting data.

circle-info

If you are using more than one Airlock, each device needs its own unique Auth Token and its own descriptive name on the server.

3. Enable Plaato Airlock in Brewfather

This is the Brewfather side of the setup. See Settings for the Power-ups page overview.

  1. In Brewfather, open Settings > Power-ups > Plaato Airlock.

  2. Enable the integration.

  3. Copy the Logging URL shown by Brewfather.

circle-info

The upstream open-plaato-keg guide may refer to Settings > Integrations. In Brewfather docs and current UI, this setup lives under Settings > Power-ups.

Follow the upstream PLAATO Airlock Brewfather Integration Guidearrow-up-right for the server-to-Brewfather forwarding flow. The steps below summarize that process in Brewfather terms.

  1. Open the open-plaato-keg web UI at http://<server-ip>:8085.

  2. Go to Configure > Airlock Setup.

  3. Select the Airlock you want to send to Brewfather.

  4. In the Brewfather section, enter:

    • Brewfather URL: paste the Logging URL from Brewfather

    • Temp Units: match your Brewfather batch temperature unit

    • Starting SG / Specific Gravity: the batch starting gravity or current specific gravity

    • Original Gravity: optional

    • Batch Volume: optional

  5. Save the Brewfather settings.

The server forwards readings to Brewfather at most once every 15 minutes per Airlock.

5. Verify the device in Brewfather

See Devices for how discovered devices appear and how batch attachment works.

  1. Wait up to 15 minutes for the first forwarded reading.

  2. Open the Devices page in Brewfather and confirm the Plaato Airlock appears there.

  3. Open the active batch you want to track.

  4. In the Fermenting tab, open Readings > Devices.

  5. Attach the Plaato Airlock to the batch.

  6. Wait for the next logging interval for readings to appear in the batch.

circle-info

Brewfather ignores device updates that arrive more often than once every 15 minutes per device. The BPM graph may take around one hour to populate because it needs multiple readings.

Data logged

With this setup, Brewfather receives:

  • Temperature

  • BPM

  • Specific gravity

  • Original gravity if you configured it on the server

  • Batch volume if you configured it on the server

Troubleshooting

  • The Airlock does not show PLAATO-XXXXX

    Power-cycle or reset the Airlock, then follow the upstream PLAATO Airlock Setup Guidearrow-up-right again.

  • http://192.168.4.1 does not open

    Confirm your phone or computer is still connected to the Airlock Wi-Fi network, not your normal home network.

  • The Airlock does not appear on the open-plaato-keg server

    Verify the Wi-Fi is 2.4 GHz, the server IP address is correct, and the port matches KEG_LISTENER_PORT.

  • The Airlock appears on the server but not in Brewfather

    Re-copy the Brewfather Logging URL, save the Brewfather section again in open-plaato-keg, then wait for the next 15-minute interval. If needed, recheck the upstream PLAATO Airlock Brewfather Integration Guidearrow-up-right.

  • The device appears in Brewfather but not in the batch

    Attach it from Fermenting > Readings > Devices. Readings are not logged to a batch until the device is attached.

Last updated

Was this helpful?