2GIG GC3 or GC3e: Properly Replacing a Bad Sensor

In this video, Jarrett from Alarm Grid shows you how to properly replace a bad sensor on a 2GIG GC3 or 2GIG GC3e. This process involves clearing the wireless zone entirely and then reprogramming the zone from scratch. A user will typically find that if they just delete the old Serial Number from the sensor being replaced and then enter the Serial Number for the new sensor, then they will get a "bypassed at device" error for the zone.

Any user who needs to replace a sensor on their GC3 or GC3e should clear out the zone and then reprogram the zone from scratch. While this does require more time, it will save you trouble by not encounter the "bypassed at device" status. This condition results in the sensor being ignored by the system and the system not taking any action when the sensor is faulted. While the "bypassed at device" condition is what we have seen, it's possible that other abnormal zone status messages or zone responses may appear when a sensor is not properly replaced. After replacing a sensor, you should test the newly enrolled one to ensure that the system responds in the proper manner.

Both the 2GIG GC3 and 2GIG GC3e follow the same general programming steps. But there are some things to keep in mind when programming sensors. First, you will need the Installer Code for the system to enter programming so that you can delete zones and set up new ones. The default Installer Code on a GC3 or GC3e is 1561, and we recommend keeping the code at the default so that you do not become locked out of programming later on. Second, remember that using the correct Equipment Code is extremely important when you are enrolling 2GIG eSeries Encrypted Sensors on a 2GIG GC3e. Failing to use the proper code can result in issues.

https://www.alarmgrid.com/faq/how-do-i-properly-replace-a-bad-sensor-on-my-gc3-or-gc3e

http://alrm.gd/get-monitored