> 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/functions.md). # Functions Under **Functions** you will find additional capabilities your nomos controller brings with it but does not run on its own. You switch on what you want to use — everything else stays off and consumes no resources. Unlike Skills, functions do not connect devices. They evaluate what is already there. Presence detection, for example, combines components of your choosing into a single statement — is anybody on site — and makes that statement available to automations and scenes. Functions are delivered with the software update. A newly arrived function is marked **NEW** for two weeks, so that you notice it even if you were not watching when the update landed. ## Functions overview * **Name:** The name of the function. Clicking it opens its settings. * **Description:** What the function is for. * **Category:** A rough classification, such as comfort, energy or security. * **Version:** The state of the function as delivered with the package. * **Since:** When this controller first saw the function — as a rule, the update that brought it. * **ON/OFF:** Switches the function on or off. * **Reset:** Resets the function completely (see below). If your licence does not cover a function, it is marked **Not licensed** and cannot be switched on. If a function that is switched on failed to start, or can no longer do its work sensibly, the reason is stated in plain words in its row. ## Settings Every function has a page of its own. You reach it through the name in the overview, or directly from the navigation bar on the left: below **Functions**, the ones that are switched on appear under **Active**, the rest under **Available**. The bar therefore shows at a glance what is running. The page itself carries the same on/off switch at the top, so you do not have to go back to the overview to activate a function you are in the middle of setting up. If the function created devices of its own, they are listed at the end of the page. A click takes you into the device settings, where you name it and assign it to a room. ## Switching on and off **Switching on** starts the function immediately. If it creates devices of its own — presence detection does — they appear under Devices right afterwards and can be used in automations and scenes like any other device. **Switching off** stops the function but leaves its devices and settings in place. Automations and scenes referring to them stay intact; the devices simply report that they are no longer reachable. Switch the function back on and it continues with the same settings. A device belonging to a function cannot be deleted on its own, so it is not offered for deletion in the first place. Remove the function itself instead — see Reset. ## Reset **Reset** goes considerably further than switching off. It deletes: * the devices the function created, * its settings, * its recorded history. The function itself stays installed and can be switched on again at any time — it then starts from scratch. **This cannot be undone.** Before you confirm, you are shown which automations and scenes use this function's devices. Those lose their point of reference and will no longer work as before. Check that list before you proceed. --- # 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/functions.md?ask=&goal= ``` `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.