Integrating HVAC with lighting and access control

Most commercial buildings already know where people are. Lighting systems have occupancy sensors in nearly every room, access control systems log every card swipe, and room booking systems know which meeting rooms are reserved. Yet in many buildings, the HVAC system runs on fixed schedules and ignores all of this information. Integrating these systems lets HVAC respond to actual occupancy, saving energy in empty spaces while maintaining comfort where people are.

This guide covers what integration can achieve, how systems are connected, and the limits that must be respected for life safety and security.

Why integrate

HVAC systems traditionally assume every zone is occupied throughout the scheduled day. In practice, offices and meeting rooms are frequently empty, hybrid work has reduced average occupancy, and after-hours use is unpredictable. Occupancy information allows:

• Setpoint setback in unoccupied zones during the day
• Reduced ventilation in unoccupied zones, consistent with ASHRAE 62.1 occupied standby provisions
• Lower VAV minimum airflows in unoccupied zones
• After-hours HVAC on demand, triggered by card access instead of a phone call or timed override
• Pre-conditioning of booked meeting rooms before a meeting starts
• Better data for space planning and energy analysis

NECB 2020 and ASHRAE 90.1 include requirements for occupancy-based control in certain space types, and ASHRAE Guideline 36 defines occupied standby mode for zones with occupancy sensors. See occupancy-based HVAC control.

Sources of occupancy data

Combining sources usually works best: lighting sensors for room presence, access control for building-level arrival, and CO2 for ventilation.

Integration methods

BACnet

The simplest approach is when lighting controls expose occupancy status as BACnet objects that the BAS can read. Many networked lighting control systems support BACnet/IP directly or through a gateway. The BAS maps each lighting zone's occupancy object to the corresponding HVAC zone. See BACnet basics for building owners.

Hardwired contacts

For a few critical points, such as a main entrance card reader enabling after-hours HVAC, a dry contact between systems is simple and robust.

Software integration and APIs

Access control, room booking and analytics platforms often integrate at the software level using APIs. A supervisory platform or middleware collects data from several systems and passes relevant signals to the BAS. This approach is flexible but adds a layer that must be maintained and secured.

Shared sensors

Some multi-sensors combine occupancy, light level, temperature, humidity and CO2 in one device and serve both lighting and HVAC. This reduces ceiling clutter but requires agreement between trades on ownership, configuration and maintenance.

Designing the integration

1. Map zones. Lighting zones, HVAC zones and access control areas rarely line up. Create a map showing which occupancy inputs apply to which HVAC zones.
2. Define behaviour. For each zone, specify what happens when it becomes vacant: setpoint offsets, ventilation reduction, minimum airflow changes and time delays.
3. Set time delays. Lighting sensors often switch off after 10 to 20 minutes. HVAC setback should usually wait somewhat longer, and recovery should be fast enough that occupants returning to a room do not notice.
4. Handle failures. If communication between systems fails, zones should default to occupied mode, not to setback.
5. Specify responsibilities. Make clear in the contract documents which contractor provides, configures and tests each part of the interface.
6. Commission end to end. Test from the sensor or card reader through to the HVAC response.

Common problems in practice

Integrations that look simple on paper often fail quietly after turnover. Typical findings include:

• Lighting sensors relocated or recalibrated during tenant fit-outs without updating the BAS mapping
• Lighting time delays shortened to save energy, causing HVAC to set back while people are still in the room
• Gateways that stop updating after a software change, leaving zones stuck in one mode
• After-hours card access enabling an entire floor or air handler when only one office is occupied
• No trends of occupancy status, so nobody notices that a zone has reported vacant for months

Trending occupancy inputs alongside zone temperatures and airflows, and reviewing them periodically, catches most of these problems early.

Life safety boundaries

Integration must never compromise life safety systems. Fire alarm systems, smoke control, stairwell pressurization and emergency door release are governed by the NBC, provincial fire codes and CAN/ULC standards such as CAN/ULC-S524 for fire alarm installation and CAN/ULC-S1001 for integrated systems testing.

• Life safety functions should be initiated by the fire alarm system through listed interfaces, not through the BAS or a lighting network.
• The BAS may monitor fire alarm status, but it should not be relied on to perform life safety functions unless specifically designed and listed for that purpose.
• Access control door release on fire alarm must follow the applicable codes and the authority having jurisdiction.

Integrated systems testing under CAN/ULC-S1001 verifies that these interactions work as intended. See integrated systems testing and CAN/ULC-S1001.

Cybersecurity and privacy

Every integration creates a new connection between networks, and access control systems in particular are security-critical. Good practice includes network segmentation, least-privilege access between systems, encrypted communications where available (such as BACnet/SC), and coordination with the owner's IT and security teams. Using person-level access data for HVAC raises privacy questions; aggregate occupancy, rather than individual identities, is usually all HVAC needs. See cybersecurity for building automation systems.

Our building automation work includes defining and testing these interfaces.

Key takeaways

• Lighting sensors, access control and booking systems already hold occupancy data HVAC can use.
• Integration enables setback, reduced ventilation and minimum airflows in empty zones, and on-demand after-hours HVAC.
• BACnet, hardwired contacts and software APIs are the main integration methods.
• Map zones, define behaviour and failure modes, and commission end to end.
• Life safety functions stay with the fire alarm system, and integrations must be secured and respect privacy.