novantMercuryExt icon


Novant Mercury Connector

Registered StackHub users may elect to receive email notifications whenever a new package version is released.

There are 0 watchers.



The NovantExt implements connector support for the Novant Mercury legacy platform.

API Keys

Access to Novant devices are built around API keys. It's recommended you create a specific API key just for SkySpark access.


Each connector in SkySpark maps 1:1 to a Novant device. To create and map a new connector:

dis: "My Device"
apiKey: "***********"
novantMercuryDeviceId: dv_xxxxxxxxxxxxx
novantMercuryHisInterval: "15min"

Where apiKey is the key you generated from the Novant platform, and novantDeviceId is the Novant device id for the device to connect.


Current values are configured using the novantMercuryCur tag on a point. Writable points use the novantMercuryWrite tag. Likewise histories use the novantMercuryHis tag. The value of these tags maps to the point ID for the Novant device, which will be in the format of "p{id}".

dis: "My Point"
novantMercuryCur: "p15"
novantMercuryWrite: "p15"
novantMercuryHis: "p15"
equipRef: @equip-id
siteRef: @site-id
kind: "Number"
unit: "kW"

The SkySpark write level will be carried over directly into the downstream I/O device under the Novant gateway. For protocols that support priority, like Bacnet, this means the Bacnet priority array level matches the SkySpark write level. For protocols that do not support priority (such as Modbus) this value is ignored.


The Novant connector supports learning. Once a connector has been added, you can use the Site Builder to walk the device tree and add any or all points.

Published by Novant

Packages by Novant

Free packages

Package details
Build date4 months ago
on Mon 11th Mar
Requirements SkySpark v3.1
Depends on
File namenovantMercuryExt.pod
File size27.04 kB
SHA1 64d1eff1dca932f5e18f3942f2347561879b1142
Published by
NovantDownload now
Also available via SkyArc Install Manager
Pod File