Protocol Support
Eight Protocols, Compared
What each protocol is for, how it connects, and how IoTServa reads it.

The Eight, Side by Side
| Protocol | Best For | Medium | Range | Data Model | IoTServa Reads It Via |
|---|---|---|---|---|---|
| BACnet | HVAC and building plant | IP networks (BACnet/IP over UDP, BACnet/SC over secure WebSocket) or RS-485 (MS/TP) | Building and campus LAN | Objects with properties: Analog Input, Analog Value, Binary, Multi-state, Schedule, Trend Log | BACnet/IP on your LAN, or MS/TP through an RS-485 gateway |
| Modbus | Meters, drives and PLCs | RS-485 or RS-232 (RTU), Ethernet port 502 (TCP) | Plant floor and switch room | Four tables: coils, discrete inputs, input registers, holding registers | RS-485 serial or Ethernet port 502 |
| KNX | Lighting, blinds and rooms | Twisted pair (TP), KNX IP, KNX RF | A building or campus, with areas and lines linked over KNX IP | Group addresses (for example 1/2/5) carrying typed datapoints (DPT) | A KNX IP interface or router |
| DALI | Luminaire status and emergency tests | Two-wire bus carrying power and data, read through a DALI gateway or controller | Up to 300 m between the furthest devices on 1.5 mm2 cable, per DALI line | Control gear (drivers) and control devices (sensors, buttons), addressed by short address, group and scene | A DALI gateway or controller, over its BACnet, Modbus, KNX or MQTT interface |
| Serial Bus | Legacy and serial-only equipment | Serial cable: shielded twisted pair for RS-485, point-to-point for RS-232 | RS-485: about 1200 m at 100 kbit/s or lower, shorter at higher speeds. RS-232: about 15 m by the standard, longer at low baud rates on good cable | A master polls devices by address, one request at a time; the electrical layer carries the bytes, a protocol on top gives them meaning | An RS-485 or RS-232 port on the edge gateway |
| MQTT | Moving data between systems | TCP and TLS (port 8883), WebSocket | Anywhere with IP reachability | Topic strings with free-form payloads such as JSON or plain values | Your broker, as a client |
| LoRa | Low-power sensors over distance | Sub-GHz radio to a gateway, then IP backhaul | Kilometres in open terrain, less indoors | Small uplink frames on a port, decoded by a payload decoder | Your LoRaWAN network server or gateways |
| BLE | Tags and short-range sensors | 2.4 GHz radio to a BLE gateway, then IP backhaul | Metres to tens of metres indoors (Bluetooth 5 Coded PHY reaches further in open line of sight) | Advertising data, or GATT services and characteristics | BLE gateways in the premises |
Which One Fits Your Site?
Find your situation and jump to the matching page.
I Have HVAC Controllers or a BMS
BACnet
I Have Power Meters, Drives or PLCs
Modbus
I Have Smart Lighting or Hotel Rooms
KNX
I Have DALI Lighting and Want Failure Alerts
DALI
I Have Equipment on an RS-485 or RS-232 Line
Serial Bus
My Devices Already Publish to a Broker
MQTT
I Need Sensors Where There Are No Cables
LoRa
I Want to Tag Assets or Read Nearby Sensors
BLE
Choosing, Answered
Which protocol should I start with?
Start with the protocol of the equipment that matters most on site. Most pilots begin with one wired protocol and one wireless one, then add the rest.
Can one project use all eight protocols?
Yes. Protocols are drivers inside the same project, and every reading ends up in the same tag model.
Start with One Site. Prove It on Real Devices.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.