Jasper Sources
Novant supports native integration with Jasper, the protocol used to communicate with Niagara systems. This allows you to read and write data points from Niagara-based building systems using standard Jasper connections. This guide covers how to configure Jasper sources, define system addresses, and map point identifiers for use in your projects.
Credentials
Jasper sources require a Password credential to authenticate and authorize requests to Niagara. Create this user account directly in the Niagara system, and ensure it has the appropriate permissions to access the points and devices you intend to use.red permissions to access desired sources.
Sources
The address format for Jasper sources is:
[tls:]<ip>:<port>/<id>
10.0.0.5:80/54d # no prefix implies HTTP
tls:10.0.0.5:443/621 # tls prefix requires TLSPoints
The address format for Bacnet points is:
<type>.<suffix>Examples:
av.ZoneTemp
bo.FanStatusThe supported point types for Jasper, along with their type prefix:
| Prefix | Niagara Type |
|---|---|
ai.* |
NumericInput |
ao.* |
NumericOutput |
av.* |
NumericWritable |
bi.* |
BooleanInput |
bo.* |
BooleanOutput |
bv.* |
BooleanWritable |
ei.* |
EnumInput |
eo.* |
EnumOutput |
ev.* |
EnumWritable |
The full point address (<type>.<suffix>)
must be unique within a given Jasper source. The suffix itself is opaque
to Novant—it can follow any convention you choose—as long as the
combination of type and suffix forms a unique identifier. By convention,
fragments within the suffix should be dot-separated (.) for
clarity and consistency.