Never assume a repeated activation is false until the first event and area have been checked
Follow the premises fire procedure, capture the panel information before reset and use formal impairment controls where detectors or zones need to be isolated for investigation or building work.
MOST LIKELY CAUSES
Start with the first event and environment
Symptom variations Match the exact timing, location and environmental pattern. ⌄
- Same address appears repeatedly
- Alarm occurs at similar times
- Detector value runs high
- Activation follows weather or plant operation
- Replacement head does not solve the issue
Safe first checks Checks for authorised site staff before engineering work. ⌄
- Treat the activation as genuine until the area is checked.
- Record the first zone, address, device and time before reset.
- Check for steam, dust, aerosols, insects, water or nearby work.
- Review whether the same device or time pattern repeats.
- Do not leave detectors covered, removed or disabled without formal controls.
Step 1 — Confirm it is always the same device Treat every activation as genuine until the first event and cause are confirmed. ⌄
Use the event log rather than memory or location assumptions.
Step 2 — Inspect the local environment Treat every activation as genuine until the first event and cause are confirmed. ⌄
Check vents, steam, dust, insects, sunlight and nearby processes.
Step 3 — Check maintenance and replacement history Treat every activation as genuine until the first event and cause are confirmed. ⌄
Recurring events after replacement may point to siting, base or wiring.
What the activation usually means How this unwanted-alarm pattern develops. ⌄
When the same detector repeatedly triggers, the cause is usually local: contamination, airflow, steam, insects, temperature change, poor siting, unstable wiring or a failing device.
Engineer diagnostic sequence Competent-person checks after the site information has been captured. ⌄
- Trend analogue values over time.
- Inspect the base, terminals and loop communication.
- Substitute device and base separately where authorised.
- Review detector type and sensitivity assignment.
- Assess whether the detector location should be redesigned.
Information and equipment needed Useful items for accurate investigation. ⌄
- Panel event log and first-event record
- Detector type, address and location
- Recent work, cleaning and weather history
- Manufacturer diagnostics and analogue values
- Approved cleaning and functional test equipment
Parts that may be involved Components commonly associated with this problem. ⌄
- Replacement detector
- Detector base
- Address programmer
- Loop cable or terminals
- Alternative compatible detector type
When immediate action is required Conditions that should trigger escalation or an impairment plan. ⌄
- The activation source cannot be confirmed.
- The same detector or area repeatedly causes evacuation.
- Building work is contaminating multiple devices.
- Water ingress, cable damage or external equipment is involved.
- Detectors are being covered or removed without control.
- The system cannot be returned to normal reliable operation.
Frequently asked questions Common unwanted-alarm questions. ⌄
Can a detector simply be moved away from steam or cooking?
Not without reviewing the design, coverage and fire strategy. Any relocation or detector-type change should be controlled and documented.
Should a detector that keeps triggering always be replaced?
No. The environment, base, wiring, type and siting should be checked as well as the detector head.
Can detectors be covered during building work?
Only under a managed impairment procedure with suitable temporary measures and prompt removal of covers when work stops.