By the SNMP Monitoring team · Reviewed July 2026
Bringing smoke and fire signals into SNMP is genuinely useful — the on-call team gets the same early visibility they have for a leak or a hot aisle, and can start pulling load or dispatching someone before things escalate. But there's a line that has to be drawn clearly before anything else: SNMP monitoring supplements a certified fire system; it never replaces one. A script polling a relay is not life-safety equipment. With that boundary firmly set, an SNMP-visible fire signal is a valuable early-warning overlay on top of the real, code-compliant detection and suppression that protects the room and the people in it.
This is the how-to. Parent: environmental monitoring. Siblings: water & leak, door contact.
Safety boundary first
Say it plainly, because it's the most important part of this page: your SNMP monitoring must not be the sole protection against fire. A proper fire detection and suppression system — designed, installed, and certified to the applicable code and standards (NFPA and your local authority having jurisdiction) — is a legal and life-safety requirement, and it operates independently of your monitoring stack.
- SNMP gives operational early warning to the ops team; it does not evacuate people or discharge suppression.
- The certified system is the life-safety layer; SNMP is an overlay on top of it.
- If your monitoring is down, the fire system must still detect, alarm, and suppress on its own.
Treat the SNMP path as "so ops finds out fast," not "so the building is protected." Design accordingly, and never let a monitoring project become an excuse to under-spec the real system.
| Aspect | Certified fire system | SNMP monitoring overlay |
|---|---|---|
| Role | Life-safety — detect, alarm, suppress | Operational early warning for ops |
| Independence | Works with monitoring down | Depends on gateway and network |
| Authority | NFPA / local code compliant | Observes the panel's relay output |
How smoke/fire reaches SNMP
With the boundary set, the mechanism is the same dry-contact pattern as other discrete sensors. A smoke or heat detector — or, more often, the alarm relay on the certified fire panel — presents a dry contact to an SNMP environmental gateway. The gateway publishes that contact as an integer enum in its vendor MIB under 1.3.6.1.4.1: one value normal, another alarm.
So you're usually not reading a smoke detector directly. You're reading a relay output from the fire panel that the panel provides precisely so external systems can observe its state without interfering with it. That's the correct, non-invasive way to bring the signal into monitoring. Exact OIDs are vendor-specific — read the panel/gateway MIB, don't invent leaves, and confirm the enum polarity so "alarm" isn't mistaken for "normal."
Reading the alarm state
Poll the gateway's fire/smoke object (vendor placeholder arc):
snmpget -v2c -c <RO_string> <gateway> 1.3.6.1.4.1.<vendor>.sensors.smoke.1
enterprises.<vendor>.sensors.smoke.1 = INTEGER: 1
As with any dry contact, 1 means nothing until you check the vendor MIB. If it defines 1 = normal and 2 = alarm, this is a clear state; if it's inverted, 1 is an active alarm. Load the MIB so the value resolves to a name like normal or alarmActive, and verify the polarity during commissioning by testing the panel's relay — never guess it. <RO_string> and the <vendor> arc are placeholders; keep live community strings out of committed scripts.
Early-warning systems (VESDA)
Some facilities go beyond spot detectors with aspirating smoke detection — VESDA-style systems that continuously draw air samples through a pipe network and can detect smoke at very low concentrations, well before a conventional detector would trip. For monitoring, the key points:
- These systems typically expose relay outputs at staged alert levels (e.g. an early "alert" stage before a full "fire" stage), which map neatly onto SNMP enum states.
- Relaying those stages into SNMP lets ops react to an early stage — investigate a warming PSU or a smoking fan — before it becomes a fire.
- They are still part of the certified life-safety system; SNMP just observes their relays.
Aspirating detection is where the "early warning" value of SNMP monitoring is highest, because the underlying system is designed to catch trouble early in the first place.
Critical alerting & escalation
A fire signal is the highest-priority event you'll monitor. Escalation logic:
- Route the alarm to page immediately — P1, phone/push, no delay window.
- Pair polling with a trap so the gateway pushes the alarm instantly; back it with a poll in case a trap is lost. See traps vs polling.
- Escalate to a named on-call and a secondary if unacknowledged within minutes — a fire alert must never sit silently in a queue.
- Include the location in the alert so responders know which room/row, and monitor the gateway's own reachability so a dead probe can't hide an alarm.
- Remember the SNMP alert is for ops response; the certified system independently handles alarm and suppression.
Route, escalate and de-duplicate through alerts — but give this signal the shortest path and the loudest channel you have.
Reference
This is the smoke/fire how-to. The environmental section of the full sensor index lists related objects at all sensors. Siblings: water & leak, door contact. Definitions at glossary.
Frequently asked questions
Can SNMP detect smoke or fire?
Indirectly, yes. A smoke/heat detector or the fire panel's alarm relay presents a dry contact to an SNMP environmental gateway, which reports the state as an integer enum under 1.3.6.1.4.1. You poll or receive a trap from the gateway and alert on the alarm state — but this is an operational overlay, not a substitute for the certified system.
Does SNMP replace a fire alarm?
No — absolutely not. SNMP monitoring supplements a code-compliant fire detection and suppression system; it does not replace it. The certified system is the life-safety layer that must detect, alarm, and suppress independently of your monitoring. SNMP just gives the ops team early visibility on top of it.
What is VESDA?
VESDA refers to aspirating smoke detection — a system that continuously samples air through a pipe network and detects smoke at very low concentrations, earlier than a conventional detector. Such systems usually expose staged relay outputs that can be relayed into SNMP as enum states, making them ideal for early-warning monitoring.
How do I get an instant fire alert?
Pair polling with an SNMP trap so the gateway pushes the alarm the instant the panel's relay trips, and route it as a P1 to a paging channel with escalation to a named on-call. Back the trap with a fast poll for durability, and monitor the gateway's reachability so a dead probe can't mask an alarm.
Key takeaways
- SNMP supplements, never replaces, a certified fire system — it's an ops overlay, not life-safety.
- Smoke/fire reaches SNMP as a dry-contact/relay enum in a vendor MIB under
1.3.6.1.4.1— usually the panel's relay output. - Read the vendor MIB and test the relay for polarity; never guess which integer means alarm.
- VESDA aspirating systems expose staged relays — the highest-value early-warning source.
- Treat a fire signal as P1: instant trap + poll, immediate page, escalation to a named on-call.
- Full index: all sensors; an off-box external check via external monitoring still pages you if a room-wide incident hits.