Annual Test Finds a Detector That Will Not Alarm but Passes the Panel
During an annual inspection of a 12-year-old addressable system in a hotel, you test 60 smoke detectors with canned smoke. Fifty-nine alarm and report correctly at the panel and at the remote annunciator. One detector in a guest corridor does not produce an alarm at the panel when smoked, but the panel shows the device as 'normal' and the detector's LED blinks. You re-smoke it twice with the same result. The panel event log shows no trouble for that address in the past year. The detector is on a loop with 40 other devices, all of which test fine. The building is fully sprinklered and the corridor is a means of egress. The owner asks whether the detector can be left in service until the next annual test because 'it's probably just a dirty head and the panel says it's fine.'
1. Interpret the symptom: device normal and blinking, but no alarm on smoke. What are the plausible causes and how would you isolate them?
Read the worked answer
A device that reports normal and blinks (indicating it is communicating and powered) but does not alarm on smoke is a detector-level or address-level problem, not a loop wiring problem - the other 40 devices on the loop are fine.
Plausible causes:
- Obstructed or contaminated sensing chamber - dust, lint, or insect debris can prevent the chamber from reaching alarm threshold while the device still communicates.
- Detector electronics/calibration drift - the head is at end of useful life or has failed its sensitivity window.
- Misaddressed or mismapped device - the physical detector may not be the device the panel thinks is at that address, so smoking it alarms a different address. Cross-check the address and the as-built mapping.
- Detector base/contact problem - poor head-to-base connection can leave it communicating but unable to report alarm.
Isolation steps:
- Swap the head with a known-good head of the same model and re-test. If the known-good head alarms, the original head is defective. If it still does not, the base or address is the problem.
- Verify the programmed address matches the physical device and the floor plan.
- Check the panel's sensitivity reading for that device, if available.
2. The owner wants to defer. What is your recommendation and what must happen before the system is returned to service?
Read the worked answer
Do not defer. A detector in a means-of-egress corridor that will not alarm is a failed life-safety device and must be corrected before the system is returned to normal service.
Reasoning:
- The panel showing 'normal' does not mean the detector works. Supervision confirms communication and power, not detection. A device that communicates but cannot alarm is exactly the failure mode annual functional testing exists to catch.
- The corridor is a means of egress in an occupied hotel. Leaving a known non-functional detector in service is not a judgement call in the owner's favor.
Before return to service:
- Replace or repair the detector (new head, or new base/head as isolation shows), then functionally test it with smoke and confirm alarm at the panel and annunciator.
- Verify the address and mapping so the annunciator identifies the correct location.
- Record the failed device, the corrective action, and the retest in the inspection report.
- Consider whether the finding suggests a broader sensitivity/age issue - at 12 years, review the detector replacement/cleaning schedule for the rest of the loop.
The correct posture: a known failed detector is corrected now, not at the next annual.