Announcement

Collapse
No announcement yet.

Napco Plug-in choking on Carbon Monoxide Detector

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • nfrobertson
    replied
    The Napco GEM-AUTOMATION EEPROM is what this plugin was developed to operate with. It is an HS3 port with some improvements over the original Napco plugin for HS2. I can't really comment on non-Napco devices and how the GEM-AUTOMATION or the apparently newer iBridge compatible EEPROM will respond with a non-Napco device. When I have some time to look further at this I may consider getting one of the Napco CO detectors and see if it works or has issues like you are seeing.

    Leave a comment:


  • Guest's Avatar
    Guest replied
    Hi,

    No actually they are Macurco CMS1's.

    http://homeappliance.manualsonline.c...urco/cms1.html



    I'm guessing maybe since these are not NAPCO products (though they are intended to be hardwired into a control panel) they might not respond to the:

    CMD_ZONE_DESC_LOW command?

    Leave a comment:


  • nfrobertson
    replied
    So based on your log, it appears that newer EEPROM on P3200 panels that are iBridge compatible may work with this plugin, at least in some capacity. I have to assume that much of the protocol implemented by the GEM-AUTOMATION EEPROM must be built into this version of the EEPROM - only a guess however.

    Is the CO detector you mention the FW-CO1224 like found at the link below?
    http://www.napcosecurity.com/images/...wolfCOspec.pdf

    Leave a comment:


  • Guest's Avatar
    Guest started a topic Napco Plug-in choking on Carbon Monoxide Detector

    Napco Plug-in choking on Carbon Monoxide Detector

    Plugin Version=3.0.0.5

    I have a Gemini 3200 with a very new EEPROM; it is the EEPROM that works with the Napco iBridge ethernet / zwave unit.

    Communication seems OK up until my 13th zone which is one of my Carbon Monoxide detectors:

    Specifically:

    Full Log:

Working...
X