Template built by

Telegraf Plugins used:

Included Resources:

  • 1 Bucket: fireboard
  • 1 Telegraf Configuration: Fireboard
  • 1 Dashboard: Fireboard
  • 12 Dashboard Variables:
    • probe1_target
    • probe1_type
    • probe2_target
    • probe2_type
    • probe3_target
    • probe3_type
    • probe4_target
    • probe4_type
    • probe5_target
    • probe5_type
    • probe6_target
    • probe6_type
  • 1 Task:
    Fireboard Stall Check
  • 1 Notification Endpoint:
    Example Endpoint
  • 1 Notification Rule:
    Fireboard Stall Notification
  • 1 Label: Fireboard

Quick Install

If you have your InfluxDB credentials configured in the CLI, you can install this template with:


Fireboard monitoring dashboard

Whether you are cooking on your stove top, oven or outdoor barbeque, understanding cooking temperature will have an impact because different foods cook at different recommended temperatures. You can set the temperature of your oven or bbq to understand the ambient temperature, but you need to also know the temperature of the food that you are cooking to achieve the target temperature to maintain it. A probe can do just that — help you monitor the temperature of the food protein you are cooking and monitor it from an external unit, thus avoiding opening the oven which will impact the desired temperature.

The Fireboard kit comes with an ambient and food probe, a temperature gauge, and a smartphone app that can help you monitor your cooking environment and your food protein. It connects via WiFi and Bluetooth and has a data logging capability to view historical data.

Why monitor your Fireboard?

Fireboard has a smartphone application that collects the probe data and provides graphs and alerts for your bbq. The reason you may want to put this data into an InfluxDB time series database is to provide you with historical data so you can look for trends, find anomalies that may help with future bbqs as well as forecast the remaining cook time once the protein has passed the “stall” time.

How to use Fireboard Monitoring Template

Once your InfluxDB credentials have been properly configured in the CLI, you can install the Fireboard Monitoring Template using the Quick Install command.

Get your Fireboard authentication token
    1. Create a Fireboard account.
    2. POST your login credentials to the Fireboard API to retrieve your Fireboard authentication token.
      curl https://fireboard.io/api/rest-auth/login/
      -X POST
      -H 'Content-Type: application/json'
      -d '{"username":"your-username-here","password":"your-password-here"}'

      Example response

      { "key": "9944bb9966cc22cc9418ad846dd0e4bbdfc6ee4b" }
Configure environment variables

The data for the Fireboard dashboard is populated by the Telegraf configuration included in the template. The Telegraf configuration requires the following environment variables:

  • INFLUX_TOKEN - InfluxDB authentication token with the permissions to read Telegraf configurations and write data to the fireboard bucket. Use your operator token to get started or generate a new token in the Telegraf configuration setup instructions. Find tokens in the InfluxDB UI under Load Data > Tokens.
  • INFLUX_ORG - Name of your InfluxDB organization. If using InfluxDB Cloud, this is the email address you used to create your account. To find your organization name, click your user avatar in the InfluxDB UI. Your organization name appears under your username.
  • INFLUX_HOST - The URL of your InfluxDB instance. See InfluxDB Cloud regions or InfluxDB OSS 2.x URLs.
  • FIREBOARD_TOKEN – Your Fireboard authentication token.

You MUST set these environment variables before running Telegraf, using commands similar to the following:

export INFLUX_TOKEN=YourInfluxDBAuthToken
export INFLUX_ORG=YourInfluxDBOrg
export INFLUX_HOST=http://localhost:8086
export FIREBOARD_TOKEN=YourFireboardAuthToken

Run Telegraf

  1. Download and install Telegraf.
  2. Start Telegraf using the instructions provided in Load Data > Telegraf > Setup Instructions in the InfluxDB UI.


Dashboard cells

The Fireboard dashboard provided by the template includes cells for individual Fireboard probes that display the current temperature and cooking status. Use the dashboard variables specific to each cell to select the following:

  • Probe target: target temperature for the probe (30 - 300)
  • Probe type: Ambient or Food
Fireboard Stall Check task

The Fireboard Stall Check task provided by the template includes a meatProbes variable that lists which Fireboard probe channels should be tracked when identifying stalls. By default, the task assumes Probe 1 is an ambient probe and all other probes should be tracked. To change what channels are tracked, edit the task and customize the variable:

meatProbes = [2,3,4,5,6]

NOTE: The Fireboard Stall Check task is disabled by default.

Notification endpoint

The template provides tasks that trigger notifications. To send notifications, add a notification endpoint.

Key fireboard metrics to monitor

Some of the most important Fireboard metrics that you should proactively monitor include:

  • Probe temperature
  • Probe status

Related Resources

Obtaining the Perfect Smoke by Monitoring Your BBQ with InfluxDB and Telegraf

Scott Anderson demonstrates how he uses a FireBoard wireless thermometer, Telegraf and InfluxDB 2.0 to continuously work towards the perfect smoke.

Enviro+ Raspberry Pi

With Enviro + Air Quality for Raspberry Pi, it's never been easier to build your own air quality monitor from scratch using the existing resources that you're already comfortable with.

Island Pulse Monitoring Template

The Island Pulse Monitoring Template uses energy consumption data to showcase deploying the Modbus Telegraf plugin to collect data stored in InfluxDB. It shows energy consumption compared to previous periods.

Scroll to Top