Re: 2GiG recall

[Spellcheck Patrol <alarminstall@xxxxxxx>]

On Oct 26, 9:39=A0pm, mleuck <m.le...@xxxxxxxxx> wrote:
> On Oct 26, 3:38=A0pm, Spellcheck Patrol <alarminst...@xxxxxxx> wrote:
>
>
>
> > On Oct 26, 9:19=A0am, tourman <robercampb...@xxxxxxxxx> wrote:
>
> > > On Oct 24, 7:03=A0pm, Spellcheck Patrol <alarminst...@xxxxxxx> wrote:
>
> > > > I received an email announcing a recall on the 2GiG GSM today. Here=
 it
> > > > is:
>
> > > > 2GIG Voluntary Recall
>
> > > > 2GIG Technologies, Inc. is voluntarily recalling the following GSM
> > > > radio modules ("GSM Modules") used with 2GIG's GO!Control security
> > > > panels. We have been working with 2GIG and Alarm.com to secure a li=
st
> > > > of customers. We are developing a plan to replace these units as
> > > > quickly as possible and will communicate that plan to you as soon a=
s I
> > > > have worked out all of the details. In the mean time, please review
> > > > the note below so you can check your existing inventory.
>
> > > > Model #
>
> > > > GSM Signal Carrier
>
> > > > 2GIG-GSM1
>
> > > > T-Mobile
>
> > > > 2GIG-GSM2
>
> > > > T-Mobile
>
> > > > 2GIG-GSM3
>
> > > > Rogers
>
> > > > 2GIG-GSM4
>
> > > > Rogers
>
> > > > 2GIG-GSM5
>
> > > > AT&T
>
> > > > 2GIG-GSM6
>
> > > > AT&T
>
> > > > Date Codes Affected: 201049, 201050, 201051, 201052, 201101, 201102=
,
> > > > 201103 and 201104. These date codes appear as the first six numbers=
 of
> > > > the MDSN code of GSM Modules. This recall involves GSM Modules only
> > > > and not GO!Control panels.
>
> > > > We are recalling these GSM Modules because of the potential failure=
 of
> > > > a voltage regulator integrated circuit located on the GSM Module bo=
ard
> > > > that could, upon a reset or power off/on cycle, allow an overvoltag=
e
> > > > condition causing tantalum capacitors located on the GSM Module boa=
rd
> > > > to overheat and fail. This in turn could result in heat, smoke or f=
ire
> > > > damage to the control panel and potentially to surrounding areas.
>
> > > > Your support and assistance is critical to ensuring that affected
> > > > inventory is not installed and that installed recalled GSM Modules =
are
> > > > replaced correctly and promptly. Exchanges of new GSM Modules for
> > > > recalled GSM Modules must be performed by qualified service
> > > > technicians.
>
> > > > 2GIG has, through its back-end service provider, blocked all curren=
tly
> > > > uninstalled recalled GSM Modules from being activated and authorize=
d.
> > > > If a security dealer or technician attempts to install and authoriz=
e a
> > > > recalled GSM Module, the authorization will be denied by the back-e=
nd
> > > > service provider and a non- recalled GSM Module must be obtained to
> > > > continue the customer installation.
>
> > > > Instructions for Inspecting Inventory to Identify Recalled GSM Modu=
les
>
> > > > To identify GSM Modules within the date code range applicable for t=
his
> > > > recall, you will need to physically inspect all GSM Modules in your
> > > > inventory (whether in original packaging as a kit component, in
> > > > packaging as a separate component or otherwise). Only GSM Modules w=
ith
> > > > MDSN numbers that begin in the following range are being recalled:
>
> > > > Date Codes Affected: 201049, 201050, 201051, 201052, 201101, 201102=
,
> > > > 201103 and 201104.
>
> > > > (Note: The first four digits of the MDSN number are the year, the n=
ext
> > > > two are the week number of that year)
>
> > > > The MDSN number is found on the barcode label above the IMEI number=
,
> > > > which is used to register a customer=92s Alarm.com account. =A0This
> > > > barcode label can be found affixed directly to GSM Module itself, a=
s
> > > > well as the box it comes in. =A0If the GSM Module is installed in a=
 2GIG
> > > > GO!Control panel, open the rear panel cover and locate the GSM Modu=
le.
>
> > > > This is an automated email notification from ASIS. Please do not re=
ply
> > > > to this email.
>
> > > RHC: One could possibly make the argument that they rushed to market
> > > too quickly; however, at least they stepped up to the plate and
> > > acknowledged the problem....better than some other security parts
> > > suppliers in the past <
>
> > They have another issue looming with their thermostats. I know for
> > fact one end user in Dallas had their heat turned on during the summer
> > due to a malfunctioning thermostat.
> > Small bit of information for those that don't know but 2GiG is owned
> > by the head of Vivint aka APX
>
> I really wish I knew where you get your information. <

Yeah you're right, Mark. I never hear about anything that happens in
this industry. Keep telling yourself that.

>
> 1. It isn't owned by Vivint, they are however a major purchaser of the
> panel, the current owners/founders are Lance Dean formerly a Honeywell
> rep and Scott Simon who ran AlarmNet. <

I said it's the head of Vivint, who is an owner (didn't mean to imply
he owns 100%).
He's the man with the cash. The silent partner. He funded Lance's
venture.

>
> 2. The thermostats are manufactured by Radio Thermostat, if there are
> any issues it's from them although I've used several models of their
> thermostats including the one offered by 2GIG and haven't seen that
> problem. <

Well it happened. The dealer had to hire a HVAC company to replace the
lady's thermostat with something that works. The alarmco got stuck
with that bill, lost the client, and further compensated the client.