Total Connect 2.0 Posts

Final Update: Per a restoral announcement, this issue was resolved by 11:45 AM

Update 10:56 AM: According to Resideo, these notifications are the result of "catch-up" notifications from the outage earlier this week. As the queue for these old messages clears out, the erroneous messages should taper off. In the meantime, actual disarm photos may be delayed.

Original Post: We've had multiple reports this morning of Honeywell Lyric users who are receiving disarm photos from their panels every few minutes. Even users who don't have notifications enabled for disarm photos are being bombarded via the activity log. If you are affected, ignore disarm photo notifications for now.

Initially, it was only Lyric users who were reporting this issue, but now we've received reports from users of the Pro Series panels as well. It seems to be Push Notifications that are being affected. To disable Push Notifications for now, do the following:

1. Log into Total Connect 2.0.
2. Go to More > Settings > Notifications.
3. Tap the toggle for Push Notifications so that it is disabled.

We'll provide more details as they become available.

I was able to speak with an industry insider familiar with the events at Resideo's data center on Sunday night into Monday evening. This person related to me that there was an HVAC failure at the primary data center. It was initially thought to be an easy fix, but that turned out to be false.

Things started to go wrong in Resideo's primary data center on Sunday night at around 7:00 PM Eastern Time. An HVAC failure allowed the temperature in the data center to climb to a dangerous level for the servers located there. The normal temperature is around 70℉ (21℃) but on Sunday it rose into the neighborhood of 130℉ (54.4℃). The servers are set to failsafe, so rather than continue running, and risk catastrophic damage, they began to shut down.

An automated system is in place which notifies engineering and other stakeholders when a serious event like this occurs. An HVAC technician responded. Initially, the technician believed this would be a quick and easy fix, so the decision was made not to switch to the secondary data center, which is located in the Chicago area. The switch takes a bit of time, somewhere around 20 minutes, and the thought was that it wouldn't be worthwhile at that point to make the switch.

However, the HVAC tech discovered that in order to implement a fix, he or she was going to require a part, which they didn't have and couldn't get at that time. So, at around 1:00 AM Eastern Time, the decision was made to switch things over to the secondary data center. By about 1:30 AM Eastern Time, the backup data center was in control.

At around daylight Monday morning the HVAC system in the primary data center had been fixed. Once it was fixed, there was a period of time where the temperature was coming down to an acceptable level. By approximately 11:00 AM Eastern Time, Resideo was ready to switch back to the primary data center. At this point, alarm signaling was back up and had been for some time. By around 2:00 PM AlarmNet360 was back up, and by about 6:00 PM Total Connect 2.0 was back online, though customers and our own testing show that it was somewhat sluggish at first.

This outage affected three (3) things. The most serious was alarm signaling. During the early hours of the outage, customer's systems were unable to send signals to the monitoring station, or to send notifications to the customers themselves. Total Connect 2.0, the customer-facing app and website for end-user remote control was also down. Lastly, AlarmNet360, the alarm dealer facing service used to create or cancel accounts and remotely troubleshoot issues was also affected. When things went wrong, the initial focus was on getting alarm signaling backup as quickly as possible. This was the focus when they initially switched to the Chicago area data center.

This is a fully redundant system, and it is tested regularly. According to my source, there were hourly notifications being sent to alarm dealers, but the database of email addresses for these notifications seems to be outdated. This is something they will address going forward. A root cause analysis will be completed in the coming days, and any processes or procedures that need to be updated will be dealt with at that time. The site at status.resideo.com doesn't have a section showing either AlarmNet360 or Total Connect 2.0 status. Hopefully, this is something that will change in the very near future as well. Finally, those dealers who did receive notification noted that the emails weren't flagged as containing particularly important information. This is also something that will be addressed in the future.

Update March 16, Post Outage: Alarm Grid has confirmed that the Lyric and Pro Series panels are not uploading Disarm photos to TC2 in the wake of the recent service outage. We can't be sure these two issues are related, but the customers we've spoken to indicate that this feature was working prior to the outage. The issue has been reported to Resideo.

Since the restoral: We have noticed that some panels with WIFI, such as the Lynx Touch panels, are not automatically reconnecting to WIFI. If this happens to you try a panel reboot. If that doesn't fix the problem, then go back through WIFI settings and rejoin the network.

9:18 pm Update: Our testing indicates that Total Connect 2.0 is fully restored. We've confirmed that both iOS and Android devices are now able to connect. Resideo has confirmed that Total Connect 2.0 is restored as well.

Dear Valued Customer,
Subject: The following AlarmNet Services are now Restored

Alarm Delivery/Signaling
AN360
Total Connect

Alarm Delivery/Signaling
Date:3/14/22
Restored Time:2:40 PM ET
AN360
Date: 3/14/22
Time: 2:40 PM ET

Total Connect
Date: 3/14/22
Restored Time: 7:30 PM ET
Thank you for your patience.

