Protocol Discovery

Discovery works differently depending on the protocol. This page covers what to expect when discovering devices and points across supported protocols.

BACnet

BACnet devices announce themselves on the network, so Explorer can automatically discover them without manual configuration. You’ll see each device’s instance number, name, and its full list of objects (analog inputs, binary values, etc.).

For protocol details, see BACnet Sources.

Jasper

Jasper sources connect to Niagara-based building systems. Discovery requires the Niagara system’s address and credentials. Once connected, Explorer can scan for available points exposed by the Niagara station.

For protocol details, see Jasper Sources.

Modbus

Modbus devices don’t support automatic discovery — you need to know the device address and register map ahead of time. Explorer lets you read specific registers to verify connectivity and confirm the data you expect is available.

For protocol details, see Modbus Sources.

OPC UA

OPC UA servers expose a browsable address space. Explorer connects to the server and lets you navigate its node tree, inspect variables, and view live values. You’ll need the server’s endpoint URL to get started.

For protocol details, see OPC Sources.

Kaiterra

Kaiterra sources connect to Kaiterra indoor air quality devices through the Kaiterra API. Discovery requires an API key. Once configured, Explorer can learn the points available from each device.

For protocol details, see Kaiterra Sources.