Turn your Koolmesh lighting network into a practical source of room-level building data.
Through HBGW04/R, selected occupancy, daylight, lighting, device-status and supported energy data can be made available to compatible building-management platforms via BACnet/IP, Modbus TCP/IP or MQTT.
Does Your BMS See What Is Happening Inside the Room?
Many building-management platforms control plant, HVAC, schedules and alarms but have limited visibility of real-time conditions inside individual rooms.
What the BMS Controls
HVAC
Plant equipment
Schedules
Alarms
THE MISSING LAYER
Structured room-level information
What’s Actually Happening in the Room
Occupancy and presence
Daylight lux levels
Lighting status
Other sensor status
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.
LIGHTING IS EVERYWHERE PEOPLE ARE
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.
From Lighting Data to Building Operation
One connected route carries selected lighting-side and room-level information from Koolmesh devices into the building-management system.
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.
FIELD LAYER
Koolmesh Lighting Devices & Sensors
Bluetooth Mesh
GATEWAY LAYER
HBGW04/R
Multi-protocol Gateway
Translate
PROTOCOL LAYER
Standard BMS Interfaces
Integrate
BMS LAYER
BMS
FIELD DATA Occupancy · daylight · lighting status · energy · device conditionGATEWAY OUTPUT BACnet/IP · Modbus TCP/IP · MQTTSUPERVISORY USE Dashboards · reporting · monitoring · agreed control
Final point lists, object mapping, writable points and integration responsibilities must be confirmed for each project.
What Data Can the Lighting Network Share?
A connected lighting network can give the BMS a clearer view of connected spaces—from occupancy and daylight to lighting operation and supported device data.
Space Use
Occupancy and presence across rooms and zones.
Daylight
Daylight lux levels and ambient brightness through the space.
Lighting Operation
Lighting status, dimming levels and colour temperature where available.
Energy Use
Consumption and metering data from compatible devices.
Device Health
Device status and selected fault information.
Zones & Scenes
Information and control at room, zone, group or scene level.
Turn Room-Level Data Into Building Action
Each available room-level input can support a practical building-level outcome when used within the BMS control strategy.
Occupancy→
Demand-Based HVAC
Adapt heating, cooling and ventilation to actual room use.
Occupancy over time→
Space Utilisation
Understand when and how rooms and areas are being used.
Daylight + Lighting + Energy→
Energy Optimisation
Identify unnecessary operation and support building energy strategies.
Device / Fault Status→
Proactive Maintenance
Surface faults centrally and prioritise intervention.
Out-of-Hours Occupancy→
Operational & Security Alerts
Flag unexpected activity outside normal schedules.
Lighting Control / Writable Points→
Whole-Building Automation
Coordinate lighting with HVAC, schedules, modes or other building systems.
EXAMPLES IN PRACTICE
Room-Level InputOccupancy data provides a clearer view of how spaces are actually being used.Supervisory UseSelected data can support dashboards, reporting, alerts and operational review.
Available data depends on the connected Koolmesh devices, gateway configuration, firmware version and agreed project scope. The BMS determines the final logic and response.
Where This Route Fits
Turn a lighting project into a practical building automation opportunity.
Upgrade Existing Lighting Infrastructure
Use a lighting refurbishment or retrofit as an opportunity to bring room-level data into the wider building automation system.
Bring More Data into an Existing BMS
Add occupancy, lighting and sensor data from the spaces the BMS may not currently see.
Connect Lighting from the Start
Make the lighting network part of the wider building automation strategy in new-build projects.
Extend Your Luminaire Offering Beyond Lighting
Use connected sensors and controls to make room-level data from your luminaires available to the wider BMS.
Connect the Lighting Network to the BMS
HBGW04/R provides the multi-protocol connection between the Koolmesh Bluetooth Mesh lighting network and compatible building-management or supervisory platforms.
CORE INTEGRATION PRODUCT
HBGW04/R
Multi-protocol BMS Gateway
Connects Koolmesh Bluetooth Mesh lighting systems with building-management and supervisory platforms.
Every project has a different lighting installation, BMS, network and point requirement. These answers establish the starting point.
Can this be added to an existing Koolmesh lighting installation?+
Yes, depending on the existing devices, gateway compatibility and project configuration. This makes it possible to extend an existing lighting installation into building automation without starting again from scratch.
Can it integrate with any BMS?+
Integration is possible with BMS and supervisory platforms supporting BACnet/IP, Modbus TCP/IP or MQTT. The required points, mapping, network access and integration route should be confirmed for each project.
Where does the automation logic sit?+
Koolmesh makes lighting and room-level data available to the BMS. The BMS remains the supervisory layer and determines how that data is used within the wider building automation strategy.
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.
This website uses cookies to ensure the best experience possible. More information...