> For the complete documentation index, see [llms.txt](https://wiki.inels.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.inels.com/inels-home/inels-wireless/devices/inels-wireless-heating-temperature-control/thermostats/rftc-3/automations-page.md).
# Automations page
**Devices** In the **"Devices"** section, RF devices are added that are then used in rules. These devices serve as input or output points for various automated actions. Adding and managing devices in this section allows users to efficiently create and manage automations in their environment.
 
***
**Rules** The **"Rules"** section provides a classic rule engine where users can define conditions and actions based on different inputs. These inputs may include controllers, relay states, motion detectors, or various statuses such as room occupancy, **MUR** (Make Up Room), **DND** (Do Not Disturb), and others. With this rule engine, users can create complex automation scenarios that respond to events and states in the environment and perform appropriate actions based on defined rules.
---
# 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://wiki.inels.com/inels-home/inels-wireless/devices/inels-wireless-heating-temperature-control/thermostats/rftc-3/automations-page.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.
