Connect
Native drivers talk to each device the way it expects, on the network it is already on. Discovery finds what is there, profiles describe what it means.
- BACnet
- Modbus
- KNX
- MQTT
- LoRa
- BLE
BACnet, Modbus, KNX, DALI, Serial Bus, MQTT, LoRa and BLE devices, read, normalized and put to work from one place.
8
Protocols read natively: BACnet, Modbus, KNX, DALI, Serial Bus, MQTT, LoRa and BLE
1
Tag model, so a temperature looks the same whichever protocol sent it
2
Ways to connect a site: a Linux edge gateway, or the Windows screen scraper for standalone systems
4
Ways to use the data: dashboards, alerts, reports and an open API
IoTServa is an IoT platform from VYROX INTERNATIONAL SDN BHD, Malaysia, that reads BACnet, Modbus, KNX, DALI, Serial Bus, MQTT, LoRa and BLE devices, turns every reading into one tag model, and adds history, alerts, dashboards, reports and an open API for building, factory and energy teams. Most sites run at least three of these protocols side by side, and IoTServa exists so that the people who need the data do not have to learn all of them.
A chiller, a power meter, a hotel room and a tank sensor can all measure temperature or energy. Each one describes it in a different way, so combining them usually means a different tool per protocol.
Object analog-input 3, property present-value.
Holding register 40012, two words, word-swapped.
Group address 1/2/5, datapoint type 9.001.
A topic string and whatever payload the vendor chose.
A few bytes on a port, decoded by a payload decoder.
A GATT characteristic or an advertising packet.
Pick a protocol to see how a native address becomes a named, typed tag. The table below lists all eight.
Read chillers, air handlers and VAV boxes over BACnet/IP and BACnet MS/TP, with COV subscriptions so changes arrive when they happen.
Native Address
Node
Tower A > AHU-02 > Supply Air Temperature
13.4°C
Sample addresses are illustrative. Real Node names follow your own Site, Facility, Level and Area naming.
Read the BACnet Page| Protocol | Native Address | Node | Value |
|---|---|---|---|
| BACnet | Device 1204, analog-input,3, present-value, units: degrees-celsius | Tower A > AHU-02 > Supply Air Temperature | 13.4 °C |
| Modbus | Unit 5 (RTU, 9600 baud, 8E1), Holding register 40012, INT16 raw 1842, scale 0.1 | Plant 1 > MDB-03 > Active Power | 184.2 kW |
| KNX | Group address 1/2/5, DPT 9.001, Room 214, temperature, KNX IP tunnelling | Hotel > Level 2 > Room 214 > Air Temperature | 23.5 °C |
| DALI | DALI line 2, short address 14, Group 3, LED driver (device type 6), Read via a BACnet/IP gateway | Office > Level 3 > Zone B > Luminaire 14 Dim Level | 80 % |
| Serial Bus | Port /dev/ttyUSB0 (RS-485), 9600 baud, 8 data bits, even parity, 1 stop bit, Unit 12, holding register 40001, Protocol: Modbus RTU | Plant > MCC-1 > Motor 12 Run Current | 14.2 A |
| MQTT | Topic factory/line-2/oven/temperature, JSON payload {"t":182.4}, QoS 1, retained, Broker over TLS | Factory > Line 2 > Oven Temperature | 182.4 °C |
| LoRa | devEUI 24E1...A3F0, uplink port 2, payload 0x0138 (312, scale 0.1), AS923, RSSI -104 dBm | Estate > Block 7 > Soil Moisture | 31.2 % |
| BLE | Gateway BG-3, room 4, MAC AC:23:3F:..., GATT 0x181A, 0x2A6E, RSSI -67 dBm | Warehouse > Rack 12 > Shelf Temperature | 19.8 °C |
Three jobs, done once, whichever protocol a device speaks.
Native drivers talk to each device the way it expects, on the network it is already on. Discovery finds what is there, profiles describe what it means.
Every reading becomes a tag with a name, a unit, a timestamp and a quality flag, placed in your site, building and equipment hierarchy.
Show it, alert on it, chart it, report on it, or hand it to another system. The same Node drives all of them.
How It Works
Eight steps every site goes through with IoTServa. Watch it play, or pick a step.
Install and Pair
$ curl -fsSL install.example.com | sh -s DEMO-CODE
Release signature verified
Service started on boot
Paired with Plant Room Gateway
Signed configuration in sync
All Sensors
BACnet, Modbus, KNX, MQTT and serial values share one shape: name, unit, time and quality.
Automation Rule
When Tank Temperature Is Above 165 °C for 5 min
Condition FalseCondition True for 5 min
Tested first with a Dry Run against the last 7 days of real data.
Actions Run in Order
Offline Buffer and Local Rules
Local Rule Heater Relay Off at 166 °C Ran Offline
Gaps are recorded, never hidden. Local Rules are signed and checked against limits on the gateway.
AI Assistant
Which tanks ran hot last night?
Tank U ran above 165 °C for 12 minutes from 02:10. The Rule switched its relays once and the alert cleared at 02:22.
Turn the heater off for one hour.
Done. Heater relay is Off, confirmed by the controller. It switches back On at 10:42.
Voice input, six AI model choices, and only the rights of the person asking.
Health and Work Orders
New: 3D Digital Twin
A three.js twin of your tanks and rooms, linked to live Nodes. Switch to a thermal view, cut a tank open to see its level, and watch the tank glow when an automation fires.

