English 
Français 
Español 
Deutsch 
Português 
Italiano 
العربية Connect · BACnet
BACnet building systems, visible beyond the BMS
Your BMS speaks BACnet; your operations team wants live dashboards, escalating alarms, and one platform across every building. A BACnet-to-MQTT edge gateway reads the points that matter and publishes them as JSON over MQTT into Kilo.
Connect · BACnet
How BACnet equipment connects to Kilo
Bridge BACnet to MQTT
An edge gateway on the building network reads BACnet points — via change-of-value subscriptions or polling — from AHUs, chillers, VAV boxes, and meters.
Publish points as JSON
Values arrive on topics like building/floor-2/ahu-1/data with point-to-value JSON payloads — into your own broker or a Cloud MQTT endpoint.
Register equipment as devices
Each AHU or controller becomes a device with mapped metrics — supply temperature, setpoints, fan state — feeding dashboards, rules, and alarms.
Connect · BACnet
BACnet integration specs
- HVAC coverage
- Air handling units, chillers, VAV boxes, heat pumps, and meters — any point your BACnet network exposes can be bridged into the platform.
- COV or polling
- Change-of-value subscriptions keep traffic low by publishing only when a point changes; polling covers equipment that does not support COV.
- Complements the BMS
- Control stays in the BMS. Kilo adds fleet-wide visibility, escalation chains, and analytics on top — read-side integration, no rewiring of control logic.
- Point mapping
- Point-to-value JSON payloads map to normalized metrics; nested payloads flatten automatically to dot-notation keys.
- Multi-building portfolios
- Every building publishes into the same pipeline, so portfolio dashboards and cross-site comparisons come for free.
Connect · BACnet
What your BACnet data feeds
Connect · BACnet
BACnet integration FAQ
Does Kilo have a native BACnet driver?
No. Kilo’s native connectors are LoRaWAN/mioty, MQTT, and vehicle trackers. BACnet equipment connects through a BACnet-to-MQTT edge gateway on the building network — the standard pattern for getting BMS data into cloud platforms.
Will this interfere with my BMS?
No. The edge gateway reads points via COV subscriptions or polling; control logic remains entirely in the BMS. Kilo consumes the resulting telemetry stream — it does not sit in the control loop.
What gateway software works?
Vendor BMS bridges, integration platforms and appliances such as EasyIO, and custom integration flows all work. The only requirement is that the gateway publishes JSON over MQTT to a broker the platform can reach.
Why put BACnet data in an IoT platform at all?
Because the BMS stops at the building. Kilo adds escalating alarm chains that reach on-call staff, dashboards spanning whole portfolios, and rules that combine BACnet points with wireless sensors — for example LoRaWAN room sensors validating what the AHU claims.
See every building on one screen
Start free and bridge your first BACnet points — or book a call and we’ll scope the edge gateway and point list with your BMS integrator.