BACnet integration
BACnet is the default supervisory protocol for commercial HVAC in many regions. CONTEXUS treats BACnet devices as first-class citizens alongside MQTT and Modbus in Open IoT Hub.
Supported profiles
- BACnet/IP on UDP/47808 (BBMD-aware deployments supported via router config)
- MS/TP segments behind BACnet/IP routers (B-TL/dongle)
- Read-focused integration for analog, binary, and multi-state objects
- Write privileges gated by role — enable only after commissioning sign-off
Network placement
Run the protocol adapter on the same broadcast domain as controllers, or configure a BBMD table when traversing subnets. In Docker, use network_mode: host on Linux for BACnet discovery, or map known device IPs explicitly when host networking is unavailable.
# Example: list containers after compose up (web on 9001, db on 5433)
docker-compose ps
docker-compose logs -f webDiscovery workflow
- Define a BACnet data source with interface IP and UDP port.
- Run Who-Is / I-Am discovery or import a static device list from your BMS export.
- Select object types (AI, AO, BI, BO, MI, MO, AV, BV) to poll or subscribe via COV.
- Map BACnet names to canonical point IDs for dashboard bindings.
Polling vs COV
Use COV for high-change values such as space temperature when the controller supports it; fall back to scheduled reads for older firmware. Default poll intervals should respect controller CPU limits — start at 60s for supervisory trending, tighten only where alarms require it.
Commissioning checklist
- Confirm device instance numbers do not collide across VLANs merged into one hub.
- Verify priority arrays before enabling writes to setpoints.
- Document schedules and overrides — expose as read-only points first.
- Compare against BMS graphics in the gallery templates.
Troubleshooting
See troubleshooting for firewall and discovery issues. BACnet traffic does not traverse naive NAT; place the adapter on the control VLAN.
Next steps
Explore a running stack, review the open source repositories, estimate ROI for a deployment, or talk with the CONTEXUS team about integration and licensing.
Module licensing details are summarised on /licensing. Browse reference dashboards in the gallery.