How to Troubleshoot Chirps on a Kidde Smoke Alarm

Written by jon stefansson
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to Troubleshoot Chirps on a Kidde Smoke Alarm
Troubleshooting your Kidde smoke alarm keeps your home safe. (Michael Blann/Digital Vision/Getty Images)

Smoke alarms are the first warning for your family in the event of a fire in your home. Keep your alarm in good working order to increase your chances of fighting a blaze or of escaping before it grows too large. Kidde smoke alarms chirp when there is a problem with the power supply, when the alarm has grown too old or when the sensors begin to malfunction. Troubleshooting these chirps helps identify the cause of the problem.

Skill level:
Moderately Easy

Other People Are Reading


  1. 1

    Change the batteries. Twist the alarm counterclockwise, disconnecting it from its ceiling mount and pry off the battery cover. Remove the three AA batteries or single 9V battery and install fresh replacements. Replace the cover and twist the alarm clockwise back onto its ceiling mount. Kidde alarms emit a chirp once every minute when the batteries are low.

  2. 2

    Move the unit to a new location; electrical interference could be causing problems with your alarm. Keep your alarm out of tight corners or the very top of pitched ceilings for best smoke detection. False alarms from cooking smoke may briefly trigger the alarm causing a chirping sound if the unit is poorly positioned.

  3. 3

    Replace the unit. Some Kidde smoke alarms chirp every 30 seconds once 10 years have passed from the initial start-up indicating the unit should be replaced. The "Alarm Replacement" chirps cannot be cancelled and are designed to encourage purchase of a replacement that will safely protect your home.

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.