Skip to documentation content

Integrations

BACnet Integration

Configure BACnet/IP discovery, object mapping, monitoring, and control.

On this page

BACnet Integration & Setup Guide

Overview

C-Bridge supports BACnet integration to enable communication between Casambi lighting networks and building management systems (BMS). This allows lighting data and control to be exposed to third-party systems such as HVAC, energy management, and facility dashboards.

C-Bridge acts as a BACnet server (device), publishing lighting and sensor data as standard BACnet objects.

Key Features

  • Automatic mapping of Casambi devices to BACnet objects
  • Real-time or polling-based updates
  • Support for lighting, sensors, scenes, and areas
  • Standard BACnet object types (Analog, Binary, Multi-state)
  • Compatible with common BMS platforms

BACnet Architecture

In a typical setup:

  • C-Bridge = BACnet Server (device)
  • BMS / Controller = BACnet Client

C-Bridge exposes:

  • Device-level data (lights, sensors)
  • Group/area control
  • Energy and status values

Supported Object Types

C-Bridge automatically generates BACnet objects based on device type:

Device TypeBACnet Object TypeExample Use
Light LevelAnalog Output (AO)Dimming control
On/Off StatusBinary Output (BO)Switching
Daylight sensorAnalog Input (AI)Lux
Occupancy sensorBinary Input (BI)Occupied / unoccupied
ScenesMulti-state Value (MSV)Scene recall
Device StatusBinary Input (BI)Online / offline

Before You Begin

Ensure the following:

  • C-Bridge is installed and powered
  • Network connection is active (Ethernet recommended)
  • Casambi network is commissioned and operational
  • BACnet client (BMS) is available on the same network

Enabling BACnet on C-Bridge

  1. Log into the C-Bridge interface
  2. Navigate to Settings → BACnet
  3. Enable BACnet service
  4. Configure the following:

Required Settings

  • Device Instance Number (unique on network)
  • BACnet Port (default: 47808)
  • Network Interface (Ethernet recommended)
  1. Save configuration and restart BACnet service

Device Discovery

Once BACnet is enabled:

  • The C-Bridge device will appear on the BACnet network

  • Use a BACnet tool or BMS to:

  • Discover devices

  • Read object lists

Common tools:

  • YABE (testing)
  • BMS platforms (Tridium, Siemens, etc.)

Object Mapping

C-Bridge automatically maps Casambi devices into BACnet objects.

Example Mapping

  • Light fixture → Analog Output (brightness control)
  • Occupancy sensor → Binary Input
  • Daylight sensor → Analog Input (lux value)
  • Scene → Multi-state Value

Example naming convention: Area_DeviceType_ID.

Control & Monitoring

Reading Data

BACnet clients can:

  • Read light levels
  • Monitor occupancy
  • Track sensor values
  • View device status

Writing Commands

Where enabled, BACnet clients can:

  • Adjust light levels
  • Turn devices on/off
  • Recall scenes

Update Modes

C-Bridge supports multiple data update strategies:

Real-Time (Event-Based)

  • Updates are pushed automatically when values change
  • Best for responsive systems

Polling

  • BACnet client requests updates at intervals
  • Simpler but less efficient

Hybrid

  • Combination of event updates and periodic polling

Network Considerations

  • Ensure C-Bridge and BACnet client are on the same subnet
  • Avoid port conflicts (default UDP 47808)
  • Use static IP for stability in enterprise environments
  • Configure firewall rules if needed

Commissioning Checklist

Before completing setup:

  • BACnet service enabled on C-Bridge
  • Unique device instance configured
  • Device visible in BACnet discovery
  • Objects are readable from BMS
  • Control commands function correctly
  • No network conflicts or duplicate IDs

Troubleshooting

Device Not Discoverable

  • Verify BACnet is enabled
  • Check network connectivity
  • Confirm correct port and subnet

Objects Not Updating

  • Check update mode (polling vs real-time)
  • Verify Casambi network communication

Control Not Working

  • Ensure write permissions are enabled
  • Confirm correct object type (AO vs BI vs MSV)

Best Practices

  • Use consistent naming conventions for objects
  • Group devices logically by area
  • Limit unnecessary polling to reduce network load
  • Document device instance numbers for each installation

Ignition Integration

Ignition (an industrial automation and SCADA platform) is a commonly used BACnet client for C-Bridge deployments — see System Overview and Terminology & Definitions. Because C-Bridge exposes standard BACnet/IP objects, Ignition can discover and poll it like any other BACnet device.

An Ignition-specific commissioning walkthrough has not yet been verified. Confirm the driver configuration and point mapping with your integrator before deployment.

Future Enhancements

Planned BACnet improvements may include:

  • Advanced object configuration
  • BACnet write prioritization handling
  • BTL certification for full compliance

Summary

BACnet integration allows C-Bridge to bridge lighting systems into broader building automation platforms. With proper setup, users can monitor, control, and optimize lighting alongside other building systems from a centralized interface.