Random long beep or multiple beeps in the middle of the night (Possibly from CO or smoke detector)

The problem turned out to be my PowerG smoke detector (PG9936). I replaced the
batteries in it, and one week later, it started to have error beeps and an indicator that the batteries were low.

What was the specific color and flash pattern, how many seconds between each flash?

If the batteries are low, you may need to remove the bad battery, wait 2 minutes, then replace with fresh batteries of the type recommended by the manufacturer, and within the printed date code.

I am going to order another smoke detector to replace this one. Are there any better models than this? This was a very short time for it to go haywire.

The panel on file is compatible with 319.5MHz and PowerG sensors. There are only two smokes that work:

The Qolsys IQ Smoke (319.5Mhz) and the DSC PowerG PG9936.

The Firefighter SLX-AD-T3 Audio Detector (319.5MHz) can be leveraged to monitor interconnected smokes. It does not work with carbon.

I am concerned that the FD will be called and come out based on this. Is there a way for verification to happen before sending the FD?

Fire w/ Verification (Two Trip) is an option. With the Qolsys panel, Fire w/ Verification is a global setting, not an individual sensor setting. It is enabled through the Siren and Alarms section of panel programming.

  • Settings > Advanced Settings > Enter Dealer or Installer code > Installation > Siren and Alarms.

Regarding dispatch on fire alarm signals, the procedure is:

  1. Two Way Voice (if enabled)
  2. Premise Number (if provided)
  3. Cell Contact(s)

If desired you can enable Two-Way or include a premise number (landline) if available. Any contacts listed above the Police/Fire line in your Professional Monitoring tab will be called prior to dispatch.

Steps on how to update contacts can be found here: