> 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/platform/live-cockpit/widgets/predefined-widgets/comfort.md).

# Comfort

The "Comfort" widget displays the comfort level of a room. The comfort level is calculated from the ratio of temperature and humidity. The room in question must therefore be equipped with sensors that can measure these values.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FjViypABS9qLCVnLiGAd1%2FFrame%201010105793.png?alt=media&amp;token=f376d2da-d412-435c-9679-8f7f390ce78b" alt=""><figcaption></figcaption></figure>

The temperature is displayed on the X-axis. The humidity is displayed on the Y-axis.

If the black indicator is in the green area, the comfort is good.

If the black indicator is in the yellow area, the comfort is still acceptable.

If the black indicator is outside the yellow and green areas, the comfort is poor.

## Configure Widget

{% @supademo/embed url="<https://app.supademo.com/demo/bm5RVse6XnQMdMroJIpU0>" demoId="bm5RVse6XnQMdMroJIpU0" fullWidth="true" %}

1. Make sure you are in the "Dashboard" menu
2. Click on "Add widget"
3. Click on "View"
4. Click on "Comfort"
5. Select the primary asset. This is the asset for which alarms exist. The name of this asset appears in the title bar of the widget.
6. Select the asset with which the temperature is measured
7. Select the asset with which the humidity is measured.
8. Optional: Select how much space your new widget should occupy on the dashboard.
9. Select the primary asset. This is the asset for which alarms exist. The name of this asset appears in the title bar of the widget.


---

# 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/platform/live-cockpit/widgets/predefined-widgets/comfort.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.
