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
IoT Platform for Buildings and Plants
Six Protocols.
Six Protocols.
One IoT Platform.
BACnet, Modbus, KNX, MQTT, LoRa and BLE devices, read, normalized and put to work from one place.
Wired and Wireless Together
One Tag Model
Edge, On-Premise or Cloud
Open REST and MQTT Output
Read-Only Mode per Site
6
Protocols read natively: BACnet, Modbus, KNX, MQTT, LoRa and BLE
1
Tag model, so a temperature looks the same whichever protocol sent it
3
Ways to deploy: on an edge gateway, on your own server, or in the cloud
4
Ways to use the data: dashboards, alerts, rules and an open API
Most sites run at least three of these protocols side by side. 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.
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
Normalized tag
site.tower-a.ahu-02.supply-air-temp
13.4°C
Sample addresses are illustrative. Real tag names follow your site, building and equipment naming.
Read the BACnet PageConnect. Normalize. Act.
Three jobs, done once, whichever protocol a device speaks.
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, trend it, automate with it, or hand it to another system. The same tag drives all of them.
- Dashboards
- Alerts
- Rules
- API
Six Protocols, Each Done Properly.
Each protocol has its own pitfalls. We build around them instead of hiding them.
KNX
Listen to KNX group telegrams over KNX IP, map group addresses from your ETS project, and control rooms from one place.
Explore KNXLoRa
Years of battery, kilometres of range.
Explore LoRaBLE
Tags, beacons and nearby sensors.
Explore BLEBACnet
Read chillers, air handlers and VAV boxes over BACnet/IP and BACnet MS/TP, with COV subscriptions so changes arrive when they happen.
Explore BACnetModbus
Poll Modbus RTU and Modbus TCP devices, decode registers with the right word order and scaling, and publish clean engineering values.
Explore Modbus
MQTT
Subscribe to any broker, publish normalized data back out, and keep topics, QoS and retained state under control.
Explore MQTTFive Parts, One Platform
Everything between the device and the decision, built to work together.
Edge Gateway
Protocol drivers that run beside the equipment.
Tag Model
One shape for every reading, whatever protocol sent it.
Dashboards and Alerts
The right view for each role, and an alert only when it matters.
Open API
Your data, available to the tools you already use.
Device Profiles
Describe a device model once, reuse it everywhere.
Integrations
Brokers, LoRaWAN networks, BMS and your own tools.
Built for Sites With Mixed Equipment.
Real sites are never a single protocol. These are the places where combining them pays off first.
Commercial Buildings
HVAC, metering and lighting from different vendors, in one view.
Factories and Plants
Drives, meters and PLCs trended together, with alarms that mean something.
Energy and Solar
Generation and consumption reconciled in one view.
Cold Chain
Temperature coverage for cold rooms, with sensor health tracked.
Hotels and Campuses
Rooms, plant and meters across many buildings.
Estates and Agriculture
Sensors across land where Wi-Fi and cables never reach.
Prove It Before You Commit
A pilot reads your real devices against written criteria. Then you decide.
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.
Run protocol drivers on a gateway at the site, keep history on your own server, or use the cloud. You choose, and you can mix.
- Edge gateway. Drivers run beside the equipment, so a lost uplink does not stop collection.
- On-premise server. History, dashboards and users stay inside your network.
- Cloud. One place for many sites, with TLS and per-site access.
Learn the Protocols
Practical guides from the engineers who read them every day.
BACnet vs Modbus: Which Protocol Fits Which Job
BACnet and Modbus are both common in buildings and plants. Compare their data models, networks and where each one fits.
Read the Guide KNX vs BACnet in Buildings: Rooms Versus Plant
KNX controls rooms, BACnet controls plant. See how they differ and why many buildings run both.
Read the Guide
LoRaWAN in Malaysia: What AS923 Means for Your Sensors
LoRaWAN devices and gateways must use the right regional plan. Learn why Malaysia uses AS923 and what to check before buying.
Read the GuideQuestions, Answered.
The short version of what people ask before a pilot.
What is IoTServa?
IoTServa is an IoT platform that reads devices speaking BACnet, Modbus, KNX, MQTT, LoRa and BLE, turns every reading into one consistent tag model, and puts the data to work in dashboards, alerts, rules and an open API.
Which protocols does IoTServa support?
BACnet (IP and MS/TP), Modbus (RTU and TCP), KNX (through KNX IP), 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?
At the edge on a gateway or industrial PC, on a server in your own premises, or in the cloud. Many sites use an edge gateway for protocol work and a server for history and dashboards.
Can IoTServa control equipment, or only monitor it?
Both are possible, and writes can be disabled per site. A monitoring-only project stays read-only until you decide otherwise.
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.