> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets/vordefinierte-widgets/stockwerk.md).

# Floor

The "Floor" widget shows an overview of a floor with a selection of assets located on the floor.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/5gopIxP1WaRudgpedtk9/233C9D3C-836E-4C2E-9C86-214839137839.png" alt=""><figcaption><p>The "Floor" widget with 4 connected assets.<br>The connected assets are displayed as green dots at the bottom right.</p></figcaption></figure></div>

{% hint style="warning" %}
**Warning!**\
The "Floor" widget is designed for use with contact sensors or with assets that send values between 0 and 1!

If other assets are linked to the widget, errors may occur.

If you want to display other assets on a floor widget, please create a [-> Custom Widget](/collection/english-v14/documentation/widgets/benutzerdefinierte-widgets/module/custom-stockwerk.md)
{% endhint %}

## Configure widget

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/dsg7eachVnVF44z8n9pi/Stockwerk.png" alt=""><figcaption></figcaption></figure>

1. Make sure you are in the “Dashboard” menu
2. Click on “Add widget”
3. Click on “View”
4. Click on “Floor”
5. Select the primary asset **\[A]**. The name of this asset will appear in the title bar **\[I]** of the widget
6. Optional: Choose how much space your new widget should take up on the dashboard **\[**&#x42;**]**
7. Select the floor to be displayed in the widget **\[C]**
8. Select the asset to be displayed in the widget **\[E]**

   ◈ Click on **\[D]** <\<Add current POIs/polygons>> to add all assets placed on the floor. [-> Place assets on a floor](/collection/english-v14/documentation/karte-und-stockwerk/stockwerk/assets-auf-einem-stockwerk-platzieren.md)
9. Click on “Add widget” **\[H]**

In the **Smart View** you have the option to switch the display type between **Simple** and **Status** to switch.

* **Simple**: In this view, the positions of the assets and sensors on the floor are displayed simply, without additional status information.
* **Status**: In this view, you can also see the current **Status** status of the assets and sensors, such as occupancies, warnings, or other status information.

This switch between views helps optimize the overview depending on the use case.

<div align="left"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/nqjYkjM0bKxqHYoD81HF/image.png" alt="" width="375"><figcaption></figcaption></figure></div>

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/druv16pbYO48ViyRdxj8/Stockwerk%20(2).png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To make alarms visible in the floor widget, the alarms switch must be enabled in the placed point or polygon [-> Place assets on a floor](/collection/english-v14/documentation/karte-und-stockwerk/stockwerk/assets-auf-einem-stockwerk-platzieren.md#assets-auf-einem-stockwerk-platzieren)
{% endhint %}

***

## Using the widget

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/eDUT4B1oLPmJhIHyEeMU/58CE095A-5AD3-4648-BDBD-2AAC8F7E9E9F.png" alt=""><figcaption></figcaption></figure></div>

<table><thead><tr><th width="142.33333333333331"></th><th width="162"></th><th></th></tr></thead><tbody><tr><td><strong>[I]</strong></td><td>Title bar</td><td>The title of the widget. Can be selected during configuration of the widget under <strong>[A]</strong> selected.</td></tr><tr><td><strong>[J]</strong></td><td>Icon</td><td>Widget icon</td></tr><tr><td><strong>[K]</strong></td><td>Yellow-marked asset</td><td>Symbolizes an occupied asset or an asset that sends the value "1".</td></tr><tr><td><strong>[L]</strong></td><td>Green-marked asset</td><td>Symbolizes a free asset or an asset that sends the value "0".</td></tr><tr><td><strong>[M]</strong></td><td>More options</td><td>See <a href="/collection/english-v14/documentation/widgets/widgets-bedienen.md#uber-widgets-navigieren">-> Navigate through widgets</a></td></tr><tr><td><strong>[N]</strong></td><td>Zoom in</td><td>Enlarge image</td></tr><tr><td><strong>[I]</strong></td><td>Zoom out</td><td>Reduce image</td></tr><tr><td><strong>[I]</strong></td><td>Black-marked asset</td><td>Invalid asset. This asset sends an unsupported value.<br>Create a <a href="/collection/english-v14/documentation/widgets/benutzerdefinierte-widgets.md">-> Custom Widget</a>, to display this asset.</td></tr></tbody></table>

## Asset placement

The placement of the individual assets can be adjusted in the properties of each asset.

Learn more about [-> Place assets](/collection/english-v14/documentation/assets/assets-auf-einer-karte-platzieren.md)

## Adjust floor image

The widget displays the floor with the image stored in the corresponding floor asset.

How to assign an image to a floor or change an existing image can be found under [-> Create floor](/collection/english-v14/documentation/karte-und-stockwerk/stockwerk/ein-stockwerk-erstellen.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets/vordefinierte-widgets/stockwerk.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.