> For the complete documentation index, see [llms.txt](https://documentation.nomos-system.com/nomos-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.nomos-system.com/nomos-system/integrator-en/devices.md).

# Devices

Click on a device tile in the dashboard or in a room view to open the **device page**. This is where you configure all device-specific settings.

The device page is divided into several tabs:

* **General** – Master data for the device: name, icon, room assignment, type, manufacturer info, and links to automations and scenes.
* **Display** – Controls how the device appears in the nomos app: status display, visible elements, names, order, and screensaver.
* **Quick Config** – Predefined triggers, actions, and synchronizations for common use cases, without having to create a full automation.
* **Data Log** – Historical data for numeric and logical values of the device (e.g. temperature, power), with export functionality.

{% hint style="info" %}
**Note:** Which tabs are shown depends on the device. The Data Log only appears if the device has loggable values. For management devices an additional "Management" tab is available.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.nomos-system.com/nomos-system/integrator-en/devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.