Service Announcements Posts

Posted By

We have received word that Qolsys has released Firmware Version 2.5.4 for the IQ Panel 2 and IQ Panel 2 Plus Systems. The main highlights for this latest firmware update include fixes with the Z-Wave S2 Encryption Protocol, plus fixes regarding the use of LiftMaster Garage Door Control.

We do have one thing to mention for users of the Qolsys IQ Panel 2 Solar Integration. If you are using the IQ2 Solar Integration then, DO NOT UPGRADE TO 2.5.4. Instead stay on 2.5.3. However, if you want to use the LiftMaster Garage Door Integration instead of the Solar Integration, then you should upgrade to 2.5.4, but you will LOSE the Solar Integration. On Version 2.5.4, it is IMPOSSIBLE to use BOTH the Solar Integration AND the LiftMaster Integration. Qolsys has said that this will be fixed in Firmware Version 2.6.0, which should hopefully be available in the coming months. For now, if the Solar Integration is more important to you than a LiftMaster Integration, then just STAY ON 2.5.3. This ONLY applies to users of the Solar Integration. If you do not care about the Solar Integration, or if the LiftMaster Integration is more important to you, then UPGRADE TO 2.5.4. All things considered, MOST USERS WILL WANT TO UPGRADE TO 2.5.4. Keep in mind that there is NO WAY TO DOWNGRADE TO A LOWER FIRMWARE VERSION AFTER UPGRADING.

Before we get into all of the exciting new changes for IQ2 Firmware Update 2.5.4, we will first explain how to apply the firmware update to your Qolsys IQ Panel 2 or IQ Panel 2 Plus System. To get started, there are a few prerequisites to keep in mind. Your Qolsys IQ Panel 2 or IQ Panel 2 Plus must be on at least Firmware Version 2.0.1 or higher to apply the update. It must also be connected to WIFI, it should be receiving AC power from its plug-in transformer, and it should not have a low battery condition.

Now, this may get a bit confusing, but stick with us. Depending on which firmware version your IQ2 is currently running, it may be necessary to update in stages to get to 2.5.4. Start by considering which firmware version your system is currently running, and then take the appropriate action(s) based on what is outlined below. The important thing to remember is that your IQ2 must be already on 2.52 or 2.5.3 OR between 2.0.1 and 2.4.2 to upgrade directly to 2.5.4. If that applies to your system, then just go directly to 2.5.4.

For users on Version 2.5.0 or 2.5.1, things become a bit tricky. For these users, you need to upgrade to 2.5.2 or 2.5.3 first before you can get to 2.5.4. We recommend just updating to 2.5.2 and then going to 2.5.4, skipping 2.5.3. For information on updating to Version 2.5.2, please refer to this blog post. Once you are on 2.5.2 or 2.5.3, you can then follow the steps listed below.

Once you are on 2.5.2 or 2.5.3, or between 2.0.1 and 2.4.2, do the following:

  • Start from the main screen of the IQ Panel 2 or IQ Panel 2 Plus.
  • Swipe down the small grey bar at the top.
  • Choose Settings > Advanced Settings.
  • Enter your Installer Code. Remember that this code is 1111 by default.
  • Choose Upgrade Software.
  • Find Patch Tag, and enter iqpanel2.5.4. You must enter the patch tag EXACTLY AS DISPLAYED. Choose OK.
  • Press Upgrade Using Network. If all the requirements have been met, the update will start.