7:40 pm Update: It's unofficial, but it appears the TC2 website is now accessible. In addition, when logging in through the iOS App, Activity appears to now be logging correctly again. Now, when I bypass a sensor, then arm, TC2 and the panel status match. When I look in Activity, the proper events are showing up. What I see when I log into the webpage matches what I see in the app.

5:00 pm Update: Total Connect 2.0 Text notifications are beginning to be processed. Earlier in the day, only push notifications were coming through. In these notifications, you are likely to see some older events as the queued events are processed by the server.

The Total Connect 2.0 Website, it appears, is still unavailable. To our knowledge, Android users are still not able to log in via the app. Users on the iOS platform can log in, but TC2 seems to be having trouble knowing whether a command is processed or not. I was able to bypass a zone and arm my system successfully (I can tell because I'm sitting next to it) but TC2 thought the arming command failed, and showed my system disarmed.

Resideo put up an official notice on the AlarmNet360 site. It states:

IMPAIRED
Alarm Delivery and AN360 Restored / Total Connect is still impaired

Start:2022-03-13 07:00 PM
End: N/A

Dear Valued Customer,
Subject: The following AlarmNet Services are now Restored
Alarm Delivery/Signaling
AN360

Alarm Delivery/Signaling
Date: 3/14/22
Restored Time: 2:40 PM ET

AN360
Date: 3/14/22
Restored Time: 2:40 PM ET

2:00 pm Update: AlarmNet360 is now up and functioning. This means our ability to create new accounts and remotely troubleshoot existing accounts is restored. There could still be a few hiccups, so please be patient.

Total Connect 2.0 is still accessible via iOS device, but not via the website. Some activity and notifications have begun to come through via iOS. As far as we know, Android users are still unable to log into TC2 at all.

Please Note: As the service begins to come back up, there may be some events that TC2 has had queued since the service went down. When the connection is restored, you may receive some notifications for events that actually happened at an earlier time.

1:00 pm Update: To our knowledge, AlarmNet customers' alarm signals are being delivered, and have been since about 3:00 am this morning. We've done some signal testing, and currently our signals are coming through.

The AlarmNet360 website and the mobile app are still down. It is not currently possible to log in there.

Total Connect 2.0 appears to be partly up. You can log in through iOS devices and execute some commands, but the Activity Log appears not to be working, at least not with consistency. Android users of the App report they are still unable to log into Total Connect 2.0. If you have news to report on your status, you can do so in the comments below.

UPDATE 12:42 pm: If you have silenced your system after receiving an error message about a comm failure or other outage-related message, such as communication path failure, the system should not sound again unless the condition restores, then occurs again. In that case, it will sound again because the system sees it as a new event that it needs to make you aware of.

The website listed above, status.resideo.com is the site for Resideo Total Connect Comfort (thermostats). Though this isn't a site specifically for Total Connect 2.0, the issues seem to be mirroring one another, so it's a reasonable site to check for progress. Honeywell Home is not the same thing as Total Connect 2.0.

Original Post: Alarm Grid has received information that Total Connect 2.0, a service of AlarmNet, is currently down. During this outage, you will be unable to log into your Total Connect 2.0 account, and you will likely see an error, and hear beeping, from your system.

To silence the beeping, simply disarm your system twice, or if you have a touchscreen, acknowledge the error by entering your normal arm/disarm code when prompted. Once the error is silenced, it should not sound again*, though it will continue to display on the keypad until the issue is resolved. Once the problem is resolved, another disarm (or two) may be required. You can check the status of this outage at status.resideo.com.

This outage has also affected the ability of the system to deliver signals to the central station and to Total Connect 2.0. We apologize for this inconvenience, rest assured that Resideo is working diligently to resolve the issue. We'll follow up with more information as it becomes available.

In addition to Total Connect 2.0 being unavailable, AlarmNet360 is also down. This means that we are unable to activate accounts using this service, and we are unable to remotely troubleshoot systems that communicate through AlarmNet.

Today, February 22, 2022 is the official date for the AT&T 3G Sunset. As we've mentioned before, there isn't a big switch that gets turned off and then, "Poof!" no more 3G. If you still have an AT&T 3G communicator, it may continue to work for a while, but there is no way to know how long.

If you're just becoming aware of the AT&T 3G Sunset because you have a security panel that you haven't been paying much attention to for a while, then you probably are seeing some type of error, and possibly hearing some annoying beeping. Some of the more common error messages are shown further down in this post. The thing to keep in mind is that your alarm panel wants to be sure that you know there's a problem. So, if you just press the touchscreen, or press any button on the keypad, that should stop the beeping, at least temporarily.

If you know the arming/disarming code for the system, enter it if prompted on a touchscreen panel, or if you're on a VISTA panel, just enter your 4-digit code and then press the OFF or 1 Key. This will acknowledge the trouble condition and stop the beeping on a more permanent basis, though in some cases, it may come back after a period of time. If you don't know a valid code for the system, then you will likely need to shut down your system by unplugging the transformer and the battery. If you're interested in putting your system into service keep reading to see how Alarm Grid is helping out in this situation.

If you find yourself in the unenviable position of needing to replace an AT&T 3G communicator, but you haven't done so yet, don't panic. The AT&T 3G network is vast and complex. It's not something that you can simply turn off. The process of sunsetting 3G equipment will take a bit of time. So, if after today your 3G communicator still works, you're one of the lucky ones. You've been given a slight reprieve. However, there is no way for us to know how long that reprieve will last, so decide what you're going to do, and do it now.

One ongoing problem that we've seen recently is supply chain issues. Maybe you've been trying to upgrade for the past six (6) months, but the communicator or system you need hasn't been available. Communicator manufacturers have been rolling out LTE Cat-M1 communicators in the absence of available components for standard LTE.

LTE Cat-M1 is the cellular network that was created for Internet-of-Things (IoT) use. It has lower power consumption, better range, and the modems used for it have a smaller form factor. The trade-off is lower bandwidth. However, the amount of data being transmitted by alarm communicators is very low compared to voice and data used for a traditional phone, so the difference in bandwidth isn't noticeable. Happily, the components to make LTE Cat-M1 communicators appears to be readily available, so those communicators have been coming into stock in the past months and continue to become available.

Some of the available AlarmNet LTE Cat-M1 communicators are listed below. These communicators are all compatible with the VISTA panels. The LTEM-PA and LTEM-PV are also compatible with the DSC PC1616, DSC PC1832, and DSC PC1864 and the Interlogix NX Series panels. For the Interlogix NX Series, the PRODCM is also required:

• LTEM-PA - Dual-path IP and AT&T LTE Cat-M1 communicator with the ability to add a traditional LTE communicator if needed. First communicator to allow non-Honeywell panels to use Total Connect 2.0.
• LTEM-PV - Dual-path IP and Verizon LTE Cat-M1 communicator with the ability to add a traditional LTE communicator if needed. Along with the LTEM-PA can allow non-Honeywell panels to use Total Connect 2.0.
• LTEM-XA - AT&T LTE Cat-M1 Communicator for VISTA Panels.
• LTEMXA-TC2 - AT&T LTE Cat-M1 Communicator for VISTA Panels. Includes upgrade chips for VISTA-15P and VISTA-20P panels, allowing them to support Total Connect 2.0.
• LTEM-XV - Verizon LTE Cat-M1 Communicator for VISTA Panels.
LTEMXV-TC2 - Verizon LTE Cat-M1 Communicator for VISTA Panels. Includes upgrade chips for VISTA-15P and VISTA-20P panels, allowing them to support Total Connect 2.0.
• LTEM-IA -COMING SOON - AT&T LTE Cat-M1 Communicator with RJ45 Port for Ethernet. Currently in Beta.
• LTEM-PIA - AT&T LTE Cat-M1 Communicator with RJ45 Ethernet port. Listed for UL-985 Household Fire.
• LTEM-PIV - Verizon LTE Cat-M1 Communicator with RJ45 Ethernet port. Listed for UL-985 Household Fire.

Some of the available Alarm.com LTE Cat-M1 communicators are listed below. Compatibility is listed with each communicator:

• Alarm.com ADC-SEM210-PS-AT-M - COMING SOON - Dual-path AT&T LTE Cat-M1 and ethernet capable communicator for use with legacy DSC Power Series panels (PC1616, PC1832, PC1864).
• Alarm.com ADC-SEM210-PS-VZ-M - COMING SOON. - Dual-path Verizon LTE Cat-M1 and ethernet capable communicator for use with legacy DSC Power Series panels (PC1616, PC1832, PC1864).
• Alarm.com ADC-SEM300-VT-AT-M - COMING SOON. - Dual-path AT&T LTE Cat-M1 and ethernet capable communicator for use with Honeywell VISTA (non-polling loop) panels (VISTA-10P, VISTA-15P, VISTA-20P, VISTA-21iP manufactured in 2005 or later).
• Alarm.com ADC-SEM300-VT-VZ-M - Dual-path Verizon LTE Cat-M1 and ethernet capable communicator for use with Honeywell VISTA (non-polling loop) panels (VISTA-10P, VISTA-15P, VISTA-20P, VISTA-21iP manufactured in 2005 or later).

Panel Cellular Communicator Trouble Condition Messages

If you are affected immediately by the AT&T 3G shutdown, you may see one of these error messages on your system:

• Check 103 ####: - You may see this on a non-polling VISTA panel, such as the VISTA-20P, but only if you have an Alpha Keypad like a 6160. The #### will be a 4-digit number. It may be 4005, which indicates that the communicator has lost connection with AlarmNet. The exact 4-digit code will depend on whether there are any other trouble conditions existing on the communicator at the time the message is displayed.
  *If you have a VISTA panel, choose from any of the communicators listed above for VISTA panels. The VISTA-21IPLTE can use the LTE-21V. The only way to update an original VISTA-21iP is to add an external communicator and disable the internal one. The prior link is an FAQ on how to do just that. The same rule about possibly downgrading to an IP only plan mentioned under the bF message applies here too.
• bF, or it may look like 6F: - This is supposed to be a bF, which stands for Backup Failure, as in backup communicator. This message means the same thing as Check 103, but will be displayed on a non-alpha keypad like a 6150. If this is the only type of keypad you have, then this is all the information the panel and the communicator can give you. If you get this message after 02/22/22 and your AT&T 3G Communicator has been fine until then, you're not one of the lucky ones. You should look to upgrade your communicator ASAP. *Or, if you have a dual-path communicator and an IP connection is available near it, you could downgrade to an IP only plan for now, and upgrade to LTE at a later time. Just bear in mind, if you go IP only, when the internet is out, your panel's ability to communicate is out. This is usually the case during power outages. The above rule about upgrading the communicator under the Check 103 message also applies here.
• Fault 103: - This may also show as a Check 103, then display as a Fault 103 after you silence the panel. This is what you see on the Honeywell L3000 panels when there is a problem with the communicator. Losing connection due to the 3G Sunset would cause this error code. There is not a good IP only option for the L3000 currently available. You can use a 7847-I, but it is a messy installation. You can also use the 7847I-L, if you can find one, they are discontinued.
  • Honeywell LTE-L3V - Verizon LTE Communicator for the Honeywell L3000 panel.
  • Honeywell LTE-L3A - AT&T LTE Communicator for the Honeywell L3000 panel.
• 103 Comm. Trouble: - The Lynx Touch Panels will display something along these lines. The icon and message may differ slightly, but the gist is the same. This is what you'll see on these panels if you're affected by the AT&T 3G shut down.
  • Honeywell LTE-L57A: - AT&T LTE Communicator for Lynx Touch panels. Important! There may be panel firmware revision restrictions with your panel and either of these communicators. Read the product description very carefully to be sure your panel is on the correct version for the communicator you choose. If you need to update the panel, you can do so with the Honeywell LYNXTOUCH-MSD Firmware Update Tool. It is compatible with the L5200, L5210, and L7000.
  • Honeywell LTE-L57V: - Verizon LTE communicator for the Lynx Touch panels. See the Important note above about panel firmware version limitations.
• ⚠ 950 Comm. Trouble: This is the message displayed on a Lyric Controller if it has a cellular communication path, and it loses contact with AlarmNet on that path. This is what you will see if the AT&T 3G shutdown has caused your communicator to go down. There may be other messages in the status bar at the top of the screen as well, having to do with Comm Failure and potentially other conditions, depending on what's happening with your panel at the time.
  • Honeywell LYRICLTE-A - AT&T LTE Communicator for Lyric. Firmware Revision v01.03.06548.482 or higher required!
  • Honeywell LYRICLTE-V - Verizon LTE Communicator for Lyric. Firmware Revision 1.09 (aka MR9) or higher required!
    
    
• Check 8##, ####: - You may see this message on a VISTA-128 or VISTA-250 panel. Devices connected to the keypad bus can be supervised for a connection to the panel, and for a tamper condition where applicable. The AT&T 3G Communicator can also be supervised for communicator troubles, such as a loss of connection to AlarmNet. If supervision is enabled (and it is not enabled by default) then when the 3G Sunset affects the communicator, the panel will display a Check or Trouble (based on programming) 8 + the 2-digit number of the address. So, if the communicator is assigned to address 03, and supervision is enabled, it will display as a Check or Trouble on Zone 803 plus the 4-digit communicator status code associated with the condition when you have the proper keypad to display it. If the only problem is a loss of network connection, then the 4-digit code should be 4005. Supervision is enabled by enabling the associated 800-zone with a trouble zone type, such as 05, Trouble by Day/Alarm by Night.
• 2GIG GC2 and GC2e Displays Trouble Icon and beeps 6 Times per minute until the trouble condition is acknowledged: This is the behavior of the 2GIG GC2e and presumable the 2GIG GC2 as well. The Security Screen will show a Yellow button with an exclamation mark and a number. When you press the button, it will take you to the Trouble Display screen where you can scroll through the trouble conditions, and you may click on the communicator trouble then press OK. This will stop any beeping, but the display will continue to show trouble until the condition is cleared. In the case of the AT&T 3G Sunset, this means upgrading the communicator.
  
  
  
  • 2GIG LTEA-A-GC2: - Alarm.com compatible AT&T LTE Communicator for 2GIG GC2 and 2GIG GC2e. Important! Be sure to check for any panel firmware version requirements associated with either of these LTE communicators for the 2GIG GC2 and GC2e panels.
  • 2GIG LTEV1-A-GC2: - Alarm.com compatible Verizon LTE Communicator for 2GIG GC2 and 2GIG GC2e.
2GIG GC3 and GC3e Message LED is lit and the panel chimes at ten-second intervals until the condition is acknowledged: The behavior for the cellular communicator losing connection to the AT&T 3G network on a 2GIG GC3 or GC3e depends somewhat on panel programming. In Q30, you set the amount of time that is allowed to elapse with no communication to the server before a trouble condition is indicated. The default is 30 minutes. A 0 in this field disables the supervision feature. The maximum entry is 255 minutes. Q31 also determines whether the radio network failure causes a trouble condition on the panel. This is enabled by default, but if disabled, you will have no visible indication if you are affected by the AT&T 3G sunset. Q32 is radio network failure reports. This is enabled by default and determines whether the panel reports the radio failure to the monitoring station (assuming it is able to do so with the radio down, the panel would need to be utilizing the WIFI communication path for this to be possible.)
• 2GIG LTEA-A-GC3: AT&T LTE Communicator for the 2GIG GC3 and GC3e panels. The panel must have Firmware Version 3.2.3 or higher to support this communicator.
• 2GIG LTEV1-A-GC3: Verizon LTE Communicator for the 2GIG GC3 and GC3e panels. The GC3 or GC3e must have Firmware Version 3.1.3 or higher to support this communicator.

Alarm Grid Is Here To Help!

If you're a current Alarm Grid customer and you have purchased an LTE communicator, but haven't switched over to it yet, please send an email to support@alarmgrid.com. In the subject line, be sure to put "I Need an LTE Upgrade". We'll reach out with further instructions and either a link to schedule your upgrade, or information as to what we need to begin your upgrade. Lyric and Lynx Touch users may be able to get upgraded with no appointment, where a VISTA user may require an appointment as those communicator swaps are a little more intricate.

If you purchase an LTE communicator or an upgrade kit from Alarm Grid, we will credit your monitoring account in the amount of the communicator or upgrade kit. If you purchase more than $150 in product, we'll also offer you free ground shipping, so if you've been thinking of adding a doorbell camera, or other products to your system, now may be a good time. The cost of products not associated with the communicator or system and communicator upgrade will not count toward free monitoring though.

If you have the ability to switch to an ethernet or WIFI connection only, you can choose to do that and your monthly monitoring fee will go down. You can purchase an IP or WIFI communicator strictly for that purpose. You may have that option with your existing panel and you just aren't using it, or maybe you were using dual-path monitoring, but now the cellular portion of your 3G communicator has stopped working. Whatever the case, if your communicator or panel supports the option for an IP-only connection, we will be glad to downgrade your service plan permanently, or until you can get the LTE upgrade. But be aware, Alarm.com customers do not have an option for IP-only monitoring.

If you're not a current Alarm Grid customer, never fear, you can get exactly the same deal as existing customers. If you purchase an LTE communicator from us or a kit with a panel and LTE communicator and you then sign up for monitoring with us, we'll give you credit toward free monitoring in the amount of the purchase for the communicator or communicator and panel. Once again, purchases over $150 will have free ground shipping, but any sensors or other devices that you purchase will not count toward free monitoring.

If you have any questions, feel free to reach out to us at support@alarmgrid.com. Our support hours are Monday - Friday from 9:00 am - 8:00 pm Eastern. We will help in any way that we can to get you through this transition. Your safety and peace of mind is our top priority.

A recent blog post about the looming AT&T 3G Sunset contained an error. We mentioned in that blog that the ingenious Resideo Cellbounce, a 3G to LTE converter, does not support Total Connect 2.0. That is incorrect. As long as the original 3G device supports TC2, the Cellbounce also supports it.

This misinformation has been updated in the original post, but for those who may have already read it, we wanted to also briefly touch on it here. In brief, the Resideo Cellbounce is a plug-and-play device. It plugs into a standard 110 Volt AC outlet and should be mounted within 25' (7.6m) of the working AT&T 3G Communicator. The Cellbounce connects to the 3G communicator, and to an AT&T LTE network. Once those connections have been made, it acts as a bridge, receiving the 3G information and transmitting it through the LTE network.

AT&T has committed to supporting the Resideo Cellbounce unit until at least the end of April, 2025. It is possible that support may go beyond that date, but the contractual obligation ends on May 1. Since the Cellbounce is plug-and-play, anyone can install it. An Installation Professional is not required. Though, it is important to note that the Cellbounce should not be powered on until after the information has been added to the customer account by the alarm dealer.

The Cellbounce will arrive in a box with a Serial Number and an IMEI number printed on it. This information must be provided to the alarm dealer so that they can attach the unit to the proper customer account. This step must be performed BEFORE the Cellbounce is powered on. Once power is applied, within a few minutes the Cellbounce will connect to the existing communicator and to the LTE network. LEDs on the unit will signal when these connections take place. From there it's just a matter of testing to be sure signals are going through successfully. Just be sure to put your system on test with the monitoring station prior to beginning this process.

The Resideo Cellbounce is only compatible with AlarmNet AT&T 3G communicators. The existing communicator must be registered and working. This means it can't be in a comm failure condition. Adding a Cellbounce to a communicator that is in comm failure will not correct that issue.

Freezing and water damage accounted for 29.4% of Homeowner's Insurance losses by cause in 2019*. From 2015 - 2019, the weighted average cost per accident year was $11,000* for freezing and water damage. Only fire and lightning damage was more costly. But flood damage can often be avoided.

At this time of year, with the worst of winter still ahead of us, our thoughts always turn to incidents of flooding which are caused predominantly by freezing temperatures. In many instances, homeowner's insurance companies want proof that there is both freeze and flood protection in a dwelling as a condition of insurance, or in order to provide the best available rate. With just a few added sensors and tweaks, your existing alarm system can help you prevent freezing and flood damage. Below we'll outline some products and strategies that can help.

To properly protect against this type of damage, it is helpful to know when the temperature in a building drops low enough to cause concern. There are many sensors that can assist in this, and in many cases, a sensor may perform double duty. There are motion detectors that also have built-in freeze sensing, as well as smoke, heat, and combination sensors. Here's a list of just a few, and the systems they are compatible with:

With any of the low-temperature sensing devices above, you can be alerted to dangerously low temperatures within a building. Alerts can come in the form of an email, text, or push notification from either Alarm.com or Total Connect 2.0, a call from the monitoring station, or both. With a Z-Wave or WIFI thermostat you can adjust the temperature when the HVAC system is working, or contact an HVAC service technician when it isn't.

Some of the devices listed in the table above combine freeze and flood sensing into a single unit. Of course, avoiding the presence of water in a location where it shouldn't be is optimal, but in some cases, it may not be possible. Flooding isn't always the result of freezing water pipes. With a flood sensor, you can be alerted to these situations and then take action accordingly. Alarm Grid offers a variety of both wired and wireless flood sensors. Some are listed above. Those and others can be found here.

If you can't control what's happening with the temperature in a location, then the next step in avoiding flood damage is controlling the flow of water. If you have a water shut-off valve within the building, then a Z-Wave water valve is just the thing you need to save the day (and a good deal of money). Once you receive a notification that a freeze condition is possible, or that a flood situation is underway, with Alarm.com or Total Connect 2.0 service, you can either set up a scene to automatically shut off the water within the premises, or you can manually log in and do so remotely.

With a combination of freeze and flood sensors, and a Z-Wave Water Valve, you can anticipate potential low-temperature flooding issues, be alerted to non-freeze-related flooding issues, and either automatically or manually turn off the water before damage occurs. Check with your homeowner's insurance agent to see if there are any discounts available on your policy if you add freeze and/or flood protection with an automated water shut-off option. You may be surprised at how quickly this equipment can pay for itself, even if you never have to use it.

*Statistics are taken from the Insurance Information Institute at iii.org.

**Qolsys Panels come in a variety of versions. All IQ Panel 2 Plus and IQ Panel 4 versions support PowerG wireless sensors. Then in addition, there are versions that support 319.5 MHz wireless, including S-Line Sensors. There are also versions that support 345 MHz wireless and 433 MHz wireless. When purchasing a Qolsys panel, or a sensor that will be used with a Qolsys panel, be sure to match the receiver type with the sensor type. Panels that support 319.5 MHz come in a box with a Gold stripe. Panels that support 345 MHz sensors come in a box with a Silver or Gray stripe, and those that support 433 MHz sensors have a Red stripe on the box.

We told you in 2020 how the Total Connect 2.0 app for Android could support Google Assistant voice commands. This feature allowed you to use your voice to control your system, but only through your phone. Now, the ProSeries panels, including the PROA7PLUS, can fully support Google Assistant.

What this meant back then was that there was nothing to download. Once the feature was enabled on your phone, a blue microphone icon would appear at the bottom of the Total Connect 2.0 app screen. When you pressed it, you could use your voice to check system status, and to arm or disarm the system. Now, with the latest Total Connect 2.0 release, you can actually set up TC2 within Google Home, and control your system from any Google Home capable device you have connected to your account.

Another improvement is the fact that this functionality is now available to both Android and iOS users. On either platform, make sure you have the Google Home app and then follow the steps to configure the Total Connect 2.0 skill within it.

Below is the Google Home App as seen in the Apple App Store:

The ProSeries panels include the Honeywell Home PROA7 and Honeywell Home PROA7PLUS and the Resideo PROA7C and Resideo PROA7PLUSC. Currently, these are the only Total Connect 2.0 compatible panels that support the improved Google integration. If you have one of the ProSeries panels, coupled with a Total Connect 2.0 account and you would like to take advantage of voice commands through Google Assistant, follow these steps:

1. Open the Google Home App, then click the [Plus (+)] Icon at the top left of the main screen.
2. Select, [Set up Device].
3. Select [Works with Google].
4. Search for [Total Connect] then select it.
5. Use your Total Connect 2.0 login credentials to log into TC2 from the skill.
6. Read the User Agreement and if you agree, press [Allow].
7. Be sure the Security System icon is selected, then press [Connect].
8. Click the [Pencil Icon] to assign the system to a room, then choose which room you'd like to add it to.
9. Hit the [Back button] repeatedly until you reach the Home screen.
10. You should now be able to query Google for system status, as well as arm the system to Away, Stay, or Night and Disarm the system using Google Assistant.

Important Update: We now have a full FAQ with a walk-through on how to set up the Google Home feature. This FAQ is applicable whether you're setting Google Home up using an Android or an iOS device running the Google Home App.

Voice control of automation devices is not yet available unless the automation is achieved through a scene tied to system arming or disarming. For example, if you have a scene that turns on the porch light when the system is armed to Away, and you use the Google Assistant to arm in this mode, then the porch light will come on once the system is armed.

Total Connect 2.0 also supports integration with Amazon Alexa, and has for a while now. The configuration is very similar between the two services. One difference between them is that Amazon Alexa is compatible with more different panel types. Most of the Honeywell Wireless All-in-One panels support it. This means that in addition to the ProSeries panels, the Lyric, Lynx, and even the VISTA panels all support being used with Amazon Alexa. As long as the panel is tied to a Total Connect 2.0 account.

To integrate Total Connect 2.0 with Amazon Alexa for voice control of any of the above panels, follow these steps:

1. Open the Alexa App and search for the Total Connect 2.0 skill.
2. Click [Enable]
3. You will be prompted to enter your Total Connect 2.0 login credentials. Enter them, then hit [Login]
4. You will see a User Agreement, read through it, and if you agree click [Allow].
5. Make sure the Security System icon is selected, then click [Connect].
6. A screen should appear showing "Total Connect 2.0 has been successfully linked".

Once the above steps have been completed, log into the Total Connect 2.0 app and go to the Profile Page. Under the Access section, be sure that your user code has been saved and synched with the panel. If this isn't done, Amazon Alexa won't function properly. In the past, we've made FAQs for integrating some different panels with Amazon Alexa. You can find links to those FAQs below:

How Do I Connect My Lyric Alarm System to Alexa?

How Do I Connect My VISTA-21iP to Alexa?

Resideo Official Instruction Sheet on Integration

In October Alarm Grid received a limited supply of the new IPCAM-WOC2, which sold out quickly. Since that time, Total Connect has been without an outdoor camera option. We're happy to announce that the Resideo IPCAM-WOC2 is back in stock, ready to ship. If you've been waiting, wait no more.

As we reported in October, the IPCAM-WOC2 is the updated replacement for the discontinued IPCAM-WOC1. The two items look almost identical, with the IPCAM-WOC2 having an internal BlueTooth Antenna, as opposed to an external one on the wire dongle. The reset switch has also been redesigned to be slightly easier to reach once the camera is mounted.

In October, we had ten (10) of these cameras available, and they sold out pretty quickly. Since then, we've been waiting for this, and many other items' stock to be replenished, and today we got the word that the Total Connect 2.0 outdoor camera option is available once again. Hopefully, this will be the first of many items to have their stock replenished.

The IPCAM-WOC2 is an outdoor camera with an IP66 rated housing. It captures video in 1080p HD and can connect to a 2.4 GHz WIFI network. It has a 117.0° diagonal field of view, which provides excellent coverage. It has superior night vision capabilities compared to the IPCAM-WOC1, and also supports audio analytics with intelligent sound detection. It supports a MicroSD card for backup storage in the event the network connection goes down, and comes with a 16 GB card included.

As with the other Resideo HD cameras supported by Total Connect 2.0, the IPCAM-WOC2 uses a QR Code generated on a smart device in order to be associated with the proper Total Connect 2.0 account. For this reason, it is best to configure the camera with the account prior to actually mounting it in its final location. Doing so may prevent a few extra trips up and down a ladder. Pairing the camera with the account prior to installation also allows you to verify the installation location and viewing angle before you permanently tighten everything down in the installation.

What do you think about the IPCAM-WOC2 and its availability? Have you been waiting impatiently to purchase a Total Connect 2.0 compatible outdoor camera? Is there some other product you're waiting for? Leave a comment below and let us know. We always look forward to hearing from you.

Local Alarm Mode, also called Demo Mode, is a way for an alarm dealer to demonstrate the full features of the panel without having to register it to an AlarmNet360 account. However, while in this mode, panel communications can't be configured. A panel in this mode can seem to be broken.

Alarm Grid has seen several of the Honeywell Home PROA7, Honeywell Home PROA7PLUS, Resideo PROA7C, and Resideo PROA7PLUSC panels recently that have either arrived with Local Alarm Mode enabled, or have been put into this mode during initial setup. Once Local Alarm Mode has been enabled, it is impossible to configure the panel communication settings until Local Alarm Mode has been toggled off.

Local Alarm Mode is a valuable tool that has been made available to alarm dealers so that they can demo these new panels for a customer in spite of the fact that the panel isn't associated with an account. This was particularly important when the panel was first introduced because there was no local programming. For those early panels, until the ProSeries panel was registered, it couldn't do much unless Local Alarm Mode had been enabled.

This was a great tool at the time for alarm dealers, but for DIY customers, it doesn't offer much in the way of benefits. Now that the panel has local panel programming available, there really is no reason for an Alarm Grid customer to want to use this feature. Whether the panel arrived with this feature enabled, or the feature was enabled during programming, once the customer decides to have the system monitored, whether self monitored, or with central station monitoring, Local Alarm Mode should be disabled.

To check to see if Local Alarm Mode is enabled or disabled, choose the Menu icon (≡) at the bottom center of the Home screen. Select Tools > Installer Code (default is 4112) > Local Alarm Mode. The feature can then be toggled OFF if it is enabled. If it was enabled and you toggle it off, you'll see a confirmation screen, click on the "YES, DISABLE" option.

If you've been using the system with Local Alarm Mode enabled, and you have signed up for alarm monitoring with Alarm Grid, be sure to toggle this feature OFF as soon as possible. Depending on which monitoring plan you sign up for, activation of your account may begin immediately after sign up, and having this feature enabled at that time can cause delays. This is particularly true of the Self-Monitoring options. If you signed up for a central station monitoring plan, just be sure to disable this feature prior to your activation appointment.

Update 12/02/21:

We have confirmed with Resideo and at least one customer that the issues regarding the syncing of Automation between all versions of the Tuxedo Keypads, and the VAM have been resolved and that remote control of Z-Wave devices has returned to normal. Users should now be able to remotely control Z-Wave Automation Devices during any Total Connect 2.0 session. Any Alarm Grid customer that notices issues like this in the future, please report it to support@alarmgrid.com.

Update 11/26/21:

On Tuesday of this week, Resideo announced an update meant to fix this issue. Apparently, it fixed the portion of the issue where all Automation Syncs were failing, but did not address the issue with being unable to control Z-Wave Devices remotely.

There is something of a workaround for this portion of the issue at this time. During the TC2 session where a successful Automation Sync occurs, you can control Z-Wave devices remotely. Once you end that TC2 session and begin another one, you will lose that ability. So, for now, if you need to control a Z-Wave device remotely, perform a sync, and once you see in the Activity Log that the Automation Sync was successful, you will be able to control Z-Wave devices until the current TC2 session ends. Stay tuned and we will provide further updates as this issue is resolved.

Original Post:

In the last couple of weeks, Alarm Grid has noticed several customers with VAM and Tuxedo Keypads (all versions) having trouble syncing Z-Wave devices with Total Connect 2.0. This prevents newly added Z-Wave devices from showing up in TC2, though local control at the device is still available.

This issue doesn't seem to affect Total Connect 2.0 accounts associated with AiO (All-in-One) panels such as the Lyric Controller and the Honeywell Home PROA7PLUS. Accounts with these panel types should be working fine. It is unknown exactly what the problem is, and there is currently no workaround available. We've been in touch with Resideo and Honeywell Home and they are aware of the problem, but there is no Estimated Time of Resolution (ETR) for a fix.

You can continue to add and remove Z-Wave devices locally at the VAM or Tuxedo. But any changes that are made locally at the Z-Wave controller will not be synced to Total Connect 2.0. This means that any device deleted locally will continue to show up in TC2, and any device added locally will not show up in Total Connect 2.0 until this issue is resolved and a successful automation sync occurs.

Any device that currently shows up in Total Connect 2.0, and still exists in the Tuxedo or VAM CANNOT be controlled remotely through TC2. When an attempt to perform an Automation Sync occurs, there is no Automation Sync Failed, or Automation Sync Successful message displayed in TC2 Activity. Status changes from the Z-Wave device to TC2 seem to be coming through fine. It's only the sync process and remote control that seem to be having issues.

Alarm Grid is working with Resideo and Honeywell Home, and as soon as this issue is resolved, we'll post about it here. We posted information earlier this year about the Tuxedo Keypads and VAM Automation Controllers not updating the weather properly. We don't know if this current issue is related to the previous one, but we hope that it will be resolved soon. Stay tuned to our blog for updates.