> 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-simple.md).
# Simple Slider
Add a Simple Slider control to a Kilo IoT dashboard — a horizontal slider that sets a device value across a range.
The **Simple** slider is a horizontal track you drag to set a **numeric value**. It's the most compact of the three slider layouts and fits neatly into a row of dashboard tiles.
## When to use it
Use a Simple slider for any value an operator dials up or down where a horizontal control reads naturally: a **motor or fan speed**, a **dimming level**, or a **target setpoint**. If you want a level-style or instrument-style look instead, see the [Vertical Slider](/dashboards/adding-widgets/control-widget/slider-vertical.md) or [Circular Slider](/dashboards/adding-widgets/control-widget/slider-circular.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 slider 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 → Simple**.
4. Set the **Command** the slider drives, the **Parameter** it sets, and a starting **Value**.
5. Add **Start and End labels** for the range (for example `150` and `500`) and toggle **Display** to show them; pick a **Slider color** and toggle **Display name and last update**.
6. Click **Save**.
## What happens when you use it
Dragging the slider sends the chosen command with the new value as its parameter, through the device's command pipeline. The handle follows the **Device metric**, so it reflects the value the device actually reports.
## Common mistakes
* **Binding a command without a numeric parameter** — a slider needs a parameter it can set to a number; a plain on/off command belongs on a [Switch](/dashboards/adding-widgets/control-widget/switch.md).
* **Range that doesn't match the device** — set Start/End to the parameter's real minimum and maximum so the full travel maps to valid values.
## See also
* [Control widget](/dashboards/adding-widgets/control-widget.md) — overview and the other control types
* Other slider layouts: [Circular Slider](/dashboards/adding-widgets/control-widget/slider-circular.md) · [Vertical Slider](/dashboards/adding-widgets/control-widget/slider-vertical.md)
* [Device Commands](/devices/commands.md) — define the command this slider 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-simple.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.