Now, with that out of the way, we can start talking about what's new to 2.5.4. Here is a list of everything you can expect!

  • An issue involving the 6.81.03 Z-wave Firmware Version, also referred to as the 6.81 Z-Wave SDK, has been fixed. The issue caused Schlage Z-Wave Plus Door Locks and the Honeywell T6 PRO Z-Wave Plus Thermostat to not function properly when S2 encryption was used. These devices should now work properly when enrolled using the S2 protocol.
  • Corrections have been made to an issue that arose in Firmware Version 2.5.3 involving the use of LiftMaster Garage Door Control. The integration would not function properly from the panel UI. More information can be found in this document from Qolsys. Also, please see the message regarding the loss of the Solar Integration in 2.5.4 in the notes outlined above.
  • An issue involving the LED status light on PowerG Smoke and Heat Detectors, namely the DSC PG9936, has been fixed. Previously, the status light would not reset after an alarm had been cleared when using Installer Mode or Test Mode on the panel. More information on the issue is available in this document released by Qolsys.
  • The PowerG Radio Firmware has been upgraded to Version 80.34. This upgrade is designed to improve wireless communication, particularly when using multiple DSC PG9WLSHW8 PowerG Wired to Wireless Converter units.
  • Z-Wave Plus 500-Series Z-Wave Switches from Cooper and Eaton are now supported by the IQ Panel 2. The newly supported switches include RF9601, RF9617, RF9640-N, and RF9642-Z.
  • An issue involving PowerG Shock Sensors, namely the DSC PG9935, has been fixed. The issue occurred following a 15 minute placement test mode timeout. There have been further improvements made for false alarm prevention when shock sensors are paired as two (2) separate zones on the system.
  • The 2.5.4 Update now allows PowerG Keypads, namely the DSC WS9LCDWF9, to sound Fire Alarms triggered in other system partitions, provided that the Global Fire Setting is enabled. Please see this FAQ for more information.
  • PowerG Keypads, namely the DSC WS9LCDWF9, can now show special characters on their LCD screens if they are used as part of a Zone Description on the main Qolsys IQ Panel 2 Plus System.
  • The Energy Optimizer for the system is now available locally on the IQ Panel 2. This is used to set Z-Wave thermostats and Z-Wave Plug-In Switches to reduce their energy usage during peak consumption hours. This feature should NOT be used alongside Alarm.com Thermostat Schedules. It is also NOT compatible with the "Give Back, Get Back" program offered by Alarm.com.
  • Certain improvements have been made to the Help Videos as part of the Easy Install Wizard for the system.
  • There have been small changes to facilitate support of Canadian ULC-S304 for Level II Residential and Level II Commercial Listings.
  • A new setting for ULC Commercial Power Restoration is now available.
  • PowerG Image Sensors, namely the DSC PG9934P and DSC PG9944, now take a picture upon the activation of a Fire Alarm or a Carbon Monoxide Alarm, for EU IQ Panel 2 Systems Only. Most United States users will not have this change applied. Furthermore, image sensors learned into Sensor Group 25 will also produce pictures if triggered while the panel is armed.
  • If the EN Grade 2 Security Settings is Enabled, then User Codes will be hidden with dots, rather than showing the entered numeric code.

If you have any questions about Qolsys IQ Panel 2 Firmware Update 2.5.4, or if you are an Alarm Grid monitored customer needing help upgrading to Version 2.5.4, please email us at support@alarmgrid.com for assistance. This email is also good to use if you are interested in starting new monitoring service with Alarm Grid. Our support and planner teams are available from 9am to 8pm ET M-F. We look forward to hearing from you.

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

Comments


Posted By

Alarm.com is phasing out support for the Microsoft Edge Legacy Web Browser. Anyone using the browser to access Alarm.com may soon notice a pop-up message suggesting that they switch to a more optimized web browser instead. Alarm.com access will be denied entirely starting in February 2021.


According to Alarm.com, the appearance of the warning pop-up message suggesting the use of a different browser will appear to anyone who logs into Alarm.com using the Microsoft Edge Legacy Browser on or after Monday, December 21, 2020. The user will then be able to access their account like normal. This is being done to prepare users for the eventual plan to drop support for this browser entirely.

Then, starting in February 2021, any user who attempts to log-in using the Microsoft Edge Legacy Browser will be denied access to the Alarm.com servers entirely. The user will still be able to successfully access their Alarm.com account by using an approved web browser or the Alarm.com Mobile App on an Android or iOS device.

Alarm.com recommends using the latest version of Google Chrome, Mozilla Firefox, or Apple Safari to access their web servers. The latest version of Microsoft Edge is also supported and recommended for use with the Alarm.com website. Please note that Alarm.com dropping support for the Microsoft Edge Legacy Web Browser should not be confused with them dropping support for the Internet Explorer 11 Web Browser. Alarm.com dropped support for IE11 back in late June of 2020. You can read about that in this prior blog post.

Using a recommended web browser with the Alarm.com website will help ensure that you have the best possible end user experience. This includes optimized video viewing for Alarm.com Cameras and a better, smoother experience when using the Alarm.com website to control your security system. Alarm.com also promises fewer service disruptions when using the latest version of a recommended web browser, or the latest version of the Alarm.com Mobile App.

