Solutions / HVAC Zone Control
Wireless HVAC zone control via BACnet/IP and Modbus TCP
Thread mesh sensor nodes feed occupancy and CO2 data to your existing chiller, boiler, and AHU control systems — no gateway middleware required.
Request HVAC PilotIntegration approach
Direct BMS integration — no extra server
MK-GW-1000 translates Thread sensor data to BACnet/IP or Modbus TCP natively. Your existing BMS polls the gateway like any other BACnet device on the network.
BACnet/IP object model
Each sensor node appears as a BACnet device with standard analog input objects for temperature, humidity, CO2, and occupancy. Your BMS sees it like a wired sensor.
Modbus TCP register map
Standard Modbus TCP slave register map for Siemens, Honeywell, and Johnson Controls systems. Register addresses are configurable per zone to match your existing BMS addressing scheme.
Occupancy-driven setpoints
Feed live occupancy counts from MK-NODE-OCC directly to HVAC zone setpoint logic. Unoccupied zones setback automatically, reducing heating/cooling to unoccupied spaces.
Compatible systems
Tested BMS compatibility
BACnet/IP + Modbus TCP. N2 bus adapter available. Tested with JCi Network Automation Engines (NAE).
BACnet/IP native. Point mapping via Desigo BACnet driver. Tested with PXM50 / PXM40 controllers.
BACnet and Modbus TCP drivers. Node-RED integration for custom logic. Tested with Niagara 4.x.
Retrofit HVAC controls without rewiring
We map your existing BMS addressing before any hardware ships. Pilot typically 50–100 nodes in one HVAC zone.