2GIG XCVR3-GC3 Posts

Update! 2GIG has corrected this issue on the Edge panel with a Firmware Update. You can read all about it here.

We have some rather unfortunate news for anyone hoping to use an image sensor with the 2GIG Edge. 2GIG has informed us that the system's only compatible image sensor, the 2GIG IMAGE3, will only function as a motion sensor when paired with the Edge. 2GIG says that they are working on a fix.

In order to enroll the 2GIG IMAGE3 Image Sensor with the 2GIG Edge in any capacity, a 2GIG XCVR3-GC3 Module must be installed inside the panel. This unit is what makes two-way communication between the 2GIG Edge and the IMAGE3 possible. Contrary to popular belief, installing the 2GIG XCVR3-GC3 inside the 2GIG Edge will not have any impact on the system's ability to support encrypted 2GIG eSeries Sensors.

However, even after you install the 2GIG XCVR3-GC3 and enroll the 2GIG IMAGE3, you will find that the IMAGE3 does not work as an image sensor as intended. Instead, the IMAGE3 will only behave as a standard motion detection sensor, and it will not transmit any captured photographs to Alarm.com. This effectively defeats the main purpose of the device, and you would really be no better off pairing an ordinary motion sensor with the Edge.

When we reached out to 2GIG for more information, we were informed that this behavior is not intentional, and a fix is being implemented to make the 2GIG IMAGE3 operate as a true image sensor when paired with the Edge. While it is believed that the fix will be applied as a firmware update for the 2GIG Edge, this is mere speculation, and it has not been confirmed. We also do not have an expected timeframe for when such a fix will be implemented.

Alarm Grid apologizes to anyone who was hoping to use image sensors with the 2GIG Edge at this time. We are just as hopeful as you are that 2GIG will make a quick fix to the problem so that image sensors may be successfully used with the system as intended. Stay tuned to the Alarm Grid Blog for updates on when the issue is corrected. Also please leave any thoughts you have on the situation down in a comment below. We'll be back with more security updates and news coming real soon!