Alarm.com says that they will keep us informed regarding the upcoming Microsoft Edge Legacy Sunset, as well as the Adobe Flash Sunset. The Microsoft Edge Legacy Desktop App will reach its end of life on March 9, 2021. Adobe Flash is set to reach its end of life after December 31, 2020. We will update this blog if we learn any new important information regarding these respective sunsets.

If you have any questions regarding the use of Alarm.com, or if you are interested in starting new alarm monitoring service for accessing the Alarm.com platform, please email our team at support@alarmgrid.com. We're here to check and respond to your emails from 9am to 8pm ET M-F. We look forward to hearing from you!

Tags: , , , ,

Comments


Posted By

Alarm Grid is aware of Technical Notification #55 that identifies possible premature low battery warnings for Honeywell Combination Smoke and CO Detectors. Affected products include the Honeywell 5800COMBO, the Honeywell SiXCOMBO, and the new Honeywell Home PROSIXCOMBO for the PROA7PLUS.


According to Technical Notification #55 from Resideo, most instances of a premature low battery condition occur after replacing the batteries in a Honeywell 5800COMBO, Honeywell SiXCOMBO, or Honeywell Home PROSIXCOMBO. This notice pertains only to a low battery condition that occurs immediately, or almost immediately, after replacing the batteries in a sensor that has been in use for several years.

Each of the aforementioned combination smoke/CO detectors uses four (4) lithium 3V CR123A batteries for power. A premature low battery condition is when the sensor falsely indicates that the batteries inside the sensor are low on power, and a corresponding trouble condition is displayed for the associated zone(s) on the panel. But while the sensor is falsely indicating low batteries, the actual reality is that the batteries are still at, or near, full power.

Resideo states that the false low battery condition is the result of intermittent connectivity between the batteries themselves and the nickel battery contact points inside the sensor's battery compartment. The best way to verify that the low-battery condition is indeed false is to take a voltmeter reading of the batteries. If you find that the reading for each battery is at or above 3V, then you can confirm that the low battery condition is false. Any one of the four (4) batteries that reads below 3V could cause a low battery indication.

Additionally, Resideo suggests taking the following steps to see if a low battery trouble condition can be cleared:

  • Make sure each battery is properly seated and secured in its holder.
  • Make sure the battery contacts are snug with no movement.
  • Make sure the battery as well as the battery contacts are clean, and wipe them with alcohol or a mildly abrasive cloth if necessary.
  • Remove and reinstall the batteries to try and clear the trouble condition.
  • Replace old batteries with fresh ones to see if the trouble clears.

As a reference, the aforementioned sensors will typically report a low battery condition once the detected voltage drops below 2.3V. If you have a premature low battery condition on one of these sensors that you cannot otherwise clear, then make sure to check the batteries regularly and replace them as soon as necessary. If possible, try performing the steps above to see if you can correct a premature low battery condition. It may be necessary in a worse case scenario to replace any sensor affected by this condition. Attempting to use a sensor displaying a consistent low battery trouble is certainly not ideal, even if that condition is known to be false. Remember that these are life-safety sensors, so keeping them consistently powered on and functioning properly is crucial.

If you have any questions about this issue, then please not hesitate to email our support team at support@alarmgrid.com. We check our email from 9am to 8pm ET M-F. We look forward to hearing from you!

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

Comments


Posted By

Alarm.com is back again for the holiday season, as users will once again be able to have Santa appear in screenshots for their Alarm.com Security Cameras. This feature is great for sharing with young family members, as well as for as anyone who loves Christmas and wants to get in the spirit.


The "Santa Security" feature is available on both the Alarm.com website and mobile app. If you are using, the Alarm.com Mobile App, then you may want to verify that you are using a high enough version. For iOS users, Version 4.17 or higher is needed. Android users need at least Version 4.15.1. Remember you can download the app for free from either the Apple App Store or the Google Play Store. And of course, you will need a monitoring plan that includes access to Alarm.com for video surveillance, such as an Alarm Grid Platinum Plan.

To get started, just open the Alarm.com website or mobile app, and then enter the Cameras Menu. Select the video feed for one of your compatible cameras, and then click on the icon of Santa. You can select from a few different Santa images to insert into your camera's screenshot. The Santa image you select can be positioned wherever you like, and you can also resize the Santa image to better fit the setting. Then all you have to do is download the altered picture and share it with your friends and family to show them that Santa visited!

