Go to homepage

BUILDING CONTROL FEATURE

Lighting Data to Building Automation

Turn your Koolmesh lighting network into a practical source of room-level building data.

Through the HBGW04/R gateway, occupancy, daylight, lighting status and device data can be shared with building management platforms using BACnet/IP, Modbus TCP/IP or MQTT.

Explore How It Works Discuss Your Project

THE MISSING LAYER

Does Your BMS See What Is Happening Inside the Room?

Building platforms may have limited visibility of what is actually happening inside rooms and occupied spaces.

01

Building-Level Control

  • Plant equipment
  • HVAC operation
  • Schedules
  • Alarms
THE MISSING LAYER

Structured room-level information

02

Room-Level Reality

  • Occupancy and presence
  • Daylight levels
  • Lighting zone status
  • Device condition

The challenge is not simply collecting more data. It is making useful room-level data available to the BMS in a structured, project-ready format.

A meeting room illustrating room-level sensing and lighting dataDaylightLighting StatusOccupancy

DATA ALREADY IN THE ROOM

Why Lighting Is the Natural Starting Point

Lighting sensors are already installed in one of the most useful positions in the building: the ceiling. They are close to occupants, desks, corridors, meeting rooms, daylight and room boundaries.

With connected controls and sensors, the lighting layer can provide a practical view of how rooms and zones are actually being used.

OccupancyDaylightLighting StatusDevice Condition
Lighting-control infrastructure becomes more than lighting. It becomes a room-level data source for wider building operation.

THE INTEGRATION PATH

How Lighting Data Reaches the BMS

01

Sense

Koolmesh luminaires, controllers and sensors collect lighting-side and room-level information.

02

Connect

Devices communicate through the Koolmesh Bluetooth Mesh lighting network.

03
BLE⇄IP

Translate

HBGW04/R converts devices, sensors, zones and scenes into accessible BMS data points.

04

Integrate

The BMS uses selected data for dashboards, reporting, monitoring and agreed control strategies.

From existing lighting infrastructure to usable building dataOccupancy, daylight, energy, device status and control data are collected through the lighting network and made available to agreed building-system interfaces.
Koolmesh contributes room-level data.The BMS remains the supervisory layer.

Final point lists, object mapping, writable points and integration responsibilities must be confirmed for each project.

AVAILABLE DATA

What Lighting Data Can Be Shared?

Available data depends on the connected Koolmesh devices, gateway configuration, firmware version and project requirements.

Lighting Control & Status

ON/OFF, dimming and CCT commands and status where supported.

Occupancy & Presence

Motion, presence and room or zone occupancy information.

Daylight

Daylight sensor lux values and ambient brightness information.

Energy Data

Meter readings and cumulative consumption where available.

Zones, Groups & Scenes

Identification, related control data and scene recall where supported.

Device & System Status

Selected device, system and failure-return information where supported.

HBGW04/R multi-protocol BMS gateway

MULTI-PROTOCOL CONNECTION

One Lighting Network. Three BMS Interfaces.

HBGW04/R bridges the Koolmesh Bluetooth Mesh lighting network with building-management and supervisory platforms.

BACnet/IP

The main route for exposing selected lighting and sensor data as structured BACnet objects.

Modbus TCP/IP

A register-based interface for compatible building and energy-management systems.

MQTT

A local data-exchange route for MQTT-enabled platforms and compatible supervisory systems.

Objects, registers, topics and writable values depend on connected devices, gateway configuration and agreed project scope.

FROM DATA TO ACTION

How the BMS Can Use Lighting-Side Data

01Occupancy

HVAC Scheduling

Room or zone occupancy can help the BMS align heating, cooling or ventilation strategies more closely with actual space use.

02Daylight + Lighting Status

Energy Review

Daylight levels and lighting operation data can support dashboards, operational review and energy-management strategies.

03Device Status

Maintenance Workflow

Selected device and fault information can be surfaced through a BMS or facility-management interface for clearer visibility.

04Out-of-Hours Occupancy

Operational Alerts

Where configured by the BMS team, occupancy outside normal schedules can support security or operational alerts.

People-counting sensor identifying occupants as room-level data
Room-Level InputOccupancy data provides a clearer view of how spaces are actually being used.
Energy dashboards and room-level operation and maintenance supervision using building data
Supervisory UseSelected data can support dashboards, reporting, alerts and operational review.

The BMS or supervisory platform determines the final logic and response. Koolmesh provides the available field data.

SYSTEM RESPONSIBILITIES

Three Layers. Clear Responsibilities.

FIELD DEVICE LAYER

Collect

Connected luminaires, controllers and sensors collect lighting-side and room-level data.

INTEGRATION LAYER

Convert

The gateway converts selected field data into formats that can be used by the BMS.

SUPERVISORY / BMS LAYER

Visualise & Act

The BMS applies dashboards, reporting, logic and facility-management interfaces.

Multi-floor building cutaway representing room-level field data across the building
ROOMS & ZONESOne connected field layer across the building

Connected luminaires, controllers and sensors extend room-level visibility from individual spaces to wider building operation.

Where This Route Fits

Lighting projects requiring BMS visibilityExisting BMS projects missing room-level dataOEM luminaires supporting wider building integrationNew-build or refurbishment projects requiring open lighting data

COMPATIBLE PRODUCTS

Build the Right Integration Route

Choose the connected sensors, controllers, drivers and system-level components that match the data and control route required by the project.

HBGW04/R BMS Gateway front view
CORE INTEGRATION PRODUCT

HBGW04/R

Multi-protocol BMS Gateway

Connects Koolmesh Bluetooth Mesh lighting systems with building-management and supervisory platforms.

BACnet/IP | Modbus TCP/IP | MQTT
View product

FAQ

Integration Questions, Answered Clearly.

Every project has a different BMS, network and point requirement. These answers establish the starting point.

Does Koolmesh replace the existing BMS?+

No. Koolmesh provides lighting-side and room-level data through an integration gateway. The BMS remains the supervisory platform.

Which communication protocols are supported?+

HBGW04/R supports BACnet/IP, Modbus TCP/IP and MQTT. BACnet/IP is the main route for exposing selected lighting and sensor data as BACnet objects.

Can the BMS control the lighting system?+

Selected commands and writable points may be supported where the connected device, gateway configuration, firmware and agreed project strategy allow. The final point list and control hierarchy must be confirmed during project review.

What data can be shared?+

Depending on the connected devices, available data may include lighting control and status, occupancy, daylight, CCT, energy readings, zones, groups, scenes and selected device status.

Can this be added to an existing BMS project?+

Yes, where the existing BMS is accessible and a suitable integration route is available. Network access, protocols, required data points and system responsibilities should be reviewed before deployment.

START THE CONVERSATION

Bring Room-Level Lighting Data Into Your BMS Project

Share your project type, existing or planned BMS platform and required data points. Hytronik can help review the suitable lighting devices, gateway and integration route.

Discuss Your Project Project type | BMS platform | Required data points
This website uses cookies to ensure the best experience possible. More information...