Real screens from IoTServa: what an operator, an engineer and a manager see every day.











Screens from the live IoTServa software with a demo company and demo data.
Each protocol has its own pitfalls. We build around them instead of hiding them.
Read chillers, air handlers and VAV boxes over BACnet/IP and BACnet MS/TP, with COV subscriptions so changes arrive when they happen.
Explore BACnetPoll Modbus RTU and Modbus TCP devices, decode registers with the right word order and scaling, and publish clean engineering values.
Explore Modbus
Listen to KNX group telegrams over KNX IP, map group addresses from your ETS project, and control rooms from one place.
Explore KNX
Read lamp and driver failures, energy, operating hours and emergency test results from DALI lighting through a DALI gateway or controller, in the same tag model as the rest of the building.
Explore DALI
Read meters, drives, controllers and instruments that speak over RS-485 or RS-232 serial lines. The edge gateway holds the serial port and polls each device, so the cabling never has to reach the internet.
Explore Serial Bus
Subscribe to any broker, publish normalized data back out, and keep topics, QoS and retained state under control.
Explore MQTTYears of battery, kilometres of range.
Explore LoRaTags, beacons and nearby sensors.
Explore BLEEverything between the device and the decision, built to work together.
Protocol drivers that run beside the equipment.
One shape for every reading, whatever protocol sent it.
The right view for each role, and an alert only when it matters.
Your data, available to the tools you already use.
Describe a device model once, reuse it everywhere.
When something happens on site, the right thing happens next.
Switch equipment safely, and know that it really switched.
Ask about any site in plain words, and get an answer from live data.
See trouble coming, assign the fix, and measure the result.
The right alarm reaches the right person, on the channel they will see.
Fix the machine before it stops the plant.
Cameras that raise an alert, not just record.
Your plant in live 3D, with every reading where it happens.
The site keeps measuring and acting when the internet does not.
The protocol, datasheet and manual sit next to the device.
Brokers, LoRaWAN networks, BMS and your own tools.
Real sites are never a single protocol. These are the places where combining them pays off first.
HVAC, metering and lighting from different vendors, in one view.
Drives, meters and PLCs trended together, with alarms that mean something.
Generation and consumption reconciled in one view.
Temperature coverage for cold rooms, with sensor health tracked.
Rooms, plant and meters across many buildings.
Luminaire faults, energy and emergency tests from DALI and KNX, in one view.
Sensors across land where Wi-Fi and cables never reach.
A pilot reads your real devices against written criteria. Then you decide.
Agree what the pilot must prove, and on which devices.
Drivers and profiles set up against your real equipment.
Readings checked against known values in real operation.
Results measured against the criteria. You choose the next step.
Protocol drivers run on a gateway at the site. History, dashboards and users live in the IoTServa cloud, scoped to each Client and Organization.

Practical guides from the engineers who read them every day.
BACnet and Modbus both run buildings and plants, but they model data differently. Compare their networks, discovery and addressing, and see where each fits.
Read the Guide
KNX controls rooms and BACnet controls plant. See how group addresses differ from BACnet objects, how each is secured, and why hotels and offices run both.
Read the Guide
Learn why Malaysia uses the AS923 LoRaWAN plan, what to confirm with suppliers before you buy gateways and sensors, and how airtime limits battery life.
Read the GuideThe short version of what people ask before a pilot.
IoTServa is an IoT platform that reads devices speaking BACnet, Modbus, KNX, DALI, Serial Bus, MQTT, LoRa and BLE, turns every reading into one consistent tag model, and puts the data to work in dashboards, alerts, reports and an open REST API.
BACnet (IP and MS/TP), Modbus (RTU and TCP), KNX (through KNX IP), DALI lighting (through a DALI gateway or controller), serial bus (RS-485 and RS-232 ports on the edge gateway), MQTT (as a client of any broker), LoRaWAN uplinks, and Bluetooth Low Energy through BLE gateways.
No. IoTServa reads the devices and systems you already run. It sits beside your BMS, PLCs and gateways rather than replacing them.
Protocol drivers run on an IoTServa gateway at the site, a 64-bit Linux computer, and the platform runs in the IoTServa cloud. Standalone systems with no data interface are read by the Windows Screen Scraper. IoTServa Private Edition puts the platform on a server for your company alone.
Both are possible. Every Organization is read-only by default. Writes are enabled per Node within min and max limits, and each command is signed, re-checked by the gateway and audited.
Request a pilot. Tell us which protocols and devices are on site, and we scope a small pilot that reads your real equipment before anything larger is agreed.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.