Every device. One tool. Pay once. Modbus · BACnet · Siemens S7 · one-time licence · also from us: ModbusManager ↗
// event notifications · acknowledgealarm · geteventinformation

BACnet Alarms
from the Devices Themselves

Controllers raise their own alarms — a supply air temperature out of range, a dirty filter, a pump fault — and send them to whoever is in their Notification Class. BACManager receives those event notifications, asks each device for what is not normal, and acknowledges an alarm in the device with the operator's name. The device's alarms stand in the same list as BACManager's own alarms on values, with the same history, sound and notifications.

Download free trial Get the alarms sent here

Windows 10/11 · one-time license · 14-day trial

// one list

The device's alarms beside your own

Each row says where it came from: device or BACManager. A device alarm shows the device, the object, the priority, the transition and the device's own message.

BACManager Alarms tab: three alarms from device AHU-1 (2101) marked device: Pump_Fault BV 12 priority 20 change-of-state normal to fault, Supply_Air_Temp AI 1 priority 40 out-of-range normal to high-limit with value 29.4 and the message Supply air above 28 °C, Filter_Status BI 7 priority 160 normal to offnormal; one BACManager alarm Office temperature; the Device alarms box asks each device every 30 s, priority 0 to 127 critical, operator name J. Smith, AHU-1 3 in alarm
Priority 20 and 40 are critical (red), 160 a warning; the device's own message, “Supply air above 28 °C”, comes with the alarm
// how they arrive

Told at once, and asked every 30 seconds

WayBACnet serviceWhen it matters
The device tellsConfirmed / UnconfirmedEventNotification — BACManager confirms the confirmed onesthe alarm appears the moment it happens
BACManager asksGetEventInformation, or GetAlarmSummary on older devices, every 30 s (or as you set)alarms of a class that does not list this computer, and alarms already active when BACManager started
AckAcknowledgeAlarm, with the operator name as its sourcethe device, and anyone else watching it, sees who acknowledged

BACnet priorities run from 0 (most urgent) to 255. You set up to which priority an alarm counts as critical — 0…127 by default, everything above is a warning. The operator name is asked at the first Ack and then kept; a Runtime machine asks at every start. The alarm history records who acknowledged what, and when.

// notification class

Send alarms to BACManager

A device sends its alarms only to the recipients in its Notification Class. Open the class on the BACnet tab and press 📨 Send alarms to BACManager: after a question, BACManager adds this computer to the class's Recipient_List.

Dashboards

A dashboard Alarm List and the Annunciator lamp block acknowledge device alarms the same way — the Ack goes to the device.

E-mail, Telegram, webhook

Device alarms go out through the same notifications as BACManager's own, also with the window closed and on a Runtime machine.

MQTT

The gateway's Publish alarms sends every alarm, device alarms included, to your broker — see BACnet to MQTT.

Adding a recipient writes to the controller, which is why BACManager asks first. On a site with a BMS, check with whoever runs it: some sites keep the Recipient_List under change control. Asking every 30 seconds needs no change in the device at all.

// questions

BACnet alarms — FAQ

Can BACManager receive BACnet event notifications?+
Yes. Confirmed and unconfirmed event notifications from a device appear in the Alarms tab at once, marked device, with the object, priority, transition and the device's message. Confirmed notifications are confirmed.
Can I acknowledge a BACnet alarm in the device?+
Yes. Ack sends AcknowledgeAlarm to the device with the operator name as the acknowledgement source, and the alarm history records who acknowledged.
What if the device does not send its alarms to my PC?+
BACManager also asks each device every 30 seconds with GetEventInformation (or GetAlarmSummary on older devices), so active alarms appear even when this computer is not a recipient. To get them at once, add this computer to the Notification Class with Send alarms to BACManager.
Which alarms count as critical?+
By default priority 0 to 127 is critical and anything above is a warning. You can change the limit under Device alarms on the Alarms tab.
Do device alarms work on BACnet MS/TP and BACnet/SC?+
Yes. They work on every datalink BACManager speaks: BACnet/IP, MS/TP and BACnet/SC.
Which version reads device alarms?+
BACManager 1.4.9 and newer, included in the standard $149 one-time license.

See the alarms your controllers raise

Download the free trial, discover the site, and the devices' active alarms appear within 30 seconds. No credit card.

Download free trial See pricing

Windows 10/11 · $149 one-time