Other protocols

Besides SNMP and Modbus, the "Protocols" tab in the device form has a separate section for several other protocols. If the model was selected from the catalog, only the protocols that model supports are shown; for a custom device, all sections are shown. Each section has an on/off toggle. This lesson reviews the key fields of each protocol and its support status, so you gather the right information before going on site.

Get to know the page

For a custom device, this note is shown above the tab: "This device was not selected from the catalog; all protocols supported by the system are shown. Enable the ones the device actually uses." In other words, a section being shown does not mean that specific piece of equipment supports it.

On the same tab, the sections ONVIF / RTSP (دوربین) (ONVIF / RTSP (ONVIF / RTSP (camera))), SSH / Telnet, and HTTP REST API are also shown; operational setup of these three is likewise done on request as an integration package.

Step by step: MQTT

1. Turn on the MQTT section. On the پروتکل‌ها (Protocols) tab, turn on the MQTT section's toggle.
2. Enter the broker details. Enter the URL واسطه (URL (Broker URL)) (the organization's MQTT broker address), شناسه مشتری (Client ID) (unique per device), and the broker's username and password.
3. Set the QoS and topic. QoS has three values: 0 (at most once), 1 (at least once, default), and 2 (exactly once). In موضوع (Topic), write the data-publishing path following the sample pattern, e.g., devices/{id}/telemetry.

   

4. Save and coordinate. Click ذخیره (Save). The connection details are recorded alongside the device; in the current version, automatic connection setup after saving is done only for SNMP, so coordinate with the implementation team to start the MQTT subscription and map topics to data points.

Step by step: Redfish

1. Turn on the Redfish (DMTF) section. This protocol is used to monitor servers through a management controller (such as iLO, iDRAC, or XClarity).
2. Enter the management account. Enter the username (hint: "usually root or admin") and password. Preferably create a separate read-only account on the server's controller.
3. Check the base path. مسیر پایه (Base Path) defaults to /redfish/v1, which is the DMTF standard path and usually needs no change. Then save and coordinate for activation as with MQTT.

Protocols set up on request

The BACnet/IP, KNX, and M-Bus sections are shown on the protocols tab, but operational connectivity for these protocols in the current version is set up on request as an integration package, and filling in these sections alone does not read any data. The same applies to OPC UA, Beckhoff ADS, and Tuya. To prepare a request, gather this information:

Which protocol to choose

If equipment offers several communication paths, the preference order in the current version is clear: first the catalog model (whichever protocol its profile is ready for), then SNMP for networked equipment such as UPSes, PDUs, switches, and environmental sensors, then Modbus TCP for meters and industrial equipment. MQTT is a good fit when the equipment or an intermediate gateway publishes the data itself and you are only the consumer. Redfish suits server hardware monitoring through a management controller and works without installing an agent on the operating system. For legacy building equipment that only has BACnet or KNX, or M-Bus meters, setup is done as an integration package; plan for this in the project schedule.

PLC controllers

Connecting PLCs (Siemens S7, Omron FINS, Mitsubishi MC, and EtherNet/IP) has no separate section in the device form and is configured as an integration package. Before requesting it, get these parameters from the controls team:

Tips and common mistakes

• On the "Connection Settings" tab, the KNX, M-Bus, and EtherCAT options only specify the physical medium; they do not activate a protocol.
• If the model was selected from the catalog and you don't see the protocol section you need, that model has not declared that protocol in the catalog; choose the correct model or use a custom device.
• For MQTT, a duplicate client ID causes the broker connection to repeatedly drop and reconnect.
• A protocol section being turned on in the form does not mean data is being received; always verify actual reception in the data-point list and their current values.

Summary

• All protocols are registered from the "Protocols" tab in the device form.
• MQTT and Redfish have operational drivers; activating them is coordinated with the implementation team.
• BACnet, KNX, M-Bus, OPC UA, and PLCs are set up as an integration package, on request.
• Before going on site, complete each protocol's parameter table with the equipment team.