Of course, this isn't capturing the real Santa on your Alarm.com Security Cameras. Santa is much too fast for that, so it won't work if you try to get video of the real Kris Kringle himself. But this is certainly a nice alternative. The feature will be available from December 7th through December 31st. That should give you plenty of time to produce a Santa image to show your kids, loved ones, and anyone else who loves Christmas. No special sign-up is required. All you need is a compatible Alarm.com Camera and a video monitoring plan.

If you have any questions about the Santa Security feature for Alarm.com, then please reach out to us be emailing support@alarmgrid.com. Our team is happy to answer any questions you might have about the Santa feature, or about Alarm.com service in general. This email is also good to use if you want to start new monitoring service. It's not too late to set up an Alarm.com Security System with a camera so that you can enjoy the Santa Security feature this year. As always, we look forward to hearing from you. Happy holidays 2020!

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

Comments


Posted By

Alarm Grid has been hearing reports from 2GIG GC3 and 2GIG GC3e users with trouble conditions that they cannot clear. According to reports, these unclearable errors only occur on these systems when Smart Area Partitioning is enabled. While inconvenient, they shouldn't cause much issue.




When a "trouble" condition appears on a 2GIG GC3 or 2GIG GC3e with partitions enabled, the "Smart Areas" menu button on the panel will appear yellow. Normally, you fix the trouble condition itself first. Then, you acknowledge the trouble by clicking on Smart Areas, entering your Master Code, and clicking the "speech bubble" next to the partition associated with the trouble. Then the trouble should clear, and the Smart Areas button should return to its usual blue state, indicating that everything is normal. More information on the trouble-clearing process can be found in this FAQ.

In the case of our customers who have reported this issue, they received a valid trouble condition of "Console Broadband Network Failure" or "Cellphone Communication Failure" appearing on various Smart Areas of their GC3 and GC3e systems. Because this was a system trouble, it showed up on multiple partitions. The trouble condition was then resolved successfully, as evidenced by the ability to send successful test signals via all communication paths to Alarm.com. However, the trouble message became stuck in multiple partitions and could not be cleared by any means.

Alarm Grid was able to replicate a similar issue through a relatively unique method. We found that if you enrolled a sensor with a GC3 or GC3e, put the sensor into a trouble condition (e.g. loss of RF supervision, cover tamper, etc.), and then deleted that sensor from the system without ever correcting and clearing the trouble condition, then the same situation would occur. Whichever partition the sensor was assigned to would be stuck with a permanent trouble condition that could never be cleared, regardless of which troubleshooting method was attempted. Of course, this would rarely happen in practice, as a responsible user would fix a trouble condition before intentionally deleting a sensor. But nevertheless, we were able to replicate a similar problem in practice.

Various methods have been attempted to fix this issue, but nothing has worked at removing these seemingly unclearable troubles. Some of the methods attempted have included disabling and then reenabling partitions, powering down the panel for a hard reboot, performing a reboot through System Manager, upgrading the firmware version, and factory defaulting the system. Users have reported that once they acknowledge the error that the panel stops making any audible sounds associated with the trouble condition, but still, the Smart Areas button remains a disturbing yellow color.

Not every GC3 and GC3e with partitions enabled appears to be affected. From what we can tell, only a small number of these systems are displaying such an error. Either that, or most users have chosen simply to ignore the issue, and not report it to us. Most of our monitored customers with a GC3 or GC3e have not reported this issue. But the ones who have reported the issue have left us at a loss for a solution. We apologize to these users, as we know how frustrating this can be. We don't often encounter issues we can't solve with a little bit of thinking, but this is one of those rare cases where we are just as confused as you are.

While this issue is annoying and bothersome, it doesn't appear to have any major impact on the performance of the system. The GC3 or GC3e System will still report to Alarm.com as intended, and it can still be relied upon for security and life-safety purposes. The one pressing factor though is that this issue can make it difficult for a user to determine when in fact there is a legitimate trouble condition on their system. Most GC3 and GC3e users who use partitions rely on the Smart Areas button to tell them if something is wrong. If it's blue, then everything is okay. But if it's yellow, then something needs their attention. This is a pretty simple check, and when it's not functioning properly, it's understandably frustrating.

Unfortunately, we do not have a solid fix for this problem at the current time. But luckily, if a new trouble condition occurs, the system will provide a trouble beep locally. It will continue to beep until a user acknowledges the new trouble condition. In addition, if you have trouble notifications enabled through Alarm.com, then you will also receive a new trouble notification via text, email, and/or push notification should any new issues arise. Nortek and 2GIG have been apprised of this error, and advise they are working on a fix.

