Integration : iNELS System with NETx BMS via MQTT Protocol

Table of Contents:

1. Introduction

2. System Requirements

3. Architecture Overview

4. MQTT Setup

   • Broker Configuration

   • iNELS Central Unit Setup

   • NETx BMS MQTT Module Setup

5. Topics and Payloads

   • Predefined Topics

   • Payload Format

6. NETx BMS Multiprotocol Server

   • Installation & Setup

   • Protocol Conversion to PMS, Door Lock Systems, etc.

7. Testing and Validation

8. Troubleshooting

9. Support and Maintenance

---

1. Introduction

This manual provides step-by-step instructions for integrating the iNELS system with NETx BMS using the MQTT protocol. This setup is ideal for hotel and commercial projects where NETx BMS acts as the superior platform, handling protocol conversion to other systems like PMS (Property Management System), door lock systems, and more.

By leveraging the MQTT communication protocol, this integration allows monitoring and control of iNELS wireless and BUS units through the NETx BMS system.

---

2. System Requirements

Before proceeding with the integration, ensure the following systems and tools are in place:

• iNELS Central Units (for communication and control)

• MQTT Broker (e.g., Mosquitto, EMQX, or any MQTT-compliant broker)

• NETx BMS Core or NETx Multiprotocol Server

• MQTT Module for NETx BMS

---

3. Architecture Overview

The integration follows this architecture:

1. iNELS Central Units connect to an MQTT Broker.

2. NETx BMS with its MQTT Module subscribes to predefined topics from the iNELS system via the broker.

3. NETx BMS handles monitoring, control, and protocol conversion for external systems like PMS or door lock systems.

The MQTT broker mediates all communication between iNELS and NETx BMS, allowing real-time data exchange and command execution.

---

4. MQTT Setup

Broker Configuration

1. Install and configure an MQTT broker (e.g., Mosquitto).

2. Ensure the broker is accessible to both iNELS central units and NETx BMS.

3. Secure the broker using authentication (username/password) and/or SSL certificates for encrypted communication if required.

iNELS Central Unit Setup

1. Access the iNELS system through iDM for BUS system and eLAN gateway web page for wireless system.

2. Define the iNELS units in Device manager who will publish/subscribe to MQTT.

3. Navigate to Communication Settings > MQTT Settings.

4. Set the following parameters:

   • Broker Address: IP or hostname of the MQTT broker.

   • Port: Standard MQTT ports (1883 for unsecured, 8883 for SSL).

   • Client ID: Unique identifier for each central unit.

   • Authentication: Enter MQTT broker credentials if required.

NETx BMS MQTT Module Setup

1. Open the NETx BMS Configuration Tool.

2. Install the MQTT Module if not already available.

3. Configure the MQTT connection by providing:

   • Broker Address: IP or hostname of the MQTT broker.

   • Port: Match the port of the broker (1883).

   

   • Data point definition: Enter the iNELS topics (detailed in Section 5).

---

5. Topics and Payloads

The communication between iNELS and NETx BMS is managed through predefined MQTT topics and corresponding payloads. These topics allow both systems to monitor statuses and issue control commands.

Predefined Topics

Here are some example topics that can be used:

Status Topic Payload (Bits)

Topic: inels/status/2C6A6F104825/bits/000001

Payload:

Copy

{
    "last_seen": "2024-03-15T13:02:07.+0100Z",
    "state": {
        "000": 1,
        "001": 0,
        "002": 0,
        ...
        "040": 0
    }
}

Set Topic Command (Bits)

Topic: inels/set/2C6A6F104825/bits/000001

Command:

Copy

{
    "cmd": {
        "005": "toggle"
    }
}

Status Topic Payload (Integers)

Topic: inels/status/2C6A6F104825/integers/000001

Payload:

Copy

{
    "last_seen": "2024-03-15T13:11:33.+0100Z",
    "state": {
        "000": 2556,
        "001": 0,
        "002": 97,
        ...
        "020": 0
    }
}

Set Topic Command (Integers)

Topic: inels/set/2C6A6F104825/integers/000001

Command:

Copy

{
    "cmd": {
        "002": 97
    }
}

---

6. NETx BMS Multiprotocol Server

The NETx BMS Multiprotocol Server facilitates protocol conversions from iNELS to other systems like PMS or door locks.

Installation & Setup

1. Install the Multiprotocol Server using the official NETx installation guide.

2. Configure the iNELS system via MQTT as a source protocol within the Multiprotocol Server.

3. Set up destination protocols as modules (e.g., PMS, door lock systems) for conversion.

Define mappings between iNELS and the external systems, ensuring that each command/status is correctly routed.

Protocol Conversion to PMS, Door Lock Systems, etc.

---

7. Testing and Validation

Testing Steps:

1. Verify that the iNELS central units successfully connect to the MQTT broker.

2. Confirm that NETx BMS subscribes to the relevant topics and receives data.

3. Test control commands by sending payloads from NETx BMS to iNELS and verify the physical response (e.g., turning lights on/off).

4. Ensure that status updates from iNELS are reflected correctly in the NETx BMS interface.

---

8. Troubleshooting

• Connection Issues: Check the MQTT broker logs to ensure both iNELS and NETx BMS are connecting correctly.

• Topic/Message Mismatch: Verify that the topics and payloads are correctly defined and formatted.

• Delayed Updates: Ensure the MQTT QoS (Quality of Service) level is set appropriately for your project (typically QoS 1 or 2).

---

9. Support and Maintenance

For ongoing maintenance, ensure that:

• The MQTT broker is regularly monitored for connectivity.

• Firmware/software updates for both iNELS and NETx BMS are applied.

• Logs are periodically checked for errors or disconnects.

For advanced issues, refer to the respective support teams of iNELS and NETx BMS for assistance.