Talks to what’s already on your site.
Eight field protocols at the edge; REST, MQTT, CoAP and webhooks out to the rest of your stack.
At the site
Field-side protocols
No rip-and-replace: if your equipment already speaks one of these, ELIAN reads it where it stands.
Modbus TCP / RTU
Pull holding / input registers from PLCs, BMS controllers and meters. Per-register polling intervals; signed and unsigned 16/32-bit support.
OPC-UA
Subscribe to existing SCADA tag namespaces. Browse the address space from the admin UI; pin tags to ELIAN sensors.
LoRaWAN
Webhook-based ingestion from The Things Network and ChirpStack. Per-LNS configuration, per-device decoder support.
BACnet/IP
Ingest building-management signals (HVAC, lighting, occupancy). Read-only by default.
M-Bus
Wired meter-bus for water, heat and energy meters. Periodic polling with at-least-once semantics.
BLE GATT
Bluetooth-LE characteristic reads from beacons and sensors via the gateway’s built-in radio.
Zigbee
Bridges an existing Zigbee2MQTT setup: device state is re-mapped per device and republished as standard telemetry. Needs Zigbee2MQTT and a coordinator running alongside the gateway.
KNXnet/IP
Tunnels to a KNX IP gateway, listens for group telegrams and runs periodic group reads, decoding DPT values into ELIAN sensors.
BLE, Zigbee and KNX integrations require host radio access (BLE) or a third-party coordinator/gateway on the LAN (Zigbee2MQTT, KNXnet/IP).
To the cloud
Cloud-side protocols
For devices that reach the internet on their own, and for pushing ELIAN data into your own systems.
REST
Devices POST readings with API-key auth (header or body). Per-device primary & secondary keys, bcrypt-hashed, rotatable from the UI.
MQTT
Native MQTT broker with a standard topic hierarchy. External pub/sub supported.
CoAP
Lightweight UDP for constrained devices.
Webhooks (in)
Trigger workflows from external systems with a per-workflow URL and shared secret.
Webhooks (out)
Workflow actions can fire arbitrary HTTPS POSTs with template-rendered bodies.
Out to your team
Notification & messaging
Where alerts and reports come out, and through which provider.
Azure Communication Services as primary path with O365 SMTP fallback. Multi-language templates.
SMS
Twilio, Vonage, MessageBird or Azure Communication Services. E.164 validation, per-notifier event-type filters, per-user quiet hours (critical alerts override).
In-app notifications
Real-time WebSocket delivery to the Notification Center. 13+ categories with per-category email / in-app toggles per user.
A clean bridge to the rest of your stack.
Outbound webhooks fire arbitrary HTTPS POSTs with template-rendered bodies. The public REST API exposes every entity. Together they cover the bridge to ticketing tools, ERP, CMMS, chat platforms and anything else your team already runs. We’re happy to walk through the specific integration shape you need.