Our reports indicate that this issue is still present in both the latest GC3 Firmware and the latest GC3e Firmware. The highest firmware currently available for these panels is Version 3.2.5, and even systems on this latest firmware have been shown to be affected. We are hopeful that 2GIG and Nortek will release a fix for these unclearable trouble conditions in Firmware Version 3.2.6. But unfortunately, we have not yet received any indication that such a fix will be implemented. We also have no release date for Version 3.2.6 at this time. Again, we apologize for any inconvenience.

If you are affected by a trouble condition that you cannot clear, make sure to try the conventional methods of clearing it first. Correct the cause of the trouble, and then acknowledge the trouble by following the the steps in the FAQ linked earlier in this post. If you still can't clear the trouble, then please, report it to our support team by emailing support@alarmgrid.com. Your data is valuable to us in reporting the problem to 2GIG and Nortek so that a fix can be implemented. Our support team is available to check and respond to emails from 9am to 8pm ET M-F. As always we look forward to hearing from you!

Tags: , , , , , , , ,

Comments


Posted By

Alarm Grid will be closed Thursday, November 26, 2020, for the Thanksgiving holiday. During this time, we will not be answering phones, responding to emails, or shipping orders. We will reopen for business as usual tomorrow, Friday, November 27, 2020. We apologize for any inconvenience.


Additionally, we are also sad to announce our Florida headquarters will be resuming quarantine due to the spike in COVID-19 cases in the state. Starting on Friday, our Florida employees will begin working from home as we did earlier this year. This should not affect your experience as an Alarm Grid customer, but please keep this in mind if you contact us for support or other inquiries. Our Florida headquarters is expected to remain in quarantine until at least the end of the 2020 year.

We understand that this has been a challenging year for many people out there. The ongoing pandemic may put a damper on many holiday gatherings, get-togethers, and annual traditions. But there is still plenty to be thankful for, and we should use this holiday to remember that. Our team will be enjoying a much-needed day of rest today, and we will be ready for business tomorrow.

Remember that you can still reach our central station partner Criticom Monitoring Services (CMS) while we are closed if you need to put your system on test mode. You can do so by calling our phone number, (888)-818-7728, and choosing option number [9]. Alarm Grid customers in Canada who receive central station service through Rapid Response can contact them at (800)-932-3822 to put their systems on test mode.

If you need to reach us while our offices are closed, please email support@alarmgrid.com, and we will do our best to reply as quickly as possible when we reopen on Friday. Keep in mind that our usual business hours are from 9am to 8pm ET M-F. We look forward to hearing from you!

Tags: , ,

Comments


Posted By

Security system users in Panama City, FL may soon have to think about alarm registration and newly enforced fines for false alarms. Reports indicate that city council members approved the first reading of a new ordinance, with a second ordinance reading set to follow sometime soon.


Concerned citizens and officials in Panama City, FL are considering a new city ordinance that would allow the city to fine businesses and residents who intentionally or unintentionally cause false burglary/intrusion alarms and/or false fire alarms. The purpose of such a new ordinance would be to make first responders more readily available and to cut down on a high rate of false alarms.

Vice Mayor of Panama City, FL Geoff McConnell said of false alarms, "This is a huge drain on resources that could be better spent responding to emergency calls... We don’t want to spend money on chasing these false alarms when the public isn’t going to benefit from the safety of them.”

According to McConnell, more than 11,000 total false alarms are reported in the city each year. That reported figure comes from combined reports from the Panama City Beach Police Department and Panama City Beach Fire Rescue. McConnell went on to state that most of the city's false alarms are from repeat offenders. The majority of these repeat offenders are neglectful businesses with faulty alarm systems.

The ordinance being considered would not only enact fines for false alarm offenders, it would also make registration of alarm systems mandatory. In particular, alarm system owners, monitoring companies like Alarm Grid, and central stations, such as Alarm Grid's central station partner CMS, would be required to register with the city. Officials state that while the majority of alarm calls end up being false, responders are trained to respond to all calls with the same seriousness every single time.

Alarm Grid understands the frustration experienced by Panama City, FL officials. But we urge the city to take a step back and not enact a new drastic policy that would only make it more difficult for law-abiding citizens to get alarm systems. We think it's perfectly reasonable to require alarm systems to be registered, and it's also fair to fine users who repeatedly cause false alarms.

