My Concord4 Security Keypad is beeping. What do I do?

Created by Tim Schilling, Modified on Mon, 11 Dec, 2023 at 11:32 AM by Tim Schilling

If your Concord4 security keypad is beeping, it can indicate several potential issues. Here are some basic troubleshooting steps you can follow:

1. Check the Keypad Display:

  • Look for any error messages or codes displayed on the keypad.
  • If no error message is shown, proceed to the next step.

2. Analyze the Beeping Pattern:

  • Single Beep: This usually occurs during system disarming, status check, or sensor closing with chime enabled.It's not typically a cause for concern.
  • Two Beeps: This might indicate Chime Mode activation, announcing door or window opening when enabled.
  • Six Rapid Beeps Every Minute: This signifies a "trouble" condition requiring resolution. Press the "*" (STATUS) button or arm/disarm the system to silence the beeps for 4 hours, but they will resume if the issue persists.

4. Try Common Solutions:

  • Silence the Beeping: Press the "*" (STATUS) button or arm/disarm the system. The beeping will resume after 4 hours unless the problem is fixed. If the LCD display indicates a message, please remember the message and submit a ticket or call us at (614) 453-2003.
  • Arm/Disarm the System: Sometimes, a simple arm/disarm cycle can resolve temporary glitches causing beeping.
  • Adjust the Volume: Press and hold "*" + "0" until a steady tone sounds, then release. Press and hold "1" to lower the pitch or "2" to raise it.

5. Contact Customer Support:

If you've tried all the above steps and the beeping persists, it's best to contact customer support for further assistance. We can help diagnose the issue and provide specific troubleshooting guidance based on your system's configuration.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article