Message Brokers
Gateways send signed telemetry over MQTT 3.1.1 to a broker you configure, over TLS with a username and password.
IoTServa connects at the protocol level, so it sits beside your brokers, networks and systems instead of replacing them.
Gateways send signed telemetry over MQTT 3.1.1 to a broker you configure, over TLS with a username and password.
Receive uplinks from the network server that manages your gateways, through its MQTT or HTTP integration, and apply a payload decoder per sensor model.
Read BACnet controllers directly, or read the Modbus and BACnet gateways that an existing BMS already exposes. Control logic stays in the BMS.
Read PLCs and drives that speak Modbus, and machines that publish MQTT, without installing anything on the controller.
Pull Nodes and history over the REST API, documented with OpenAPI, into the analytics and reporting tools your team already uses, or export CSV and JSON.
Send meter readings, production counts and Work Orders to ERP and accounting systems, and pull asset lists back.
Send alert events in the app, by push, SMS, WhatsApp, Telegram, email and voice call, to Microsoft Teams and Slack, and to ticketing tools through signed webhooks, with escalation when nobody responds. Reports go out on a schedule.
IoTServa works at the protocol level, so any device that speaks BACnet, Modbus, KNX, MQTT, LoRaWAN or BLE can be read once it has a device profile. We confirm specific models during the pilot.
No. They are examples of widely used open or standards-based tools that IoTServa can exchange data with at the protocol level. They are trademarks of their owners.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.