We hope that any registration fees for installing and maintaining security systems are kept to a minimum. Such fees make it more challenging for innocent end users to install alarm systems, and they are ultimately detrimental to alarm businesses. If the city decides that a registry of alarm systems will help prevent false alarms, then just please keep registration fees to a minimum. We understand that some small fees are necessary for maintaining the registry in the first place. But excessive fees will only deter everyday users from installing systems. We have found that low, reasonable fees, such as those in Pompano Beach, FL, tend to work best.

And if the city decides to fine users who cause false alarms, we hope that is also done within reason. One possibility is to give a warning for the first false alarm on a registered system, and then fining users for repeated offenses, or for those who fail to register their systems. Alarm Grid takes false alarm prevention very seriously, and we would expect other monitoring companies to do the same. We do our part to make sure that our customers are properly trained in this aspect of using their systems, and we highly doubt that anyone monitored through Alarm Grid is repeatedly making the same mistake. However, we do realize that mistakes happen, so we ask any city considering a false alarm policy to consider the issue with some leniency and understanding. Remember, the overwhelming majority of end users are not intentionally causing false system alarms.

If you want to learn more about false alarm prevention, we strongly recommend checking out these tips to prevent false alarms. That link is a great resource whether you are monitored through Alarm Grid, are considering signing-up for alarm monitoring, or even if you are monitored through a different company. We also invite any Alarm Grid monitored customers, as well as those who are still exploring their options for alarm monitoring, to email our team at support@alarmgrid.com to learn more about false alarm prevention. We are here to check your emails during our usual business hours of 9am to 8pm ET M-F. As always, we look forward to hearing from you!

Tags: , , ,

Comments


Posted By

We have learned that Alarm.com now allows users to receive two-factor authentication (2FA) links via email when logging into the Alarm.com website. This is in addition to the two-factor authentication via text message when accessing the Alarm.com platform. You can set up the feature in ADC.


When two-factor authentication is enabled for your Alarm.com account, your login process will have an added layer of security. Upon logging into your Alarm.com account via the website or mobile app on a device that you haven't saved, you will need to verify yourself by providing a secret access code. You will get this code via text message or email, depending upon how you have set up the 2FA feature. In other words, accessing your Alarm.com account on a new device will require your username, password, and access to either your phone or email. This is great for keeping your Alarm.com account as secure as possible.

Remember, 2FA will only be required when you access Alarm.com from a new device. For example, if you frequently access Alarm.com using the same web browser on your computer, and you tell Alarm.com that the device can be safely trusted, then you will only need to perform 2FA the first time you login, as well as anytime you login after clearing your cookies. Some users are hesitant to enable 2FA, because they don't want to have to go through the inconvenience of entering a secret code every time. Fortunately, that isn't a concern, as Alarm.com can remember your usual devices and skip the process for these trusted devices. You can also tell Alarm.com to trust your phone so that you will only need to perform 2FA if you get a new phone or if you are using a different mobile device than usual to access your account. Whenever you access Alarm.com through a new device, after completing the 2FA process, Alarm.com will ask you if you want to save that device so that you do not have to complete 2FA every time. This protects your account, while still maximizing convenience.

If you want to enable two-factor authentication for your Alarm.com account, start by logging into the Alarm.com website. Choose Settings on the left-hand side of the screen, then choose Login Information, and then Two-Factor Authentication. Then set up the feature through email address or text message by following the on-screen prompts. If you have questions, email us at support@alarmgrid.com. This email is also great if you are interested in starting new monitoring service for access to Alarm.com. We look forward to hearing from you!

Tags: , ,

Comments


Posted By

A few months ago, we made a post stating how a recent batch of Encore FF345 Smoke and CO Detector Listening Modules were not compatible with Honeywell Alarm Systems. It now appears that this issue has been fixed, and new units should properly work with Honeywell Systems as intended.

Due to the original issue, FF345 units with a date code of 01/2020 are unable to enroll with Honeywell Alarm Systems. These units will work properly with 2GIG Alarm Panels, but they are incompatible with the Honeywell Systems that they are advertised to work with. These units may also be incompatible with the 345 MHz Qolsys IQ Panel 2 Plus, which should also support these units, but this has been neither tested nor confirmed. Additionally, FF345 units with date codes ranging from 02/2020 to 08/2020 are likely also affected, but we are unable to confirm this.

