> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/reference/widgets/display/status-lamp.md).

# Status Lamp

LED-style indicator mapping bound values or executor status to colors, as circle or rectangle

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-f0234675f29f4b776e8b117b3c92aa7cb4588fa1%2Fwidget-status-lamp.png?alt=media" alt="Status lamps showing four machine states, and a strip of eight station lamps" width="548"><figcaption></figcaption></figure>

A status lamp shows a state at a glance: running, setup, fault, idle, or whatever states your machines know. You decide which value lights which color. Link it to an executor's status and it tells whether that executor can run. Give it a list of states and the rectangle shape turns it into a strip, one bar per state, so a whole line fits in one row. A click can hand a value back to your logic, for example to open the machine's detail page.

**Good for:** machine and line overviews, connection health, alarm boards.

## Properties

The widget's General tab lists these properties under Receives and Emits. Drop an executor's output, input or trigger onto a row to link it. An example also fills an unlinked widget as demo data in the App Builder.

{% tabs %}
{% tab title="Receives" %}
**`value`** (from an output, `string | Array<string>`): A single state, or an array of those.

<details>

<summary>Example</summary>

```json
"running"
```

</details>

**`color`** (from an output, `string | Array<string>`): The direct color that should be applied to the lamp.

<details>

<summary>Example</summary>

```json
"#19914b"
```

</details>

**`context`** (from an output, `string | number | boolean | object | array | null`): Any context that will be provided back, when clicked.

<details>

<summary>Example</summary>

```json
"Pump A"
```

</details>

**`value`** (from an executor's status, `string`): The linked executor's status drives the lamp state.

<details>

<summary>Example</summary>

```json
"ok"
```

</details>
{% endtab %}

{% tab title="Emits" %}
**`onClick`** (into an input, `string | number | boolean | object | array | null`): Writes the bound context value when the lamp is clicked.
{% endtab %}
{% endtabs %}

## Settings

Double-click the widget in the Page editor to open its settings, grouped in these tabs. Settings marked *set per screen* are pinned by nature: every screen keeps its own value.

<details>

<summary>Look &#x26; feel</summary>

* **Shape**: circle draws round lamps sized to the short side; rectangle splits the long side into rounded bars. Choices: Circle, Rectangle.
* **Status mappings**: Colors by status: a bound value is matched against these entries; no match shows a dim grey lamp.
  * **Value**: Status this entry matches, compared as text; an object is matched by its status field.
  * **Color**: Lamp color for this status; transparent hides the lamp, empty or auto keeps the theme's.
* **Context**: Value sent with the click to the linked input; a bound context replaces it.
* **Spacing**: Gap between the bars in px when several states show in rectangle shape. *Set per screen.*

</details>


---

# 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.heisenware.com/reference/widgets/display/status-lamp.md?ask=<question>&goal=<user_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.
