AlarmNet360 Posts

Posted By

Users of the Lyric Alarm System with an LYRICLTE-A AT&T LTE Communicator installed take note. Resideo has identified an issue where, after the AT&T 3G sunset on 02/22/22, any panel not properly updated will lose its connection with the cellular network. This issue does not affect Verizon units.

The firmware version that resolves this issue is 01.09.07772.494, and it is available now on the Resideo AlarmNet360 servers. The issue at play here is that the AT&T cellular communicator currently falls back on the 3G network when it can't connect to LTE. Once an LYRICLTE-A communicator is registered, it looks for both an LTE signal and a 3G one. Without this critical firmware update, these communicators would continue to look for a 3G signal after the 3G sunset. Being unable to find a 3G signal, they will lose connection and go offline.

Users who find themselves in this situation have a few options. If you are a Lyric Alarm System user with the AT&T LTE communicator installed, you can choose to go ahead and manually update your system now. The system needs to be disarmed and have no trouble conditions present in order for the firmware update to go through, so a manual update allows you to choose a time when it is disarmed and ready. It also allows you to confirm that the update was successful after you see your panel reboot.

Since this is a critical update, AlarmNet will begin automatically updating panels that are affected by this issue starting on December 8, 2021. Since a firmware update can only go through when the panel is disarmed with no troubles, any users with a zone trouble, or a low battery message that they have been putting off correcting, should go ahead and take care of the issue. Once all trouble conditions are clear and the system is disarmed, we recommend that you go ahead and manually perform the firmware update. Instructions for updating are linked above.

If your system is automatically updated, it will reboot as part of the update process, so don't be alarmed if you see this happen. Step 3 in the FAQ on updating the panel linked above shows you how to confirm the panel's firmware version. So, if you see your panel reboot you can verify that an update was successfully completed.

Any Lyric Controller with a LYRICLTE-A AT&T LTE Communicator that is being installed on or after 02/22/22 will need to be updated to firmware version 01.09.07772.494 via the built-in WIFI communicator before the LYRICLTE-A will work properly. The firmware update should be completed prior to the installation of the LYRICLTE-A. The LYRICLTE-V Verizon LTE Communicator is not affected by this issue. You can read the full notice from Resideo here.


Tags: , , , , , , , , , , , , , , , , , , , ,

Comments


Posted By

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.

Tags: , , , , , , , , , , , , , , , , , , ,

Comments


Posted By

Resideo and Honeywell Home have just released Firmware Version 03.592.107.0 for the PROA7 and PROA7PLUS panels. This update allows the PROTAKEOVER module to support 5800 Series life-safety sensors like the 5808W3, 5800CO, and more. In addition, it offers some other features and improvements.

There are four (4) different panels in the Resideo and Honeywell Home ProSeries lineup. The Honeywell Home PROA7, and Honeywell Home PROA7PLUS, and the Resideo PROA7C and Resideo PROA7PLUSC. The 03.592.107.0 Firmware Version applies to all of them. The differences between the Resideo versions and the Honeywell Home versions are purely cosmetic. You can find details about that in a previous post.

The biggest news in this firmware release is the addition of life-safety support when using the PROTAKEOVER module. For the Honeywell 5800 Series legacy RF sensors, the use of life-safety sensors such as the 5808W3, 5806W3, 5800CO, and others has actually been ETL tested and passed to the UL Residential Fire standard. When taking over a CO detector, be sure to check the expiration date. CO detectors are usually good anywhere from six (6) to ten (10) years. Life-safety sensors from any of the other manufacturers supported by the PROTAKEOVER, including DSC (433 MHz), Bosch (433 MHz), 2GIG (345 MHz), Qolsys, and Interlogix (319.5 MHz), can be used, but they will not meet the ETL listing requirement.

When life-safety devices are used with the PROTAKEOVER the functionality for Loop 2 becomes automatic. For sensors programmed for Fire, Loop 2 automatically becomes the Maintenance (Clean Me) input. For those programmed as Carbon Monoxide, Loop 2 automatically becomes the End-of-Life input. For this reason, if you use a 5817CB or 5817CBXT, for something such as a wired heat detector input, you MUST strap out the loop 2 input, either with a wire jumper or a resistor, depending on which 5817 you're using, and you cannot use that input for a zone on the system.

