API & ProtocolsIntegrating InfraSensing sensors
with your BMS, NMS & IoT platforms
Modbus TCP, BACnet IP & Modbus RTU for native BMS integration.
SNMP (Gets & traps) for NMS & DCIM platforms.
Native RS-485 sensor versions on select models.
MQTT 3.1 / 3.1.1 with TLS for industrial IoT platforms.
Open, documented protocols — no vendor lock-in, no cloud dependency.
One IP address exposes every sensor on the base unit.
SNMP (Gets & traps) for NMS & DCIM platforms.
Native RS-485 sensor versions on select models.
MQTT 3.1 / 3.1.1 with TLS for industrial IoT platforms.
Open, documented protocols — no vendor lock-in, no cloud dependency.
One IP address exposes every sensor on the base unit.
Sensors
temperature · humidity · flood · power · airflow · more
RJ45 — data & power
Base Unit
SensorGateway — one IP address
Modbus TCP
BACnet IP
SNMP
Modbus RTU*
MQTT
Your Platform
BMS · DCIM · NMS · IoT
* Modbus RTU (RS-485) on select models
BMS first: for enterprise, co-lo and hyperscale facilities the natural integration point is the building management system — over Modbus TCP, BACnet IP and Modbus RTU.
Protocol availability depends on the base unit model.
Protocol availability depends on the base unit model.
Modbus TCP
The universally supported path into your BMS — and into SCADA, PLC and automation platforms — with a fully documented register map.
BACnet IP
Native BACnet IP on supporting base units: sensor readings exposed as BACnet objects that your building management system discovers directly.
One Base Unit, Every Protocol
All sensors on a base unit are exposed through a single IP address — over the supported protocols simultaneously. Availability varies by base unit model.
SNMP for NMS & DCIM
For network monitoring & DCIM platforms: full SNMP support with Gets and traps, plus ready-made integration guides for Nagios, PRTG, Zabbix, SolarWinds, Centreon and more.
Modbus RTU on RS-485
The serial path into your BMS: the RTU add-on and select native RS-485 sensor versions integrate directly with controllers, field buses and 3rd party gateways.
MQTT for IoT Platforms
Publish every reading to your industrial IoT platform over MQTT 3.1 / 3.1.1 — via TCP or TLS, with username or client certificate authentication.
Modbus TCP
Modbus TCP is supported natively by the base unit and is the most universally understood way into a building management system — virtually every BMS, SCADA, PLC and automation platform on the market speaks it.
Modbus User Manual
- Native on the base unit — no gateway, no middleware, no cloud dependency.
- Fully documented register map covering every sensor value and status on the unit.
- One integration per base unit: every connected sensor arrives through a single IP address.
- Alerting independent of the BMS: the base unit keeps sending its own email, SNMP trap and optional SMS alerts even if the BMS link goes down.
Modbus User Manual
SNMP for NMS & DCIM
For network monitoring systems (NMS) and DCIM platforms, the base units support two methods of SNMP:
- SNMP Get: requests can be made to the base unit using SNMP v2c or v3.
- SNMP Traps: sent by the base unit using SNMP v1 or v3.
Modbus RTU on RS-485
Where the BMS, controller or field bus side is serial, the platform speaks Modbus RTU over RS-485 in two ways:
- Modbus RTU Add-On: adds an RS-485 interface to the base unit, exposing the connected sensors over Modbus RTU.
- RS-485 sensor versions: select sensors are available as native RS-485 models for direct integration with BMS controllers, industrial control systems and 3rd party gateways — no base unit required.
User Manual RTU Add-On RS-485 Sensor Pricing & Info
MQTT for Industrial IoT Platforms
For customers integrating the sensors with industrial IoT platforms, the base unit firmware supports publishing over MQTT.
- MQTT versions 3.1 and 3.1.1.
- Transport via TCP, TLS or TLS_CERT.
- Authentication by username or client certificate.
- Available on the BASE-6 generation base unit, as part of firmware version 10 or higher.
