*** System Sensor Cosmo 2W senses CO and...

[Mp333]

So one of the System Sensor Cosmo 2W near kitchen goes into Alarm mode for Carbon Monoxide. The blue light on the Cosmo 2W was flashing. I turned the M1G off/on and still kept going on. I swapped with another Cosmo 2W and it followed the cosmo 2w.
I wasn't sure if there was CO presence and to be safe called the Fire Dept. They confirmed there was no CO presence. I am assuming I need to replace the Cosmo 2W, unless I am missing something.
 
Any help would be appreciated.
Thanks
 

 

[ano]

I know nothing about this device, but many CO detectors contain a timer, and after a set length of time they require replacement. Typically 7 or 8 years. Is it about that old?  If so that's a likely cause.

 

[Del91574]

There was a recall on those units about 3 years back. Bad batch if I remember.
 
Could also be a bad module hitting the unit.

 

[TrojanHorse]

Links to the recall:
https://www.cpsc.gov/Recalls/2015/System-Sensor-Recalls-Combination-Carbon-Monoxide-and-Smoke-Detectors/
 
http://www.systemsensor.com/en-us/news/Pages/COSmokeSafety.aspx
 
This will sound odd and it's maybe not the same problem you're having, but about a year ago I had the same unit giving me a CO Trouble shortly after installation.  I opened the detector and found a gel-like substance on the contacts of the unit.  No idea how it got there (it wasn't me!  I'm certain it must have arrived this way).  Cleaned it up, tested again and it's fine now.  With the new year I should probably test all of my units again with the smoke-in-a-can and CO-in-a-can.

 

[Mp333]

The recall doesn't cover my unit. I need to check the others. However they are two years old and covered under 3yrs warranty.
Just picked up the replacement and will connect it when I get home.

 

[Mp333]

She's in and it works. No more false Alarm.
 
Thank you all.

 

[Mp333]

BTW. What is the protocol for CS if they receive the CO Alarm? I would imagine they would contact the residence....
I never got a call from CS.

 

[Del91574]

CO should be a direct FD dispatch followed by a courtesy call. Should not be able to cancel, just like a FA signal.
 
Might be a programming error on your system if they did not get a signal, assuming you can see it in the log. Either bad ZT or system template would be my first guess.

 

[Mp333]

DEL. I do see it in the ElkRP log.
 
CO Zone is setup for def - 17
Fire def - 10
 
I have also attached the Zone RC, Log & CS log. For some reason it will only show 20 incidents.

 

[Del91574]

First, your garage fire is wrong ZT.
Second, you do not have restorals enabled on your system.
 
Are you CID or SIA?
 
I would look at swinger shutdown on your system. That would be something I'd consider. Need to see how many signals went through prior.
 
The CS data doesn't tell the picture here. You need the raw data to see if it was an actual trouble qualifier on the RC.
 
The issue is you're defining the signal as an alarm, which the panel did not report it as. The system and detector reported a trouble condition. Different item.
 
Without knowing more, looks like the response protocol was borked. Appears they let your dealer know however. Should have also called you on it.
 
That said, both a fire trouble and CO trouble should make an attempt to contact the premise first, followed by a FD dispatch, mainly for liability purposes.

 

[Mp333]

DEL,
 
First, your garage fire is wrong ZT.
So I believe this needs to be Set to 10-FIRE instead of 21-HEAT and type 0 (EOL)
 
Second, you do not have restorals enabled on your system.
I did change to 01 instead of 00 in Restorial Pulse. Same as FIRE.
 
Are you CID or SIA?
Not sure if I am looking in the right place...Telephone 1 is setup for IP and Telephone 2 for Serial Expander. I do have the Uplink 4500EZ.
 
I would look at swinger shutdown on your system. That would be something I'd consider. Need to see how many signals went through prior.
I have attached pix for the Cutout Timer.
 
The CS data doesn't tell the picture here. You need the raw data to see if it was an actual trouble qualifier on the RC.
I imagine I can get that from the CS?
 
The issue is you're defining the signal as an alarm, which the panel did not report it as. The system and detector reported a trouble condition. Different item.
Not sure where do Correct that info?
 
Without knowing more, looks like the response protocol was borked. Appears they let your dealer know however. Should have also called you on it.
hat said, both a fire trouble and CO trouble should make an attempt to contact the premise first, followed by a FD dispatch, mainly for liability purposes.
I am trying to find out more on this.
 
Thank you for your help.

 

[Del91574]

DEL,
 
First, your garage fire is wrong ZT.
So I believe this needs to be Set to 10-FIRE instead of 21-HEAT and type 0 (EOL)

YES

Second, you do not have restorals enabled on your system.
I did change to 01 instead of 00 in Restorial Pulse. Same as FIRE.

Entire system should have restoral reporting enabled

Are you CID or SIA?
Not sure if I am looking in the right place...Telephone 1 is setup for IP and Telephone 2 for Serial Expander. I do have the Uplink 4500EZ.

Your installer or CS needs to answer this

I would look at swinger shutdown on your system. That would be something I'd consider. Need to see how many signals went through prior.
I have attached pix for the Cutout Timer.

This is in zone attributes

The CS data doesn't tell the picture here. You need the raw data to see if it was an actual trouble qualifier on the RC.
I imagine I can get that from the CS?

Yes. Also completes the picture with the format the system is sending

The issue is you're defining the signal as an alarm, which the panel did not report it as. The system and detector reported a trouble condition. Different item.
Not sure where do Correct that info?

Your system did not report an actual alarm, only a trouble condition. Was not an "actual" alarm event, only superficial reporting. Trouble conditions illicit different protocol as far as the CS is concerned. In the case of a CO trouble, if wired correctly, indicates either the detector lost power or the detector is end of life.

Without knowing more, looks like the response protocol was borked. Appears they let your dealer know however. Should have also called you on it.
hat said, both a fire trouble and CO trouble should make an attempt to contact the premise first, followed by a FD dispatch, mainly for liability purposes.
I am trying to find out more on this.
 
Thank you for your help.

 

[Mp333]

DEL, 
 
Garage Heat is now set for Zone Def 10, however the Type has only one option - Type 5 Fire/4-Wire Smoke/RF. Also it gives me a Violated under Status and displays Fire Trouble for that zone. There is no EOL on the SS 5601P.  
 
The entire Zone RC Restoral pulse is set for 01.  
 
I believe the system is sending CID. I will confirm...  
 
The CO zone does not have swinger shutdown enabled. What zones should have Swinger shutdown enabled?  
 
Sorry, I am confused... How do I change the reporting method to Alarm instead of trouble. Also the Cosmo 2W was defective. May be the reporting was correct as a trouble and not an alarm?

 

[Del91574]

You need to correct the heat detector wiring. All fire circuits require EOLR's.
 
The reporting of the trouble condition was correct. The detector was a fault, not alarm.

 

[Mp333]

DEL,
 
All set with the EOL for Heat Detector. I did talk to System Sensor during the installation of the 5601P and I am 100% sure I installed the way I was advised to...
 
Thank you again.