Most commercial buildings have two separate control systems running in parallel: a building automation system managing HVAC and a standalone lighting control system managing lights. They operate on different schedules, managed by different people, accessible through different interfaces, and generating different alarms into different systems. When HVAC says the building is unoccupied and lighting says the building is occupied, nobody knows who is right.
Integrating lighting into your BAS does not mean eliminating your lighting controls vendor's system. It means connecting the two so they share occupancy data, operate on coordinated schedules, and appear together on the same management dashboard. In buildings where this integration is done well, facilities teams have better information, occupants have better experience, and building operators have less to manage separately.
The Case for Integration
Coordinated scheduling. The most straightforward benefit is having HVAC and lighting on the same occupancy schedule. When a conference room is booked for a meeting, both the lighting and the ventilation should respond together. When the meeting ends and the room goes unoccupied, both should step back together. Running two independent scheduling systems means either operating both separately (double the administrative work) or accepting that they will be out of sync.
Single dashboard. From an operations standpoint, having to check two different front-end systems to understand building status is inefficient. When a facilities manager wants to know why a zone is uncomfortable, the relevant information includes both the HVAC status and the lighting/occupancy status of that zone. Presenting both together in one interface is genuinely more useful.
Energy reporting. Meaningful whole-building energy reporting requires all major loads. A building that has detailed HVAC energy data but no lighting data is working with an incomplete picture. Integrating lighting into the BAS allows energy dashboards to show total building consumption, with HVAC and lighting as distinct categories, against a single baseline.
Demand response. Utilities increasingly offer demand response programs that pay building owners to reduce electrical load during peak periods. HVAC load shedding is the most common response strategy, but lighting is another significant load that can be reduced (by dimming to a lower level, not turning off) during demand response events. An integrated BAS can coordinate simultaneous lighting and HVAC load shedding through a single demand response event handler.
Integration Methods
The right integration method depends on the lighting system you have or are installing, the BAS platform you are running, and what level of control you actually need.
BACnet Integration
BACnet is the preferred integration method for new installations where the lighting control system supports it. Modern lighting control platforms from Lutron (via their BACnet interface option), Acuity's nLight system, and others can present lighting zones as BACnet objects on your BAS network. The BAS can read occupancy status, current light level, and fault status from the lighting system, and can write setpoints, scene commands, and override requests back.
BACnet integration gives you the highest level of bidirectional control and is the most maintainable long-term because it uses a standard protocol that is not dependent on a proprietary interface staying current.
Modbus Integration
Where BACnet is not available from the lighting system, Modbus TCP or RTU is a common alternative. Modbus integration is more limited in terms of available data points, and the data model is less self-describing than BACnet, but it is widely supported and effective for basic occupancy sharing and control.
Dry Contact Integration
The simplest and least flexible integration method is dry contact, using relay outputs from the BAS to control lighting relays in the lighting panel, and digital inputs from occupancy sensors or lighting panel status contacts back to the BAS.
Dry contact integration is appropriate when the lighting system has no network protocol support and you need basic occupied/unoccupied scheduling. It does not provide any dimming control, no lighting level feedback, and no detailed fault information. But it is reliable, inexpensive, and requires no special gateway hardware.
DALI Gateways
DALI (Digital Addressable Lighting Interface) is a lighting-specific protocol used for granular dimming control of individual fixtures. A DALI-to-BACnet gateway translates the DALI network into BACnet objects, allowing the BAS to control individual fixture dimming levels, read lamp fault status, and manage lighting groups.
DALI integration is worth considering in spaces where individualized dimming control is important (private offices, laboratories, high-end conference rooms) and where the lighting system is already using DALI drivers.
Systems We Commonly Integrate
The lighting control systems we most frequently integrate with building automation are:
Lutron: Lutron's RadioRA 3 and Quantum systems support BACnet/IP integration through their integration processors. Lutron tends to be more common in higher-end commercial and hospitality applications. The BACnet integration is mature and well-documented.
Acuity nLight: nLight is an addressable lighting control system that uses BACnet/IP natively. Individual sensors and switches register as BACnet devices, making integration with Niagara N4 straightforward using the standard BACnet driver.
Enlighted: Enlighted is a cloud-connected smart lighting and sensor system common in newer commercial office buildings. Integration with traditional BAS platforms is through an API rather than BACnet, which requires a software integration layer rather than a hardware gateway.
Generic 0-10V dimming: Many standard LED drivers support 0-10V dimming control. BAS controllers with analog outputs can drive 0-10V signals directly, providing basic dimming control without any lighting protocol. This is a practical option for simple applications where granular feedback is not required.
Coordination During Construction
The biggest challenge with lighting integration is not technical, it is organizational. Lighting controls vendors often want to deliver a standalone system that is complete and tested without depending on the BAS. HVAC controls contractors often do not want to coordinate with the lighting trade during construction. The result is two systems that could communicate but do not.
Addressing this requires someone, either the owner's representative, the mechanical/electrical engineer, or the general contractor, to explicitly require coordination between the lighting controls contractor and the BAS contractor in the project specification. The specification should require a joint commissioning phase where both systems are tested together, with verified data exchange between them.
If you are in the design phase of a new building or a major renovation and lighting integration is something you want, the time to require it is in the specifications and owner's project requirements, not after both systems are installed and operating independently. Retrofitting integration between two already-commissioned systems is possible but significantly more difficult than building it in from the start.