Tamper works, but no fire alarm upon test of new detector?

Support
1

I just bought (Surety Order #946868 on Sept 7 2026) a 2GIG 345S Wireless Smoke/Heat/Freeze Detector and paired it to my 2GIG GoControl 3 panel. The panel has the latest GC3 3.2.6 firmware (gc3-3.2.6.6770-prod.2gig).
For this detector, I’m using only two wireless zones, #12 & #13, where #12 is set to the detector’s Loop 1 for Smoke, and #13 is set to Loop 2 for Heat.
For both:
• Sensor Type is “09 - 24-Hour Fire”
• The detector’s “I/ON” dip switch is set to I for non-encrypted, and I’m using Equipment Code 1058.
• Serial Number was input using LEARN feature then confirmed with the device’s label.
• Smart Areas Assignment is S1 (like most of our other in-house sensors).
• Equipment Age is New
• Sensor Loop is as described above, Loop 1 or Loop 2.
• Voice Descriptors are set up, meaningful to us.
• Sensor Reports are Enabled.
• Sensor Supervised is Enabled.
• Sensor Chime is Voice Only (no doorbell tones).

As part of the intial install, and all my subsequent troubleshooting, I put our whole system on test mode via the website.
GOOD: The panel does detect when I tamper the detector.
GOOD: When I test the detector’s alarm (thru its giant button), the detector does indeed alarm.
BAD: The panel fails to alarm. The user’s manual (https://suretyhome.com/wp-content/uploads/2GIG-SMKT100-345-Manual.pdf) section on “Testing the Detector” implies that the fire alarm should come into the panel upon a button test leading to the class three-tones from the detector, so the lack of panel alarm to me is a TEST FAIL.

  1. Am I missing a configuration step somewhere?
  2. Or, is no panel alarm actually expected when locally testing these detectors (and if that is the case, where is it documented?)?

We tested a second similar detector, and again local at-detector alarms only, no panel alarm. The monitoring center checked for fire/smoke alarms on their end and reported none from today.

I’m suspecting a configuration issue with my panel OR major documentation fault with these sensors. Should I get some NFPA 72 Canned Smoke to determine which is the issue? Please advise.

2

I’m curious about this one too. Since the detector itself is sounding and the panel is correctly seeing the tamper, it seems like the wireless communication is at least partly working. The fact that you tested a second detector and got the same result makes me think it may be more than a faulty unit.

I’d probably double-check the loop assignments and equipment code first, especially since Smoke and Heat are being configured on separate zones. It would also be interesting to know whether anyone here has tested the 345S on a GC3 with the same firmware and can confirm whether the local test button is supposed to generate a panel fire alarm.

I wouldn’t jump straight to canned smoke until the configuration and expected test behavior are confirmed. Hopefully someone from Surety or another member who has this exact detector installed can clarify how the test is supposed to work.

3

Hello,

Happy to help!

We are continuing to investigate your case and will provide you with an update as soon as we have additional information.

Thank you for your patience and understanding.

4

How long are you holding down the test button? If I remember correctly, the detector will sound first but you may have to keep holding it down a while longer to make it transmit an alarm to the control panel. Try holding it down for up to 30 seconds.

Is there there any chance you switched the encryption mode on the detector after enrolling it? That’s another common gotcha.