How to Troubleshoot a FireX 120-5388 Smoke Alarm

Written by kefa olang
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to Troubleshoot a FireX 120-5388 Smoke Alarm
Troubleshooting your smoke detector can improve safety. (Jupiterimages/Comstock/Getty Images)

The FireX 120-5388 smoke alarm which uses AC power and a battery backup requires regular troubleshooting and maintenance to function properly. Essential for both homes and offices, FireX 120-5388 alarms are interconnected to sound off simultaneously. Inspecting and cleaning your smoke alarms not only heightens the sensitivity, but also decreases the chances of false alarms and promotes longevity. Regular maintenance steps are both simple and necessary to improve safety.

Skill level:

Other People Are Reading

Things you need

  • Vacuum cleaner
  • Damp cloth

Show MoreHide


  1. 1

    Make sure your FireX 120-5388 smoke alarms are connected to AC power if they are not working.

  2. 2

    Remove your FireX 120-5388 smoke alarm from the wall if you hear a constant beeping sound about once a minute.

  3. 3

    Open the battery compartment and remove the old batteries. Insert new batteries. FireX 120-5388 smoke alarms use 9 Volt alkaline batteries.

  4. 4

    Remove your unit from the wall if it sounds unwanted alarms. Using a hose attached to a vacuum cleaner, vacuum all sides and cover of your smoke alarm. Vacuum all the vents to remove dirt and debris from the sensing chamber.

  5. 5

    Remove the batteries. Using a damp cloth, clean the smoke alarm cover. Do not open the smoke detector or attempt to clean the inside.

  6. 6

    Press the test button on your smoke alarm for at least five seconds. The alarm horn should sound. If the alarm does not sound, make sure the batteries are inserted correctly.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.