Integrating enteliWEB with Third-Party Systems

Quick Answer

enteliWEB integrates natively with BACnet-compliant devices (B-AWS / Secure Connect Hub profiles). Modbus devices require a BACnet/Modbus protocol gateway. Cross-platform sharing typically uses BACnet clients, CSV/export, web services, or Delta's enteliCLOUD API — not a built-in OPC UA server inside enteliWEB. Third-party dashboards (Power BI, Grafana) can consume exported or API-sourced data.

BACnet Third-Party Controllers

enteliWEB supports BACnet devices from any manufacturer. Third-party controllers from Siemens, Johnson Controls, Distech Controls, Automated Logic, and Honeywell can be discovered and monitored alongside Delta Controls equipment. Standard BACnet object types used in HVAC/BAS projects are supported; exact coverage depends on the device PICS and the enteliWEB version.

Modbus Integration

enteliWEB communicates natively over BACnet. Modbus devices (power meters, lighting controllers, variable frequency drives) require a BACnet/Modbus protocol gateway that translates Modbus registers into BACnet objects. See the IDEC Modbus TCP configuration guide for PLC-side Modbus setup and how Ignition handles multi-protocol device connections.

OPC and Enterprise Bridges

When enterprise systems need OPC DA/UA, integrators typically place an OPC gateway or SCADA/OPC server (for example Ignition) that reads BACnet or exported data and republishes OPC. Do not assume enteliWEB itself exposes a native OPC UA endpoint.

Lighting and Specialty Systems

BACnet-enabled lighting controllers (DALI gateways, dimming controllers) integrate directly. Non-BACnet lighting systems require protocol translation via gateway devices.

Data Export

Export trend data and energy reports as CSV for analysis in Excel, Power BI, or Grafana. For larger integrations, enteliCLOUD (Delta Controls' cloud platform) provides a documented API for third-party access.