> 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/rftc-3-mqtt-payload-description-hotel-room.md).

# RFTC-3 MQTT Payload Description – Hotel Room

## **MQTT Payload Description – RFTC3**

This manual describes how to interact with the RFTC3 (Room Fan Coil Thermostat Controller) via MQTT using the iNELS system.

### **MQTT Topics Overview**

MQTT topics are categorized into three main types:

#### 1. **Connected**

Indicates the **online/offline status** of the gateway (GW) or connected devices.

**Topic format:**

```
inels/connected/<MAC_ADDRESS>/<DEVICE_TYPE>
```

**Example:**

```
inels/connected/2C6A6F105BB2/gw
```

***

#### 2. **Status**

Displays the **current state** of the gateway or RFTC3 device, including parameters such as temperature, occupancy, fan state, etc.

**Topic format:**

```
inels/status/<MAC_ADDRESS>/<DEVICE_TYPE>
```

**Example:**

```
inels/status/2C6A6F105BB2/RFTC
```

**Typical status payload:**

SetPoint : Comfort, Standby, Economy, BuildProtection\
CurrentTemp : "24.01",\
FanState : "AUTO",\
Economy : "0.00",\
RoomOccu : "0.00",\
Window : "0.00",\
MUR : "0.00",\
DND : "1.00",\
AktSetTemp : "28.00",\
Butler : "0.00"

#### 3. **Set**

Used to **send control commands** to the device.

**Topic format:**

```
inels/set/<MAC_ADDRESS>/RFTC/<PARAMETER>
```

**All payloads must be sent as strings.**

***

### **MQTT Control Payloads for RFTC3**

Below are the supported control topics and string payloads.

***

#### **SetPoint – Comfort Mode**

**Topic:**

```
inels/set/<MAC>/RFTC/SetPoint/Comfort
```

**Payload (string):**

* `"25"` → Sets Comfort temperature to 25°C

#### **SetPoint – Standby Mode**

**Topic:**

```
inels/set/<MAC>/RFTC/SetPoint/Standby
```

**Payload (string):**

* `"20"` → Sets Standby temperature to 20°C

#### **SetPoint – Economy Mode**

**Topic:**

```
inels/set/<MAC>/RFTC/SetPoint/Economy
```

**Payload (string):**

* `"18"` → Sets Economy temperature to 18°C

**SetPoint – Building Protection**

**Topic:**

```
inels/set/<MAC>/RFTC/SetPoint/BuildingProtection
```

**Payload (string):**

* `"10"` → Sets anti-frost protection temperature

#### **Fan Speed Control**

**Topic:**

```
inels/set/<MAC>/RFTC/FanSpeed
```

**Payload (string):**

* `"0"` → AUTO
* `"1"` → Speed level 1
* `"2"` → Speed level 2
* `"3"` → Speed level 3

#### **Do Not Disturb (DND)**

**Topic:**

```
inels/set/<MAC>/RFTC/DND
```

**Payload (string):**

* `"1"` → Enable DND
* `"0"` → Disable DND

#### **Make Up Room (MUR)**

**Topic:**

```
inels/set/<MAC>/RFTC/MUR
```

**Payload (string):**

* `"1"` → Enable MUR
* `"0"` → Disable MUR

#### **Butler Service**

**Topic:**

```
inels/set/<MAC>/RFTC/Butler
```

**Payload (string):**

* `"1"` → Call Butler
* `"0"` → Cancel

**UP DOWN temperature:**&#x20;

```
inels/set/2C6A6F1054A8/RFTC/Up 1
```

```
inels/set/2C6A6F1054A8/RFTC/Down 1
```

**HEAT/COOL mode**\
"inels/set/" + formattedMacAddress + "/RFTC/HeatCool" 0 = cool a 1=heat

**FANSPEED** ( now there is inofo only about 0-3 )\
value 4=OFF

### **Note on MAC Address and Device Types**

Each iNELS device is uniquely identified by its **MAC address** and **device type** (e.g., `gw`, `RFTC`, `device type`).\
Refer to the \[MQTT Device Manual] for full address mappings and descriptions.

### **Example – Setting DND ON**

**Topic:**

```
inels/set/2C6A6F105BB2/RFTC/DND
```

**Payload:**

```
"1"
```

This command turns on the DND mode in the RFTC3.


---

# 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/rftc-3-mqtt-payload-description-hotel-room.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.