Although the addition of life-safety support for legacy RF sensors is the big news in this firmware release, it is by no means the only news. This revision adds the ability to enable or disable on-screen panic alarms. It also adds the ability to program scenes via Total Connect 2.0 that pertain to alarm panel arming and disarming events only. Even if the panel itself doesn't have a PROWIFIZW module installed (Smart Home monitoring plan is still required). Prior to this release, if you had no intention of using Z-Wave devices, but you still wanted to program your system to arm or disarm based on a schedule, you couldn't do so unless you installed a Z-Wave controller in the panel.

Below, we'll list all the added or updated features with an explanation of each:

  • Zone Response Type Enhancement: The Device Type "Other" now offers the option to enable Chime. The PROSIXC2W now supports 24-Hour panic response types including 24-hour Silent, 24-Hour Audible, 24-Hour Medical, & 24-Hour Auxiliary. All Device and Response Types are now available when enrolling wireless zones using the PROTAKEOVER module.
  • LCD Keypad (PROSIXLCDKP) Enhancement: Now, when a Duress Code is entered at the wireless LCD keypad, only the 4-digit code is required. Previously, users would have to enter the 4-digit code + OFF [1].
  • Quiet Time Feature Added: The PROWLTOUCH Keypad now participates in Quiet Time (10:00 pm - 8:00 am). This means that non-emergency Trouble conditions, and Low Battery troubles will not sound the keypad during this time, though they will display. Included in this list are Communicator Trouble, System Low Battery, RF Transmitter Low Battery, RF Jam Trouble, AC Loss, and PROWLTOUCH Supervision Trouble. Sensor Tamper, and RF Supervision will sound. At 8:00 am, if the non-emergency trouble condition still exists, it will sound. This feature is automatic. It cannot be disabled, and the times cannot currently be changed, though that may change in future revisions.
  • Additional PROWLTOUCH Enhancements: While in backlight timeout, if the keypad reconnects to WIFI for any reason, the keypad will not illuminate. Keypad supervision is now defaulted as "Disabled". If a system has PROWLTOUCH keypad supervision enabled, updating to this version will NOT disable it. The Wireless Touchscreen keypad can now only be enrolled when the main panel is not in program mode. This prevents conflicts with the PROSIXLCD which MUST be added through panel programming. An issue has been corrected where, if the keypad locked up, the battery had to be removed and re-installed in order to reset the keypad. The Indoor MotionViewer (PROINDMV) clips can now be played back on the PROWLTOUCH as well as on the main panel.
  • End-user Can Push User Codes to Z-Wave Locks From TC2: Whew, that was a mouthful! Any Total Connect 2.0 Admin user can now create a user code and send it to a Z-Wave lock via either the Mobile App, or the Website. They have the option to both Push the User to the Lock, and allow the Lock Disarm by that User to automatically Disarm the system.

  • Improved TC2 Behavior During a Z-Wave Lock Jam: Previously, when a lock jam condition was displayed, the only option available was to physically go to the lock and toggle the lock position. Total Connect 2.0 now gives you the option to attempt to Lock or Unlock through the app or website.
  • Z-Wave Lock User Code Sync Improvement: In the past, setting the panel user code to match the Yale lock user code would cause issues. This is still not recommended, but the behavior should be improved.
  • Security Scenes Available in TC2 Without PROWIFIZW: There is no longer a hardware requirement that the panel have the Z-Wave Controller installed in order to create TC2 Scenes pertaining to security panel-only scenes. Currently, the security system scheduling is only available for Partition 1, and a plan that includes automation (Smart Home) is still required.
  • Improved Skybell and TC2 Syncing: Some doorbell cameras were having issues syncing with TC2 after the previous firmware update. Those issues should be resolved.
  • Improved PROSIX RF Signal Level Indication: The system now refreshes signal level for PROSIX devices immediately upon entering walk-test mode.
  • Improved TC2 Camera List Sync: In the past, it was sometimes necessary to Sync the panel twice to get an accurate camera list. This has been improved.
  • Partition Master User Enhancements: A Partition Master User can now only see event logs for the partition(s) they are authorized for.
  • Language Corrections: Improvements in translations for both French and Spanish.
  • Cyber Security Updates: Ongoing Cyber Security maintenance, as well as other bug fixes.

