> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/dashboards/adding-widgets/control-widget/slider-circular.md).
# Circular Slider
Add a Circular Slider to a Kilo dashboard to set a numeric device value, such as valve position, on a radial dial.
The **Circular** slider sets a **numeric value** on a radial dial — drag around the arc and the value follows. It has the look of an instrument gauge, so it draws the eye to a headline setting.
## When to use it
Reach for the Circular slider when a dial reads better than a bar — a **color temperature**, a **valve position** as a percentage, or any single setting you want to stand out on a control screen. For a compact in-row control use the [Simple Slider](/dashboards/adding-widgets/control-widget/slider-simple.md); for a level-style control use the [Vertical Slider](/dashboards/adding-widgets/control-widget/slider-vertical.md).
## What you need first
* A controllable device with a command on its **Commands & States** tab whose **parameter takes a number** (see [Creating Commands](/devices/commands/creating-commands.md)).
* A **Device metric** that reports the current value, so the dial shows where the setting sits.
## How to set it up
1. Open the dashboard in **edit mode** → **Add widget** → **Control**.
2. **Datasource** tab: choose the **Device** and the **Device metric** for the live value. Click **Next**.
3. **Appearance** tab: enter a **Widget name**, choose **Widget type → Slider**, then set **Slider type → Circular**.
4. Set the **Command**, the **Parameter** it sets, and a starting **Value**.
5. Add **Start and End labels** for the range (e.g. `150` and `500`) with **Display** on, pick a **Slider color**, and toggle **Display name and last update**.
6. Click **Save**.
## What happens when you use it
Dragging around the dial sends the command with the new value as its parameter. The dial position follows the **Device metric**, so it always reflects the value the device reports.
## Common mistakes
* **Confusing it with the Radial Gauge** — the Circular slider *sets* a value (it's a control); the Last Data [Radial Gauge](/dashboards/adding-widgets/last-data-widget/radial-gauge.md) only *displays* one.
* **No numeric parameter** — like every slider, it needs a command parameter it can set to a number; for on/off use a [Switch](/dashboards/adding-widgets/control-widget/switch.md).
## See also
* [Control widget](/dashboards/adding-widgets/control-widget.md) — overview and the other control types
* Other slider layouts: [Simple Slider](/dashboards/adding-widgets/control-widget/slider-simple.md) · [Vertical Slider](/dashboards/adding-widgets/control-widget/slider-vertical.md)
* [Device Commands](/devices/commands.md) — define the command this dial drives
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.kiloiot.io/dashboards/adding-widgets/control-widget/slider-circular.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