Starting with date code 09/2020, a fix was implemented to make these units once again compatible with Honeywell Alarm Systems. Any FF345 unit with a date code of 09/2020 or later should be able to enroll with compatible Honeywell Panels. We have tested units with the 09/2020 date code, and we found that they were able to enroll with Honeywell Lyric and Honeywell LYNX Touch Systems as intended. However, our testing revealed that using these sensors may result in an E380 Sensor Trouble Condition occurring. The trouble condition may appear after a Fire Alarm or CO Alarm has been cleared on the system. The alarm condition is cleared by disarming the system twice. Upon further investigation, we found that the trouble Condition may clear on its own after some time, or a user can get it to clear manually with a third system disarm. This shouldn't have a major impact on performance, but it is important to keep the issue in mind if you intend on using an FF345 device manufactured from 09/2020 onward with a Honeywell Security System.

Remember, FF345 units with a date code older than 01/2020 should have no issue working with Honeywell Security Systems. Units with a date code of 01/2020 are known to not work with Honeywell Systems, and any unit with a date code from 02/2020 to 08/2020 is believed to be impacted as well. Units with a date code of 09/2020 or newer should work with any compatible Honeywell System, but they may experience the E380 Sensor Trouble Condition after an associated Fire Alarm or CO Alarm has been cleared. To check the date code on an FF345 unit, please refer to this helpful FAQ. That guide will tell you everything you need to know about checking the manufacture date on your FF345 so that you can determine if the unit is affected by the aforementioned issue.

If you have any questions about the FF345, or if you are looking to set up monitoring service for fire and/or CO detection, please email us at support@alarmgrid.com. We check our email from 9am to 8pm ET M-F. We look forward to hearing from you!

Tags: , , , ,

Comments


Posted By

We actually missed this about a month ago, but it appears Alarm.com has updated their website camera video feed viewer to use native browser streaming. This replaces the old Adobe Flash video viewer. This change does not come as a surprise, as Adobe Flash will soon reach its end of life.


Being able to live-stream the video feed for Alarm.com Security Cameras is one of the most important features of these devices. This can be done using the Alarm.com website or the mobile app. The change being discussed here affects streaming through a web browser and the Alarm.com website. Before, it was only possible to stream Alarm.com Cameras on the website by using the Adobe Flash video viewer. The update provides support for native browser streaming. This will make it easier for most viewers to access their camera feeds.

With Adobe Flash reaching its end of life by the end of the year, this update was basically a no-brainer for Alarm.com. Users will still have the ability to view their cameras using Adobe Flash until the end of the year. At that point, only native browser streaming will be supported for camera streaming through the Alarm.com website. Native browser streaming is easier to maintain, and it does not require users to install and update a Flash plug-in. Native browser streaming support was actually made available towards the end of September, but we never covered the news in our blog prior to now.

When you access your Alarm.com account through the website, the Video section will appear on the left if Video Surveillance has been added to your account. By clicking on this section then Live Video, you will be able to choose a camera for streaming. In the upper-right corner there will be a toggle bar for you to enable or disable the "New Viewer. When the bar is blue, the New Viewer is enabled, and native browser streaming will be used. This is the default option. You can click the toggle bar to turn off the New Viewer and use Adobe Flash streaming. This will only be available until the end of the year. After that, no Flash streaming will be available.


Please note that the New Viewer and native browser streaming only allows the live video stream to be maintained for a few minutes at a time. After that, you will get a message that the stream has "timed out". You will need to refresh the stream to resume viewing. This is normal, and it's just a limitation that comes with Alarm.com Camera streaming. Simply click the "Play" button that appears on the screen to refresh the stream and continue watching.

Also note that while the camera viewer now has native browser streaming available, the streaming video recorder (SVR) timeline page still uses Adobe Flash. Native browser streaming is not yet available for SVR functions on the Alarm.com website. We expect that to change in the near future, as Alarm.com continues to make their transition away from Flash. We do not have an ETA on when that will become available, but we will be sure to provide an update once we learn more.

If you have any questions about Alarm.com Camera streaming, or if you are interested in monitoring service to gain access to Alarm.com, please email us at support@alarmgrid.com. Remember that Alarm Grid customers need either a Platinum Level Plan or a Video-Only Plan to gain access to Alarm.com for camera streaming. Our team is happy to address any questions or concerns you may have via email. We check our email during our usual business hours of 9am to 8pm ET M-F. We look forward to hearing from you!

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

Comments