This firmware update can currently only be installed via WIFI. Any account communicating via cellular only will need to be connected to a mobile hotspot or other "WIFI" option before it can be updated. The size of this update is approximately 8MB.

This is a huge update with a lot of feature additions and some user-recommended improvements. Leave a comment below and let us know what you think about the ProSeries panel and the 3.5 update. As always, we look forward to hearing from you!

Tags: , , , , , , , , , , , , , , , , , , , ,

Comments


Posted By

AlarmNet360 is both a website and an app that can be used to create, edit, and cancel AlarmNet accounts. Access to this website and app is only available for licensed alarm dealers who are affiliated with AlarmNet. As an end-user you will not need to have or create an AlarmNet360 account.

Being a DIYer in the alarm industry can be pretty confusing at times! Nearly all of the documentation provided with alarm systems that have historically been installed only by alarm professionals is intended only for alarm professionals. So, when you buy that new ProSeries or Lyric Alarm System, and you begin reading the installation instructions, one of the first things you are told to do is create an AlarmNet360 account. This is not something that you, as a DIYer will be able to do.

This is where Alarm Grid comes in. Alarm Grid is a DIY friendly company. We sell professional grade alarm systems to anyone who wants to buy them. Sometimes, alarm professionals purchase from us and then they go about configuring the system themselves because they have access to AlarmNet360. Sometimes, customers purchase from us and then hire their own alarm professional to install their system and that alarm professional completes the setup on AlarmNet360 themselves. But usually, when an individual buys a system from us, they then sign up for one of our no-contract monitoring plans, and then we set up their account through AlarmNet360.

The relationship between Alarm Grid and our monitoring customers is a symbiotic one. DIY alarm users choose not to pay a professional to do something that they can do themselves. That being the physical installation of the alarm equipment. With the proliferation of self-contained, all-in-one systems, installation has gotten more and more simple. A child can do it. We have several young customers in their teens who set up systems just because they enjoy doing it, and figuring out new and interesting ways to make things happen.

On the monitoring side of things, that's where restrictions start to come in. There are certain things that have not opened up to DIYers yet, and access to AlarmNet360 is one of those things. You may be thinking, "Forget AlarmNet360, what's AlarmNet?" You can read about AlarmNet here. At present, only alarm dealers can sign up for access to AlarmNet360 in order to be able to add, edit, or cancel AlarmNet accounts. Access to accounts is very tightly controlled. The only accounts that Alarm Grid can see in AlarmNet360 are accounts that are assigned to Alarm Grid, which usually means that Alarm Grid created them in the first place.

Alarm Grid chose the DIY business model in part because we have everything we need to administer accounts on the back end, but we don't have a team of installers to send out and put in systems. DIYers are our installers, and in turn we provide for them the account admin services that they are not allowed to perform for themselves. We sell reasonably priced, professional grade alarm equipment. The same equipment that just about any alarm dealer in the country will sell you, and we handle the administrative side of things, in addition to providing free, world-class technical support to our monitored customers. In exchange for that, we charge a reasonable monitoring fee with no activation fees, no cancellation fees, and no contracts. We also don't care if you buy your system from us or elsewhere. We will monitor any equipment that is within our power to monitor for the same prices we charge to monitor the equipment we sell.

So, when you crack open that new system, and start reading the instructions, skip the part where it talks about the AlarmNet360 account. Whoever you sign up for monitoring with will take care of that part. Do you have an AlarmNet communicator? Have you been stumped by the mention of AlarmNet360 in your system's documentation? Leave us a comment below and let us know if this information was helpful. We always look forward to hearing from you.

Tags: , , , , , , , , , , , , , , , , , , , , , , , ,

Comments