Not all drivers have devices with an AlarmDeviceExt (Alarms)—notably, this exists only if the driver protocol (or device) provides for local (native) alarming. Currently, only a device component under a NiagaraNetwork (station), BacnetNetwork, or ObixNetwork has a child Alarms extension.

Alarms extension properties in devices NiagaraStation and BacnetDevice (drivers NiagaraDriver and Bacnet, respectively) specify how alarms from that device are mapped into the station’s own alarm subsystem, plus provide status properties related to alarm sharing. Unlike some other device extensions, there are no special views, nor does the extension contain other special components.

The Alarms extension under an ObixClient device (ObixDriver) is modeled differently, where properties specify the oBIX “watch” interval and URI, and one or more child ObixAlarmImport components specify the available “alarm feeds” from the represented oBIX server. Each alarm feed (ObixAlarmImport) has properties to specify the AlarmClass used to map into the station’s subsystem, as well as status properties. This Alarms device extension is unique in its special “Obix Alarm Manager” view, from which you typically discover, add, and manage alarm feeds. See the NiagaraAX oBIX Guide for more details.