> 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-bus/inspinia/inels-integration-to-skyplatform/adding-inels-bus-units-to-inspinia-via-mqtt.md).

# Adding iNELS BUS Units to Inspinia via MQTT

This version replaces the outdated steps and provides a clean, step-by-step guide suitable for **iNELS Wiki**.

## **iNELS BUS Integration to Inspinia via MQTT (Updated Manual)**

### **Using Bits & Integers in SkyPlatform**

This manual explains how to integrate iNELS BUS units with Inspinia using **MQTT**, based on the latest update where **iNELS BUS devices are no longer added directly in SkyPlatform**.\
Integration is now performed using **Bits** and **Integers** representing BUS statuses and commands.

## **System Requirements**

You will need:

* **iNELS Central Unit** (CU3-07M, CU3-08M, CU3-09M, CU3-10M)
*  MQTT Broker
* **Inspinia Touch Panel** (4", 8", or 10") or MiniServer
* **SkyPlatform account access**
* **MQTT Explorer** (optional but recommended for checking payloads)

## **Enter MQTT Broker Credentials in iDM**

1. Add the bits and Integers in system manager and link it to the iNELS devices inside the iDM project
2. Go to **CU Configuration** in iDM.
3. Enter the MQTT broker credentials:
   * Broker address
   * Port
   * Username
   * Password
4. Save configuration to CU.
5. Save the entire project back to the CU.

This step allows the CU to connect to the MQTT broker and publish the BUS data.

## **Add iNELS MQTT Device in SkyPlatform**

In the updated version, iNELS BUS units are **not added** to SkyPlatform.\
Instead, you add an **iNELS MQTT device** and configure Bits and Integers.

#### How to add:

1. Open SkyPlatform → **Devices** → **Add Device**.

2. Select **iNELS MQTT**.

   <figure><img src="/files/TNx9aUK6qXBjMuCVg3we" alt="" width="315"><figcaption></figcaption></figure>

3. Enter the same **MQTT broker credentials** that you used in iDM.

<figure><img src="/files/EvHumpMSSqvOMAAEoWYg" alt="" width="375"><figcaption></figcaption></figure>

## **Add Bits and Integers in SkyPlatform**

After entering broker data:

1. In the iNELS MQTT device window, click **Add Bit** or **Add Integer**.
2. Now you must supply the **Device ID** and **Bit/Integer index**.

<figure><img src="/files/ufreM825A5vvqLiMKlFH" alt="" width="375"><figcaption></figcaption></figure>

#### How to find the Device ID:

Use **MQTT Explorer** and observe the iNELS MQTT topics.

* **Bit Device IDs** start with: **D00001**
* **Integer Device IDs** start with: **E00001**

#### How indexing works:

* Each Bit Device contains **40 bits**
  * Start index = **001**
  * End index = **039**

Example: inels/status/2C6A6F10XXXX/bits/D00001\
If DeviceID = `D00001`, available topics will include:

{"last\_seen":"2025-03-25T03:29:50.+0100Z",
\
"state":{"000":0,"001":0,"002":0,"003":0,"004":0,"005":0,"006":0,"007":0,"008":0,"009":0,"010":0,"011":0,"012":0,"013":0,"014":0,"015":0,"016":0}}

#### Important Notes

* Ensure the Bit number in SkyPlatform **matches the same Bit number in iDM Monitor**.
* Confirm the same Bit number exists in **MQTT Bit Status Topic**.
* If mismatched, the connection **will not work**.

For Integers, indexing follows the same structure but applies to **integer values**.

Add all Bits/Integers you need.

## **Add Bits/Integers to the Design Plane**&#x20;

1. Go to **Design** in SkyPlatform.
2. Drag the Bit or Integer object into the design plane.
3. Link it to:
   * Buttons
   * Switches
   * UI elements
   * Other devices
   * Automations

This allows Inspinia to send commands to iNELS or display statuses.

<figure><img src="/files/am9Iseh8ni0DESE5Thlt" alt=""><figcaption></figcaption></figure>

## **Linking Between Multiple CUs**

Because MQTT is a **broker-based** protocol, Bits and Integers can also be used to:

* Link devices between **multiple CUs**
* Trigger inter-CU events
* Synchronize room controls (hotel, commercial, or residential)

This makes cross-system integration very simple.

## **Important Notes & Best Practices**

* Use **MQTT Explorer** to verify that the CU publishes values.
* Bit mappings must match across **iDM**, **MQTT**, and **SkyPlatform**.
* If a Bit does not respond, check:
  * Wrong index
  * Wrong Device ID
  * Unit not selected for export in iDM
  * Incorrect MQTT credentials


---

# 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-bus/inspinia/inels-integration-to-skyplatform/adding-inels-bus-units-to-inspinia-via-mqtt.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.