> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/dashboards/adding-widgets/last-data-widget/pie.md).

# Pie Display

<figure><img src="/files/8EgAsQ3RR439bq8GtyYS" alt="Last Data widget using the Pie display type"><figcaption></figcaption></figure>

The Pie display is a solid filled circle rather than a ring — it fills in like a slice of pie and becomes whole when the reading reaches its maximum, with the value shown beside it. It works on exactly the same idea as the Doughnut; it just looks bolder and more solid.

Reach for Pie when you'd like a stronger splash of color on the dashboard instead of a thin ring.

## When to choose it

* The same range-based readings the Doughnut handles — tank level, battery, humidity — when you prefer a chunkier look.
* A tile you want to stand out on a busy dashboard.
* A board you glance at from across the room, where a solid shape reads more easily.

Doughnut and Pie do the same job — choose whichever simply looks better to you on the dashboard.

## Configure a Pie display

Let's build a real one — a bold tile showing how much water is in the garden rain barrel. A level sensor reports the barrel contents in liters, and the barrel holds 200 liters — so the reading is 0 when the barrel is empty and 200 when it's full. That 0–200 is the scale, and each color band is a slice of it. This is just an example: a Pie works for any reading shown as a share of a range, so only the sensor and the numbers change.

1. Open your dashboard in edit mode and tap **Last data** in the widget picker. The **Datasource** tab opens with nothing added yet.
2. Tap **Add datasource**. A **Datasource 1** block appears.
3. In the block, tap **Choose device** and pick the rain barrel's level sensor.
4. Tap **Add metric**. A metric row appears.
5. In the row, leave **Data type** on **Telemetry**, choose the volume reading under **Device metric**, and choose an **Icon**.

   > **This display needs a number.** The **Device metric** list shows every reading, but a gauge fills against a scale — pick a numeric one here; a text reading shows as 0. (To show text or an on/off value as-is, use the [Value display](/dashboards/adding-widgets/last-data-widget/number.md).) To change a reading's type, use the **Metrics Templates** button on your connection's Connected Devices list — see [Data Templates](/devices/data-templates.md).
6. Tap **Conditions: N** to open the Conditions window. Choose a **Default color** — the color the reading uses whenever none of your bands match the current value — then for each band tap **Add condition** and fill in the row — a **Condition name**, **Data type** set to **Number** (the condition's own Data type, not the metric's), the band's **From** and **To** — the barrel holds 200 liters, so those run from **0** (empty) to **200** (full) — and a **Color**. Then you set the color levels — for example:

   Starting from empty:

   * "Plenty" — **From** 120, **To** 200 — green
   * "Getting low" — **From** 40, **To** 120 — yellow
   * "Almost empty" — **From** 0, **To** 40 — red

   Tap **Save** to close the window.
7. Tap **Next** to move to the **Appearance** tab.
8. Type a **Widget name** — "Rain barrel" — and a **Description** if you want a subtitle.
9. Under **Widget type**, choose **Pie**.
10. In **Value range**, set **Min value** to **0** (an empty barrel) and **Max value** to **200** (its full 200-liter capacity) — the same range your bands use. The slice fills the whole circle at 200 liters.
11. Switch on **Display data legend** if you'd like, then tap **Save**.

Now a solid disc shows the barrel at a glance — full and green after rain, shrinking through yellow to red as you water the garden. The same steps fit any "how full" reading at home; change the sensor, the **Min value**/**Max value**, and the bands to suit.

## Worked examples

**Do the houseplants need water?** A soil-moisture sensor reports a percentage, so the scale is simply **Min value** 0 (bone dry) and **Max value** 100 (soaked), with conditions green From 40 To 80, yellow From 20 To 40, red From 0 To 20. The filled disc makes a thirsty plant impossible to miss.

**A tile you can read from the sofa** On a dashboard you keep on a wall tablet or a TV, a solid Pie reads more clearly from a distance than a thin ring. Use Pie for the readings you want to catch from across the room, and save the Doughnut for closer-up tiles.

## See also

* [Last Data Widget](/dashboards/adding-widgets/last-data-widget.md) — The full widget setup and the other display types
* [Conditions](/dashboards/adding-widgets/conditions.md) — Setting the From/To color rules
* Other display types: [Value](/dashboards/adding-widgets/last-data-widget/number.md) · [Doughnut](/dashboards/adding-widgets/last-data-widget/doughnut.md) · [Gauge](/dashboards/adding-widgets/last-data-widget/gauge.md) · [Tube](/dashboards/adding-widgets/last-data-widget/tube.md) · [Radial gauge](/dashboards/adding-widgets/last-data-widget/radial-gauge.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.chirpwireless.io/dashboards/adding-widgets/last-data-widget/pie.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
