IoTServa Get Started
IoT Platform for Buildings and Plants

Eight Protocols.
One IoT Platform.

BACnet, Modbus, KNX, DALI, Serial Bus, MQTT, LoRa and BLE devices, read, normalized and put to work from one place.

A DIN-rail IoT gateway at the centre of an open building control cabinet, field cables running in from both sides and teal status lights glowing
Wired and Wireless Together One Tag Model Edge Gateway Plus Cloud REST API and Signed Webhooks Read-Only by Default

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.

Every System Speaks
Its Own Dialect.

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.

  • One place to look. Every device appears in the same list with the same names and units.
  • No re-wiring. Devices stay on the protocol they already use.
  • Nothing to translate by hand. Scaling, byte order and datapoint types are handled once per device model.
BACnet

Object analog-input 3, property present-value.

Modbus

Holding register 40012, two words, word-swapped.

KNX

Group address 1/2/5, datapoint type 9.001.

MQTT

A topic string and whatever payload the vendor chose.

LoRa

A few bytes on a port, decoded by a payload decoder.

BLE

A GATT characteristic or an advertising packet.

Many Addresses In. One Tag Out.

Pick a protocol to see how a native address becomes a named, typed tag. The table below lists all eight.

BACnet

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

Device 1204
analog-input,3
present-value
units: degrees-celsius

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
See All Eight Examples in a Table
ProtocolNative AddressNodeValue
BACnetDevice 1204, analog-input,3, present-value, units: degrees-celsiusTower A > AHU-02 > Supply Air Temperature13.4 °C
ModbusUnit 5 (RTU, 9600 baud, 8E1), Holding register 40012, INT16 raw 1842, scale 0.1Plant 1 > MDB-03 > Active Power184.2 kW
KNXGroup address 1/2/5, DPT 9.001, Room 214, temperature, KNX IP tunnellingHotel > Level 2 > Room 214 > Air Temperature23.5 °C
DALIDALI line 2, short address 14, Group 3, LED driver (device type 6), Read via a BACnet/IP gatewayOffice > Level 3 > Zone B > Luminaire 14 Dim Level80 %
Serial BusPort /dev/ttyUSB0 (RS-485), 9600 baud, 8 data bits, even parity, 1 stop bit, Unit 12, holding register 40001, Protocol: Modbus RTUPlant > MCC-1 > Motor 12 Run Current14.2 A
MQTTTopic factory/line-2/oven/temperature, JSON payload {"t":182.4}, QoS 1, retained, Broker over TLSFactory > Line 2 > Oven Temperature182.4 °C
LoRadevEUI 24E1...A3F0, uplink port 2, payload 0x0138 (312, scale 0.1), AS923, RSSI -104 dBmEstate > Block 7 > Soil Moisture31.2 %
BLEGateway BG-3, room 4, MAC AC:23:3F:..., GATT 0x181A, 0x2A6E, RSSI -67 dBmWarehouse > Rack 12 > Shelf Temperature19.8 °C

Connect. Normalize. Act.

Three jobs, done once, whichever protocol a device speaks.

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

Normalize

Every reading becomes a tag with a name, a unit, a timestamp and a quality flag, placed in your site, building and equipment hierarchy.

  • Name
  • Unit
  • Timestamp
  • Quality

Act

Show it, alert on it, chart it, report on it, or hand it to another system. The same Node drives all of them.

  • Dashboards
  • Alerts
  • Reports
  • API

See the Platform Architecture

How It Works

From a Wire to a Decision.

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

Modbus RTURS-485MQTT over TLS

New: 3D Digital Twin

Your Plant in Live 3D.

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.

  • Realistic and Thermal modes, with a spot meter
  • Cutaway tanks at the live radar level
  • Alarm glow, notice and sound when a Rule fires
The IoTServa 3D Tank View with the U Shape bitumen tank glowing red and a Bitumen Over Temperature notice

See the Software Itself

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

The IoTServa Home screen with open alert counts, gateways online, Nodes reporting and Site cards with live values
Operate Home Open alerts by severity, gateways online, Nodes reporting and the newest reading, then one card per Site with live values and a 24 hour line.
An IoTServa dashboard with cold room temperature, steam pressure gauge, plant power and feedwater level widgets
Dashboards Value, gauge, trend, table and open alert widgets on your own dashboards, refreshed every 10 seconds.
The IoTServa 3D Tank View with the U Shape bitumen tank glowing red and a Bitumen Over Temperature notice
3D Tank View and Alarms A three.js twin of a bitumen tank farm. When the over temperature Rule fires, the tank glows, the probe pulses and a notice appears.
An alert page showing a critical alert that was escalated twice and snoozed with a technician note
Escalation and Snooze An alert nobody acknowledges is sent again on the rule's escalation schedule. Snooze it with a note while someone works on it.
The Gateways list with three online gateways on version 0.5.12 and a details panel
Gateway Fleet Every gateway with its status, version and transport. Select one to see buffered messages, devices, Nodes and configuration.
A floor plan of a food plant with live value markers in the cold room, freezer, boiler house and switchboard
Floor Plans Your own floor plan picture with live values and gateways placed where they really are. Markers turn red on an open alert.
An A4 Weekly Cold Chain Summary report with totals, a chart and a figures table
A4 Reports Summary, consumption, availability and alert reports as an A4 document: print it, download the PDF or CSV, or email it on a schedule.
The IoTServa Home screen on a phone
Home on a Phone The same console on a phone, no app to install.
The IoTServa Alerts list on a phone
Alerts on a Phone Acknowledge and snooze from the plant floor.
A Node page with a trend chart on a phone
Node on a Phone Latest value and 24 hour chart in your hand.
An IoTServa dashboard on a phone
Dashboard on a Phone Widgets stack into one column.

Screens from the live IoTServa software with a demo company and demo data.

Take the Full Product Tour

Prove It Before You Commit

A pilot reads your real devices against written criteria. Then you decide.

See the Pilot Process

Scope

Agree what the pilot must prove, and on which devices.

Connect

Drivers and profiles set up against your real equipment.

Prove

Readings checked against known values in real operation.

Decide

Results measured against the criteria. You choose the next step.

Deployment

Your Data Stays Where You Put It.

Protocol drivers run on a gateway at the site. History, dashboards and users live in the IoTServa cloud, scoped to each Client and Organization.

  • Edge gateway. Drivers run beside the equipment, so a lost uplink does not stop collection.
  • Store and forward. Readings are buffered on the gateway disk during an outage and sent in order afterwards.
  • Cloud or your own server. One place for many sites in the cloud, or Private Edition on a server for your company alone.

How We Protect It Private Edition

Close-up of a DIN-rail IoT gateway with RS-485 terminals, an Ethernet cable and a small antenna, teal status lights lit

Questions, Answered.

The short version of what people ask before a pilot.

More Questions

What is IoTServa?

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.

Which protocols does IoTServa support?

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.

Do I have to replace my existing devices or BMS?

No. IoTServa reads the devices and systems you already run. It sits beside your BMS, PLCs and gateways rather than replacing them.

Where does IoTServa run?

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.

Can IoTServa control equipment, or only monitor it?

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.

How do we start?

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.

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.

WhatsApp