> 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/first-steps/13.-usage-recording.md).

# 13. Usage Recording

This step asks whether the controller may learn how the installation is operated. From that it later suggests scenes and automations.

The step is deliberately kept apart from the next one: the data recorded here stays on the controller and is not sent to nomos system. The next step asks about data that is sent.

* **Screen Display:** One option is offered:
  * **Record how devices are used:** The controller remembers which devices are operated and when. Without this option nothing is recorded and no suggestions can be made.
* **Step:** Enable or disable the checkbox according to the customer's preference. The setting can be changed later under Administration → Advanced.
* **Next Step:** Click "Next".


---

# 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/first-steps/13.-usage-recording.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.