For the past few weeks we have had a random loud beep maybe about a second in duration going off in our upstairs hallway. It is very random and in the middle of the night or early morning. It appears to come from around my children’s rooms where we have a PowerG CO detector, and a PowerG smoke/heat detector. I recently replaced the batteries in these sensors and thought that maybe fixed the issue. This morning at about 6:20- 6:30 AM we had another single one second beep that woke my children up. I checked the detectors and the lights are all green. Additionally the alarm tone only happened a single time and never repeated. Some times it is a series of 3-4 long beeps and then nothing. Both devices still have about 2 years until they need replacing.
Any ideas as to what this could be?
I am assuming it is an issue with one of these given that there are no other noise emitters here except our non-alarm.com connected wired smoke detectors, which set off all others if one goes off. None of those show as latched or have anything but green leds on them. We are obviously struggling with this as I have young scared crying kids coming into my room whenever this random alert happens.
Note: Later today I am going to put my system in test and clean out both the CO sensor as well as the smoke/heat detector. I have heard that dust and sometimes bugs in the detection chambers can cause this issue.
For the past few weeks we have had a random loud beep maybe about a second in duration going off in our upstairs hallway. It is very random and in the middle of the night or early morning.
Is this always in the overnight/ early morning period? Do you recall when this first began?
Is this sound ever the temporal 4 alarm sound, or something different?
This morning at about 6:20- 6:30 AM we had another single one second beep that woke my children up. I checked the detectors and the lights are all green.
Not showing anything in history around that time aside from automation triggers. Nothing from any life safety sensors.
The PG9936 will do 2 loud alarm beeps with red LED flashes when Testing the sensor. This is done by holding the Test button down on the unit for 2 seconds.
Otherwise, The PG9936 smoke doesn’t have any documentation regarding long beeps. It does chirp briefly once every 48 seconds for a variety of onboard issues including Low Battery, Dirty Sensor, and Detector Trouble. These would all be accompanied by a a flashing Yellow LED.
Similarly, the PG9933 carbon has temporal alarm and a couple short beeps when testing which requires the test button to be held.
Much like the smoke, there are a some chirps with Yellow LEDs that signify a variety of onboard issues.
None of the documented chirps seem to match what you are describing.
It happened again this morning a little before 9AM EDT. It was about a 1 second beep, the same beep that would repeat over and over for an actual alarm. I put the system into test and used a duster to blow out the chambers in both the smoke and the CO sensors. Since then, I have not heard a repeat, though I would expect it in earlier hours based on when it happened. For good measure I also replaced the batteries in the smoke again, since they had been replaced with old stock. I can say that before any of the cleaning and replacing we did not have any amber or red lights.
As far as my inter-connected smokes, those are mostly First Alert Model: SC9120B. Those were manufactured Nov 16, 2018. There are no red or amber lights on those, none of them are latched from a previous alarm.
You may need to isolate one of the devices to determine if it is the cause. I would refrain from Removing the sensor from the base to do this, as this will cause a tamper, which will alert until it has been resolved.
Does anything show at the panel, in the Alerts/Alarms section of panel programming? Click on the Surety logo located on the top right hand corner of the screen, then select Alerts and Alarms. Any onboard alerts regarding those devices, at the times specified?
i t happened again this morning a little before 9AM EDT
Nothing in history related to either device, outside from tampers around 930 AM. Did you take them down around that time?
Typically if the batteries are low, you’ll get a message through the system, in addition to the chirp/flash combo on the unit itself.
As far as my inter-connected smokes, those are mostly First Alert Model: SC9120B.
Based on documentation those chirp for low battery and beep 3 times, pause, beep 3 times for alarms and during testing.
If needed, you can remove one of the PowerG life safeties from panel programming to avoid potential alarm issues until you are able to identify.
If the panel is showing normal and no trouble history, it may be either your First Alert smoke detectors or another device nearby
I would double check the pigtail on the smoke near the area where you are hearing the smoke. If the pigtail is not connected to the smoke correctly, it can cause the smoke detector to chirp.
I would also make sure you don’t have any other battery powered CO detectors.
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. I replaced them again, and this morning it started beeping again, with a yellow light flashing. I have taken it out of service and removed it from my panel. This detector is going bad. What makes this terrible is that it is only a couple of years old, and the expiration date on the side is: July 18, 2033.
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.
I am seeing quite a few reports of the same thing with the PG9936. I don’t think I want to purchase another one, given how unreliable they seem to get just a couple of years after purchase. Instead, I was interested in the Firefighter SLX-AD-T3, since I already have the whole house blanketed with wired smoke and CO detectors.
This brings up a question/concern. One of these wired smoke/co detectors s in the kitchen, and sometimes my wife or kids will burn some food causing that alarm to go off, and the others to subsiquently follow, since they are interconnected. Generally, the alarm will only go off for like 20 seconds as we waft the smoke away. 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?
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:
Two Way Voice (if enabled)
Premise Number (if provided)
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: