Keep your existing platform
Use supported standard interfaces to bring Koolmesh data into the BMS already used by the building.
Open Building Integration
Open integration, shaped around your project.
Connect Koolmesh lighting and compatible field devices to the building systems you choose. Use an existing BMS, select FIN-based Koolmesh BMS supervision, or combine supported routes as the project grows.
Open integration that fits your building
Lighting, sensors, HVAC and management platforms can use different networks. Adding a new system can leave information in separate places, while new cabling can make retrofit work harder.
Koolmesh keeps the connection open. Bring lighting and compatible field devices into a supported existing BMS, select FIN-based Koolmesh BMS supervision, or combine the routes around your project.
Mix compatible devices
Connect supported Koolmesh and third-party field devices through an agreed integration route.
Choose now, extend later
Start with one route or combine several. Select FIN when its supervisory and local management capabilities are needed.
Choose the connections your project needs
Use one route or combine supported routes. FIN is selected when its integration, supervision and local management capabilities are needed.
Bluetooth lighting
Koolmesh lighting and sensor data
LoRaWAN devices
Supported Koolmesh and third-party devices
Bluetooth gateway
BACnet · Modbus · MQTT
LoRaWAN gateway
Field data for BMS integration
Choose your management platform
Your existing BMS / PLC
Bring new data into the platform already in place.
FIN-based Koolmesh BMS
Select coordinated supervision and local management.
Compatible BACnet, Modbus or M-Bus systems
Direct FIN-based integration
Use one route
Select Bluetooth integration, LoRaWAN integration or the FIN-based route for the project’s current needs.
Combine routes
Bring different device networks into a common supported management platform. Include FIN where its capabilities are required.
Expand in stages
Start with the connection needed now, then extend compatible devices and integration routes as the project develops.
01 Bring Koolmesh lighting into your existing BMS
Open lighting data through a Bluetooth-to-BMS gateway route.
Lighting-control and sensor data
Occupancy
Daylight
Energy
Device status
Control
→
Multi-protocol output
.webp?ts=1787714911)
.webp?ts=1787714915)
.webp?ts=1787714917)
→
BMS
HMI
PLC
Keep the platform your team already uses
Bring lighting and sensor information into a supported existing BMS through standard interfaces. Use occupancy, daylight and device status alongside other building data for monitoring, control and energy management.
Features that support this route
- BACnet/IP, Modbus TCP/IP and MQTT interfaces.
- Accessible lighting, sensor, zone and scene data points.
- Local Web configuration, App-based commissioning and OTA updates.
Use this gateway route on its own with a supported BMS, or combine it with other device networks and FIN-based supervision.
Gateway installation example
The connection point inside the cabinet
The gateway sits alongside the building’s control equipment, linking the Koolmesh lighting network with a supported management platform.
- Compact DIN-rail installation.
- Bluetooth communication with the lighting devices.
- Ethernet connection to the supported BMS layer.
Detailed power and connection specifications are available on the HBGW04/R product page.
02 Connect wireless devices across the building
.webp?ts=1787714907){kind=logo}
Bring compatible LoRaWAN devices into building management, with less new cabling.
⇄
⇄
BMS
BACnet/IP
Cloud
Add supported devices where cabling is difficult
Use a wireless field-device route for retrofit projects and distributed sensors or HVAC devices. Connect supported Koolmesh and third-party LoRaWAN devices, then bring their available data and control points into a supported BMS or PLC.
Features that support this route
- Built-in LoRaWAN network server.
- Supported Koolmesh and third-party LoRaWAN device access.
- Ethernet, Wi-Fi and optional 4G backhaul for flexible deployment.
Use the LoRaWAN route independently or combine it with Bluetooth lighting integration. Select FIN supervision when the project needs that management layer.
Extend the wireless device network as needed
LoRaWAN provides a long-range, low-power field-device network. Start with the required areas and plan further compatible devices around the building’s coverage and integration needs.
Wide coverage
Low power consumption
High capacity
Enhanced security
Gateway placement examples
Flat-surface placement
A flexible option for open areas and service spaces.
Bracket installation
Suitable for a protected and discreet installation.
03 Manage connected systems through Koolmesh BMS
Choose FIN-based supervision for a coordinated building view and local operation.
Put connected information to work
Bring available lighting, sensing, HVAC and metering data into a common building view. Use the FIN-based Koolmesh BMS platform to review trends, manage operating plans and follow alarms through a browser-based interface.
Features that support this route
- Multi-protocol integration for compatible building systems.
- Local edge management and browser-based engineering and operation.
- Trends, operating schedules and alarm views.
Select the FIN route directly for compatible wired systems, or combine it with Bluetooth and LoRaWAN gateway routes. It is an option when these supervisory capabilities are needed.
Review trends over the day
Compare changing values over time and identify periods that need attention.
Plan operating hours
Organise schedules around the way the building and its zones are used.
Follow alarms and events
See which connected points need attention and review their event records.
Controller integration features
A multi-protocol edge controller
HIC01 provides a FIN-based route for compatible BACnet, Modbus, M-Bus and other supported building systems. Combine supported gateway data and direct field-system connections around the project’s agreed point mapping and control requirements.
Keep access and local operation under control
Where FIN-based supervision is used, work through the local network or select remote access via FIN Edge2Cloud. Existing BMS routes use the access and operational arrangements of the chosen platform.
Fits perfectly into a controls cabinet.
.webp?ts=1787714910){kind=logo}
Edge2Cloud
Fully browser-based user interface for engineering and operation.
What if the gateway or cloud goes down?
Control is executed at terminal level. A Bluetooth mesh distributes logic across nodes, so local lighting control continues if the gateway or cloud is unavailable. LoRaWAN devices communicate through their gateway, so resilience must be handled in the project design.
Bluetooth Mesh
Local logic and scene control keep working independently of cloud supervision.
LoRaWAN Layer
Gateway-dependent communication is addressed through system architecture and operational planning.
Encrypted Channels
Encrypted communication and secure device commissioning across every layer.
Role-based Access
Operator, integrator and administrator roles with scoped permissions.
Signed Firmware & OTA
Signed firmware and controlled over-the-air updates.
Network Segmentation
Separation between field, integration and supervisory layers.
Not sure which route fits your project?
Tell us about the systems already in place, the devices you want to connect and the level of control or supervision you need. Our team can help you identify a suitable integration route.