DIY Security Systems Posts

Posted By

Qolsys IQ Panel 2 and IQ Panel 2 Plus users will be pleased to learn that a new firmware update is available! Qolsys IQ Panel 2 Firmware Version 2.6.1 can be downloaded via patch tag right now. Alarm Grid recommends that IQ2 and IQ2+ users download the update at their earliest convenience.

Important Note: For those looking for the 2.6.1 Firmware File needed to update the panel using an SD Card, we will make that file available as soon as possible. Qolsys has not yet posted it. However, when the SD Card method is used, the panel will still need a WIFI connection, and active monitoring in order to be sure the panel updates properly. For this reason, unmonitored systems should not attempt this update method unless the user is absolutely sure the "Firmware2" update is not needed on the system. For those who need the "Firmware2" update, it is recommended that the Patchtag method of updating discussed below be used.

Before we get into how to download Firmware Version 2.6.1, we would like to discuss what the new update includes. This isn't a particularly loaded update, but it still includes some new features, plus some important fixes and general system improvements. For those reasons, updating at your earliest convenience is advised.

There is a new Sensor Group for motion sensors, that being Sensor Group (45) - Away/Stay Instant Non-Follower. This is just like Sensor Group (15) - Stay Instant, except that the new Sensor Group (45) will still have the system go into alarm if the sensor is faulted while the system is armed away or armed stay, even if an Entry/Exit Zone is faulted first. With the old Sensor Group (15), the system will not go into alarm if the sensor is faulted after (following) an Entry/Exit Zone. In other words, if you fault a sensor with Sensor Group (45) while the system is in its Entry Delay countdown, an alarm will occur, but if you do the same with Sensor Group (15) when the system is in its Entry Delay countdown, no alarm occurs.

For SD Card upgrades, there will be an auto-push of the "Firmware2" Patch from Alarm.com, assuming that the patch hasn't already been applied. This patch prevents certain IQ2 Panels from automatically rebooting at times. You can see more information about the Firmware2 fix from this prior blog post. The only other new feature release from the 2.6.1 release is that the IQ2 is now compliant with BS-8243 Standards in the United Kingdom.

All other changes for the IQ2 in 2.6.1 are general system improvements. As listed below:

  • Fixed an issue regarding SRF Sensors, outlined in TSB 210705. This issue prevented legacy SRF sensors from communicating with the IQ2 properly following an AC power loss condition. More information on the issue can be found here.
  • Stability improvements to dual-path communication with Alarm.com.
  • Improved push notification of message center messages while on Photo Frame screensaver.
  • Improved boot-up after performing a software update.
  • Improved doorbell camera streaming and push alerts when the panel is in the lock screen.
  • Alarm.com backend now shows username when arming/disarming from PowerG Keypads.
  • Corrected issue with an improvement from 2.6.0 so that silent and audible panics triggered from the panel are able to properly report as different CID codes to the central station.
  • Corrected issue from 2.6.0 involving daily & weekly communication tests with central station.

With that out of the way, let's explain how to apply the update! Like all of the other recent updates, users on Firmware Version 2.5.0 or 2.5.1 will need to stage upgrade to 2.5.3 first before upgrading to 2.6.1. But if you are on 2.5.3 or higher or on less than 2.5.0, then you can go right to 2.6.1. And as always, your system must be on at least 2.0.1 for any firmware update to be applied.

To get started applying the update, make sure your IQ2 or IQ2+ is plugged in and that its battery is charged. Your system must be connected to WIFI and actively monitored so that Alarm.com can determine if the Firmware2 update is required, and then send it to the panel via WIFI if it is. Begin from the main screen of the system. Press the small grey bar at the top. Pick Settings > Advanced Settings > enter the Installer Code if prompted (default 1111) > Upgrade Software > Patch Tag > enter iqpanel2.6.1 (must be entered exactly as shown) > OK > Upgrade Using Network. The update should then go through. Once it begins, do not touch the panel screen.

Remember, it will usually take about five (5) minutes for the update to be completed. You can then check the Software Version in the About Menu under the Software tab. This is good for confirming that the 2.6.1 Firmware Update went through as intended.


Please leave a comment down below with your thoughts on Qolsys IQ Panel 2 and IQ Panel 2 Plus Firmware Version 2.6.1. Don't hesitate to let us know about your experience with the panel or the firmware update. We want to hear your honest opinion and assist with any issues. Like always, stay tuned to the Alarm Grid Blog for more news and updates coming soon!

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

Comments


Posted By

Qolsys recently released a service bulletin describing an issue with certain IQ Hardwire 16-F units. This issue affects both the small enclosure and large enclosure versions. Under certain circumstances, affected units can signal a false tamper/tamper restore message for connected zones.

Qolsys TSB #210708, which was released on July 8, 2021, describes this issue, and the corrective action Qolsys is taking to remedy the problem. They do not provide a lot of information regarding what "conditions" bring about this behavior. We have asked for more detail, and if more information is forthcoming, we will provide updates here in our blog.

Rest assured that only a certain number of these devices are affected, and we will provide users with the necessary information to determine if they have one of these units. Qolsys IQ Hardwire 16-F units that were manufactured outside of the window in question are not affected and should not exhibit this behavior.

How to determine if your Qolsys IQ Hardwire 16-F small enclosure (SKU: QS7133-840) is affected:

On the unit itself, or on the box that the unit came in, check the Revision Sticker. This will appear as a bar code on the sticker and will be marked with SN: and DL: If the 4th character of the SN, moving from left to right, is a "C" then the Qolsys IQ Hardwire 16-F small enclosure should be returned/replaced. This sticker may be found on the rear of the unit and may require that you dismount the unit from the wall to get access it.

How to determine if your Qolsys IQ Hardwire 16-F large enclosure (SKU: QS7134-840) is affected:

On the Qolsys IQ Hardwire 16-F large enclosure, the way you determine the revision is the same, but the revision information is different. On these units the revision to be on the lookout for is "B" rather than "C". This sticker should also appear on the unit itself as well as on the box that the unit comes in. Since these devices come from the factory with an enclosure, the sticker may be on the enclosure rather than the printed circuit board. Unfortunately, it may also be on the back of the enclosure, requiring that it be removed from the wall to be accessed. When reading the sticker, the 4th character when viewing the SN from left to right is "B" on affected units. See the example below:

Qolsys has pulled back available affected stock to correct this issue. Units that may have been affected, but have since been pulled back into manufacturing and reworked or replaced, will sport a sticker that says "TEST OK".


If you purchase a Qolsys IQ Hardwire 16-F that falls within the Revision range discussed above, but the item has a "TEST OK" sticker affixed somewhere on the packaging or the unit itself, then you do not have to worry about this issue. If you purchased a Qolsys IQ Hardwire 16-F prior to the date that this notice was released, and your device falls within the revision range discussed above, then you should contact your distributor to discuss replacing the unit. Per Qolsys, you should do this even if you haven't observed the behavior described in this Technical Service Bulletin.

If you are an Alarm Grid customer, and you purchased an affected unit from Alarm Grid, you can contact us at support@alarmgrid.com. We are here Monday - Friday from 9am to 8pm ET. If you prefer to speak to us by phone, you can reach us at 888-818-7728. It is our pleasure to assist you with any and all of your alarm needs. Stay safe!

Tags: , , , , , , , , ,

Comments


Posted By

Welcome back from 4th of July! We have had a busy past couple of weeks at Alarm Grid since our last video recap. This time, we have seven (7) new videos to show you, including five (5) with Jorge and two with myself. We cover the PROA7PLUS, 2GIG Edge Cameras, and 2GIG GC2 Firmware Updates!

2GIG Edge: Alarm.com Cameras that Support Live Streaming

Jorge explains which Alarm.com Security Cameras can be streamed directly to a 2GIG Edge Alarm Panel. Most of the newer Alarm.com Cameras can be used in this way. In order for this to work, a camera must be paired with the same Alarm.com account used with the 2GIG Edge, and it must be enabled for panel streaming from the Alarm.com website or mobile app. Cameras can be streamed from the Smart Home Menu on the 2GIG Edge.

2GIG Edge: Alarm.com Cameras that Support 2-Way Audio via Live-Streaming

Jorge teaches users about two-way audio playback when live-streaming security cameras on the 2GIG Edge. While nearly all Alarm.com Cameras can be used for video streaming on the 2GIG Edge, only a smaller selection of cameras can be used for live audio streaming. Really, it's mostly the indoor residential cameras that do audio streaming. Most of the Alarm.com Commercial Cameras that support Power over Ethernet (PoE) and all Alarm.com Outdoor Cameras do not support two-way audio, as they typically do not have built-in microphones.


2GIG Easy Updater Tool: Updating

Jorge explains how to update the 2GIG UPDV Easy Updater Tool that is used to update the firmware on a 2GIG Go!Control GC2 Security System. The Easy Updater Tool contains the firmware update for the GC2 System. If the firmware on the Updater Tool is outdated, then you must update the Updater Tool by following the process outlined in this video. The current downloaded firmware on the Updater Tool will be displayed across the device screen when power is applied. This will let you know if you need to updater the Updater Tool.


2GIG GC2: Updating Using the Easy Updater Tool

Jorge teaches you how to use the 2GIG UPDV Easy Updater Tool to update the firmware on a 2GIG Go!Control GC2 Alarm Panel. After you have updated the firmware on the Updater Tool itself, you can then use the device to update the firmware on the GC2 Panel. Updating to the latest firmware version will ensure that you can use all of the released features for the system and that all of the latest hardware is supported. The LTE communicators for activating with Alarm.com and alarm monitoring will require a certain firmware version.


Honeywell Home PROA7PLUS: Delete a Zone

Jorge shows you how to delete a zone on a Honeywell Home PROA7PLUS or other ProSeries Alarm System. When you delete a zone, the associated sensor will no longer be programmed with the system. You would need to re-enroll it in order to continue using it. For the encrypted PROSIX Sensors and SiX Sensors, after deleting the sensor, you will then be able to enroll it with a new ProSeries Panel, provided that the sensor received the deletion signal from the panel. When deleting PROSIX and SiX Sensors, be sure the sensor is powered on and within range of the ProSeries Panel at the time of deletion.


Honeywell Home PROA7PLUS: Add a User Code

I show you how to add a new user code to a Honeywell Home PROA7PLUS Alarm System or other ProSeries Panel. All of the ProSeries Systems support up to (96) total user codes, so you should have no trouble giving everyone in your household or office their very own code to use when controlling the system. After you have added a user code, you can then go back into user settings to configure automatic Bluetooth disarming and Z-Wave lock functionality for the user.


Honeywell Home PROA7PLUS: Clear a Tamper Error

I show you how to clear a tamper error on a Honeywell Home PROA7PLUS or other ProSeries Security Controller. A tamper error occurs when the red tamper button on the back of the ProSeries Controller isn't held down properly. This is usually because the system has been taken off its backplate, or it isn't mounted on its backplate properly. Once you get the panel back on the backplate, you can then acknowledge the tamper condition by entering the system's Master Code when prompted.

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

Comments


Posted By

If you are looking for an affordable and effective way to monitor your home and see what's going on while you are away, then image sensors might be worth exploring. When used in conjunction with security systems, image sensors offer great function and convenience, all for a low price.


The simplest way to describe an image sensor is as a motion detection sensor combined with a still-picture camera. Unlike security cameras that capture full-motion video footage, most image sensors will only produce non-moving images. These are some of the most interesting and unique devices that you can use with a home alarm system. While image sensors certainly aren't for everyone, many end-users take full advantage of these peripherals and what they have to offer. Overall, image sensors can go a long way towards rounding out your security system and helping you get the most out of it.

Perhaps the best way to use image sensors is as alarm verification devices. If you live in a jurisdiction where verified response is required, then using image sensors is often the only option you can use to verify an intrusion, short of upgrading to full video monitoring service. Depending on the image sensor and system you are using, you may be able to achieve a setup where captured image sensor pictures are sent to the central station for immediate review. A trained operator can review the images and use them as sufficient proof of a crime in progress and use that as grounds for requesting emergency dispatch. You should check your local alarm codes and ask your monitoring company if verified response is enforced in your area. .Alarm Grid monitored customers can email us at support@alarmgrid,com. We respond to emails during our regular business hours of 9 am to 8 pm ET M-F.

You might be wondering why image sensors aren't more popular than they already are. While image sensors sound excellent in theory, and they often meet those high expectations in practice as well, they are somewhat quirky devices that can present a unique set of challenges. That's also not to mention that some image sensors have notable limitations and restrictions in how they can be used. This shouldn't scare you away from using them, but you should understand that you may have to overcome some obstacles to achieve the setup you want. And also understand that some systems cannot support image sensors in any fashion.

One thing to consider with image sensors is that they are always two-way communication devices. You might call them bi-directional sensors. With image sensors, it's not as simple as the sensor sending a signal to the alarm panel. The panel also needs to send signals to the image sensor. For example, if an alarm is triggered on the system, then the system needs to be able to tell the image sensor that an alarm has occurred, and the image sensor needs to capture a photo of the scene. Then the image sensor needs to turn around and send the image to the panel so that it can ultimately be distributed to an interactive security notification platform, and potentially the central station, and the end-user. The bi-directional communication is also what makes it possible for an end-user to request image sensor photos in real-time, when supported. Because of this, many alarm panels cannot support image sensors unless a specific image sensor transceiver module is added to facilitate two-way communication. And for some panels, image sensor support isn't even possible, as no compatible image sensors and/or image sensor transceivers exist for the panel.

Now that we have talked about image sensors in general, let's start exploring some of the specific models. To make this a bit more simple, we will try and focus on different options available on a panel-by-panel basis. Just like with regular sensors, image sensor support depends on which panel is being used. We will start by addressing the fact that most of the Honeywell Alarm Panels don't support image sensors, though there is an exception. The Honeywell Lyric, the Honeywell LYNX Panels, and the Honeywell VISTA Panels all lack image sensor support.

Interestingly though, the Honeywell Home and Resideo ProSeries Panels - PROA7PLUS, PROA7PLUSC, PROA7, and PROA7C - all have a fairly unique image sensor option in the Honeywell Home PROINDMV. This is the only image sensor presented in this blog that can be set to capture full-motion video (10 fps) or still motion images (320x240). Captured video and images can be viewed at the panel under Panel Camera History, with the ten (10) newest captures being available for viewing. Captured footage is also sent to Total Connect 2.0 for remote viewing. At the time of this writing, the PROINDMV is the only image sensor available for use with TC2. This also makes it the only image sensor we offer that can be used with an IP-only monitoring plan. We're sure that Resideo is also working on a way to make captured video and photos visible to central station operators, but we haven't heard of such a feature being set up just yet. There is also a downside to the PROINDMV in that you cannot use it to request video and/or images. In other words, no peek-in function is available for the PROINDMV, at least not at this time.

Moving onto the Alarm.com Security Systems, pretty much all of the most popular systems have some image sensor option available. It seems that Alarm.com has really embraced this technology and made it possible for almost all users to start using image sensors. We will start with the PowerG Image Sensors, which are some of the most popular image sensors we offer. As PowerG already operates using two-way communication, PowerG Image Sensors do not require any special modules or add-ons for support. You just need a system that supports regular PowerG Sensors, such as a Qolsys IQ Panel 2 Plus or a DSC PowerSeries NEO with an added PowerG Transceiver. And even better if you have an IQ2+ you will be able to view captured images from the alarm panel, in addition to viewing them from Alarm.com. One limitation however is that these image sensors will only capture images when they specifically trigger alarms on the system. Alarms caused by other zones will not result in the PowerG Image Sensors producing photos. There are currently two (2) PowerG Image Sensors, those being the DSC PG9934P Indoor Image Sensor and the DSC PG9944 Outdoor Image Sensor.

All of the other image sensors used with Alarm.com Systems require some type of hardware add-on for the panel. Sticking with Qolsys, adding the Qolsys IQ Card-IS to the original IQ Panel 2 will make it possible to enroll the Qolsys QZ81030-840 Image Sensor with the system. Technically, you can also add the IQ Card-IS to a newer Qolsys IQ Panel 2 Plus, but doing so will require it to "steal" the internal antenna used by the PowerG Daughtercard. This will result in the system having virtually zero useful wireless range with Power Sensors. As a result, anyone with an IQ Panel 2 Plus is strongly discouraged from going the route of the IQ Card-IS and QZ81030-840 combo, and just get PowerG Image Sensors instead. But if you do have an original IQ2, then using a QZ81030-840 with an IQ Card-IS is a great option.

The 2GIG Alarm Panels also support image sensors, but only if an image sensor module add-on has been added to the system. Starting with the 2GIG GC2 and its successor, the 2GIG GC2e, both systems can support the 2GIG IMAGE1 Image Sensor after a 2GIG XCVR2-345 Image Sensor Module has been added and installed. Unfortunately, for 2GIG GC2e users, adding the 2GIG XCVR2-345 will take away the system's ability to support 2GIG eSeries Encrypted Sensors. We have heard rumors in the past that a 2GIG XCVR2e-345 Image Sensor Transceiver Module would be specifically manufactured for the 2GIG GC2e so that the system could support both image sensors and encrypted sensors simultaneously, but it's looking increasingly likely as of late that such a release may never see the light of day. Even then, the 2GIG IMAGE1 is an older device, and it isn't known for producing the most detailed images. Still, for alarm verification purposes, it usually gets the job done. Both the IMAGE1 and the XCVR2-345 are still available on our website.

Moving onto the 2GIG GC3 and 2GIG GC3e, both of these systems support the 2GIG XCVR3-GC3 Image Sensor Module, to allow 2GIG IMAGE2 and 2GIG IMAGE3 Image Sensors to be paired. Don't let the need for the XCVR3-GC3 scare you away. The module is extremely affordable and very easy to install. It just uses a 4-wire connection with the system board, and it hangs out the back of panel. Unlike the issues experienced with the GC2e, adding the 2GIG XCVR3-GC3 to a GC3e will NOT take away the panel's ability to support 2GIG eSeries Encrypted Sensors. Furthermore, the supported image sensor devices for the XCVR3-GC3 are newer, and they are known for producing clearer images than the earlier IMAGE1. The 2GIG IMAGE2 is still relatively basic with its 320x240 QVGA resolution. But the 2GIG IMAGE3 really shines with its 640x480 VGA resolution, thereby making it one of the best image sensors on the market. These image sensors can be set to automatically produce images during alarm events, and a user can even manually request images using the "peek-in" feature on Alarm.com. All things considered, image sensor support for the GC3 and GC3e is surprisingly robust, and in our opinion, quite underrated. These really are some of the best alarm systems available for image sensor support, and we think more GC3 and GC3e users should take advantage of images sensors and what they can bring to one of these systems.

Unfortunately, we have to end this post with the sad story of image sensor support on the 2GIG Edge. While the 2GIG Edge has made a huge splash in the security industry, representing one of the most exciting panel debuts we have seen of late, image sensor support for the system is basically non-existent. To elaborate, the 2GIG Edge supports the same image sensor module add-on as the GC3 and GC3e, that being the 2GIG XCVR3-GC3, and it remains very easy to install, using the same 4-wire connection as before, and just hanging out the back of the panel. Once added, you can pair the 2GIG IMAGE3 Image Sensor with the Edge, but the 2GIG IMAGE2 is unsupported. We're glad that 2GIG chose the "better" of the two image sensors to work with the Edge, but we're still a bit surprised that the IMAGE2 can't interface with the Edge and the XCVR3-GC3 combo. Fortunately, just like with the 2GIG GC3e, adding the 2GIG XCVR3-GC3 to the Edge will not eliminate the system's ability to support 2GIG eSeries Encrypted Sensors.

However, and this is a big deal, the 2GIG Edge with 2GIG XCVR3-GC3 will only see the 2GIG IMAGE3 as a standard motion detection sensor. In other words, the Edge cannot receive any of the captured images from the IMAGE3. And since the Edge can't get the captured images, it therefore cannot forward them to Alarm.com and/or the central station. This makes the 2GIG IMAGE3 nothing more than a fancy motion sensor for the Edge. It's super unfortunate, and one of the saddest things to learn about the 2GIG Edge. There is a ray of hope though. 2GIG has stated that this behavior between the Edge and IMAGE3 is not intentional, and they are working on a firmware fix to provide true image sensor support for the Edge in the future. No ETA for a fix is currently available, but we are hopeful that the 2GIG Edge will one day be able to carry on 2GIG's legacy of having some of the best image sensor support in the industry. For more information, we have a blog on the limitations of the 2GIG Edge in regards to image sensor support, which you can view here. And you can certainly expect Alarm Grid to provide an update once image sensor support for the 2GIG Edge has been fixed and made to work as intended.

We hope that this post has opened up your mind towards adding image sensors to your security system. They really are some useful and handy devices when set up properly. Users in verified response jurisdictions who aren't quite ready to make the jump to video cameras and the more expensive monitoring plans that come with them can often get started with image sensors at very little cost. And with a bit of testing and configuration, yours can truly be great and help you keep your home safe. If you have any thoughts or questions about image sensors, please leave them in a comment down below. We are eager for some fun and enthusiastic discussion about image sensors and what they can offer for home security. And don't forget to keep checking the Alarm Grid Blog, as we will have some more great topics to cover and discuss in the near future.

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

Comments


Posted By

We have a quick and easy blog post for you today, this time covering local zones on Honeywell Home and Resideo ProSeries Alarm Panels - the PROA7PLUS, PROA7PLUSC, PROA7, and PROA7C. Local zones cannot trigger intrusion alarms to alert the central monitoring station for emergency dispatch.

Almost anyone who gets a security system will want to get it monitored so that they can receive automatic emergency dispatch if an intrusion occurs while they are away. However, you might also have some zones of your home or office where you want a "local", on-site alert to activity, and you also want to have Total Connect 2.0 alerts set up for the zone, but you don't want the central station to be notified to an alarm that occurs from the zone. Today, we're sharing a tip for achieving that type of functionality for a zone on a ProSeries Panel.

One thing to note is that if you are familiar with the Response Types for the Honeywell Lyric, then many of the same "rules" apply. This makes perfect sense, as the Honeywell Lyric is the predecessor system to the still relatively new ProSeries Control Panels. But having said that, many of the Response Types found on the Lyric were never brought over to the ProSeries Panels. Maybe they will be introduced in a later ProSeries Firmware Update, but we have no way of knowing if that will happen. Regardless, it can be a bit more challenging to set up "local" zones on the ProSeries Systems due to their more limited selection of Response Types. Nonetheless, we have a cool tip that we would like to discuss.

If you have a zone that you want to produce a local Chime and/or Voice Annunciation at your ProSeries Panel, as well as any of your PROWLTOUCH or PROWLTOUCHC Touchscreen Keypads, but you also don't want the zone to be able to cause any alarms or alert the central station, then you can set the Device Type to "Other" and the Response Type to "Garage Monitor". But before you set the Device Type to "Other", go and set the Chime setting first. The reason why you want to set the Chime first is because that setting becomes locked and unable to be changed after you set the Device Type to "Other". Whatever Chime setting you have set will be locked in and applied. By setting the Chime first, you can have a custom Chime setting, rather than the default option of Disabled when you set a "Garage Monitor" Response Type. With "Garage Monitor" set, your panel and keypads will announce the faulted zone and make whatever Chime sound is set for local alerts. You can also set up notifications from Total Connect 2.0 for this zone. Meanwhile, you can rest easy in knowing that this Garage Monitor Zone will never be able to cause an alarm on your system or result in the central station being notified. This is truly a local zone with the ultimate customization!

This ties-in with some other general tips. When you set the Device Type as "Other", all of the Response Types become available, though there are some PROSIX Sensors that may not allow for this type of programming. Also, the Device Type of "Other" is not spoken aloud when set. In other words, if you have Zone Descriptor 1 set as "Bedroom", the panel won't speak "Bedroom Other" if you have "Other" as the Device Type. It will just say "Bedroom", and nothing more. This is good to know, as if you're ever having trouble getting the desired Response Type to be made available, then setting "Other" as the Device Type can be the trick to getting the option you want. Just be careful when working with certain types of PROSIX Sensors, as they can be a bit more restrictive.

Do you have any topics you would like to see us cover on the ProSeries Panels, or on any other of our favorite security systems? Leave a comment down below, and let us know. We might just discuss it in a future blog. As for now, we hope that this simple trick helps you get the most out of your Honeywell and Resideo ProSeries Systems. Local zones are really useful in certain situations, and knowing little tips and tricks like this one that we covered today can really open up the door for more ways on using your security system. Anyway, that's all for today. Please stay tuned to the Alarm Grid Blog for more security news and helpful tips on using your system. We're always happy to help, and you can expect more great content from us coming soon!

Tags: , , , , , , , , ,

Comments


Posted By

Alarm Grid has learned that its supplier for Honeywell Home and Resideo ProSeries Panels will have ProSeries Alarm Systems pre-installed with the latest Firmware Version 3.591.92.0 in-stock and ready to ship starting on June 28th. This is is great news for anyone considering these systems!

For reference, the ProSeries Security Panels include the Honeywell Home PROA7PLUS, the Resideo PROA7PLUSC, the Honeywell Home PROA7, and the Resideo PROA7C. When these systems were first released, they did not include local programming support, meaning that all system programming, including the enrollment of new sensors, had to be completed remotely by the user's alarm monitoring company. It wasn't until System Firmware Version 3.591.92.0 that Local Programming Mode became available, allowing end-users to program their ProSeries Systems themselves. In addition to Local Programming Mode, the update also introduced support for additional PROSIX Series Sensors, common lobby partition support, local alarm mode, severe weather alerts from Total Connect 2.0, and more. If you would like more information on Firmware Update 3.591.92.0, we strongly encourage you to view this blog on the subject.

It is important to note that just because you order a ProSeries Alarm Panel on or after June 28th does not necessarily mean that the system you receive will have Firmware Version 3.591.92.0 pre-installed. It is possible that our supplier may still have older stock to get rid of first, and they may not begin shipping panels with Firmware Version 3.591.92.0 pre-installed until their older stock has been depleted. We have no control over which stock they decide to ship, so we cannot predict whether the panel you receive will be on the latest firmware or older firmware. You can check the firmware version for your ProSeries Panel after it has been powered on by clicking on the three (3) horizontal bars menu button on the home screen, and then selecting Tools, entering the system's Installer Code (default 4112), selecting System Information, and then clicking on the General field. The panel's installed Firmware Version will be displayed on the screen. Remember, you need Version 3.591.92.0 or higher for local programming support.

If you receive an older ProSeries Alarm Panel without the latest firmware, then it is not the end of the world. Once you get the system activated for alarm monitoring service with Alarm Grid, or with another company, the firmware can then be pushed down over-the-air (OTA) to the ProSeries Panel. Please note that this will require an active internet communication pathway for the ProSeries Panel. The Honeywell Home PROA7PLUS and Resideo PROA7PLUSC can readily connect with a WIFI network for this purpose, thanks to the Honeywell Home PROWIFIZW Module that comes pre-installed inside these systems.

But if you have a PROA7 or a PROA7C, then you must add a PROWIFIZW or a PROWIFI to get the system connected to the internet before a firmware update can be sent down. Keep in mind that a ProSeries System cannot receive a firmware update across cellular. This means that it will not be possible to send a firmware update if the ProSeries Panel is using a Honeywell Home PROLTE-A or Honeywell Home PROLTE-V as its only communicator. You must add one of the aforementioned IP communicators and connect the system to a WIFI network for the firmware update to be sent down. Additionally, the system must be activated for monitoring, must have AC power, must have a battery present iin the panel, and must not have an alarm memory condition at the time the firmware update is sent down. If these conditions aren't met the process will fail.

If you are an Alarm Grid monitored customer and you need to request a firmware update for your ProSeries Security System, then you should email us at support@alarmgrid.com to get started. Remember that our business hours for checking and responding to incoming emails run from 9 am to 8 pm ET M-F. If you have any thoughts or personal experiences with the ProSeries Panels from Honeywell Home and Resideo, then please share them in a comment down below. We would love to hear what you have to say. And remember to keep checking the Alarm Grid Security Blog for more news and updates coming soon!

Tags: , , , , , , ,

Comments


Posted By

It's time for the Alarm Grid Video Recap! There are five (5) new videos this week. For the first time in awhile, I did not appear in any videos. I'll hopefully be back next week. Instead, Jorge really took over, doing four (4) videos. Julia also made a rare video appearance. On with the show!

2GIG Edge: Pair the 2GIG PAD1-345

Jorge shows you how to pair the 2GIG PAD1-345 Keypad with the 2GIG Edge. The PAD1-345 is a very basic keypad device that has been around since the days of the 2GIG GC2. As a very limited keypad, the PAD1-345 can be used to arm/disarm and trigger system panics. The 2GIG PAD1-345 cannot be used to bypass sensors, and it also does not display system status. Additionally, the PAD1-345 can only control the system partition that is has been assigned, and it cannot "switch" to other partitions.

2GIG Edge: Finding the IMEI Number

Jorge shows you how to find the IMEI Number on a 2GIG Edge Alarm System. When working with a 2GIG Edge, the IMEI Number may also be referred to as the panel's Serial Number. This is an important piece of information that you need when activating the system for alarm monitoring service. It is associated with the panel's built-in cellular communicator, which is registered with Alarm.com as part of the activation process. All outbound signals for the 2GIG Edge are sent through Alarm.com.


2GIG Edge: Connect to WIFI

Jorge explains how to connect the 2GIG Edge to a WIFI network. The 2GIG Edge can use WIFI connectivity as a secondary pathway for communicating with Alarm.com. However, WIFI cannot be the only communication pathway, as Alarm.com requires that a cellular communication path is configured and set up with their servers. Most users will configure the WIFI pathway anyway, as most monitoring providers will not charge extra for internet monitoring, and almost all homes and offices have WIFI readily available.

2GIG Edge: Sending a Cell Test

Jorge teaches you how to perform a cell test on a 2GIG Edge Security Panel. A cell test is performed at the end of the system's activation process, as a way of verifying communication with the Alarm.com servers. You may also perform a cell test at any time after the activation to ensure that the system is still communicating properly. As part of the cell test, the system checks that it can successfully send signals to the Alarm.com servers, and also successfully receive incoming signals from Alarm.com.

2GIG GC2: Updating Firmware Using Updater Cable (UPCBL2)

Julia teaches you how to update the 2GIG GC2 using the 2GIG UPCBL2 Updater Cable. Normally, the easiest way to update a GC2 is to activate the system for monitoring service, and then push down an over-the-air (OTA) firmware update from Alarm.com. But if you have an old GC2 that is not on a high enough firmware version to get connected with Alarm.com, then you must update using the Updater Cable or the 2GIG UPDV Easy Updater Tool. Alarm Grid also has a 2GIG GC2 Firmware Updates Page that you can check out.

Tags: , , , , , ,

Comments


Posted By

We want to inform 2GIG Edge users, especially those who may install their own system, to a special warning put out by 2GIG. The warning identifies a potential wiring mistake that could result in permanent damage to the 2GIG Edge Alarm Panel. The entire warning put out by 2GIG can be seen here.


The 2GIG Edge receives primary power from the 2GIG AC1 Plug-In Transformer. This transformer is rated at 14VDC, 1.7A. You must add your own alarm wire to complete the connection. Since DC power is being used, proper polarity must be observed, both at the transformer and at the panel. At the transformer, the red wire should connect to positive (+) terminal, and the black wire should connect to the negative (-) terminal.

Then, at the panel, the red wire for positive (+) power should connect to the DC IN+ terminal. The black wire for negative (-) power should connect to the DC IN- Terminal. Or alternatively, if you are using a Honeywell LT-Cable, then you can simply plug the barrel connector in the DC IN Barrel Port. Following this process correctly will help ensure that you do not accidentally damage your 2GIG Edge.

Where the concern arises is that there are actually two (2) sets of terminal blocks on the 2GIG Edge Panel for connecting wires. And unfortunately, 2GIG didn't exactly make it super clear as to which set of labels goes with which terminal block. The best way to figure it out is in the fact that one set of terminal blocks is shorter than the other terminal block set. The set for providing power is the smaller terminal block with six (6) terminals, not the larger terminal block set with eight (8) terminals. You can see this in the image above.

The DC IN+ and DC IN- Terminals, along with the DC IN Barrel Port, are identified as the Power In Terminals. Those are the ports you want to use when providing power, whether you are using traditional alarm wire and you use DC IN+ and DC IN- (making sure to observe polarity) or you have a Honeywell LT-Cable and simply plug into the DC IN Barrel Port. If you do use DC IN+ and DC IN-, then make absolutely sure you are connecting to the terminal block with only six (6) terminals.

The potential problem arises in the other, larger terminal block with eight (8) terminals. This is known as the DCOUT+ Terminal Bock. And to make matters confusing the top two (2) wire terminals on this set have names that may make you think they are used for providing primary power to the system. But in reality, connecting primary system power here could seriously damage the system. These two (2) misleading wire terminals are labeled GND and AUX+, but these are output terminals.

Simply put, you do NOT want to use these terminals for providing system power. Again, the easiest way to avoid doing this is to make sure you are using the smaller terminal block with only six (6) wire terminals, NOT the larger terminal block with eight (8) wire terminals. Of course, if you use a Honeywell LT-Cable and the panel's DC IN Barrel Port, then this isn't really a potential hazard. There is only one barrel port and no way to mix it up.

The lesson of the day here is to be very careful when you are connecting power wires to the 2GIG Edge. Use the DC IN+ and DC IN- Terminals on the smaller block with six (6) terminals. The red positive (+) wire should go to DC IN+, and the black negative (-) wire should go to DC IN-. Or use a Honeywell LT-Cable and the DC IN Barrel Port. Do NOT use the GND and AUX+ Terminals on the larger block with eight (8) terminals. Making that mistake could potentially damage your 2GIG Edge System. Always be safe and smart, and make the correct wiring connections!

If you have any thoughts on the 2GIG Edge, or if you have any personal experience in wiring the system for power, then please feel free to share what you would like in a comment down below. We would love to hear from you! And remember to stay tuned to the Alarm Grid Blog for more tips and security news coming soon.

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

Comments


Posted By

After much waiting and anticipation, Resideo has delivered the firmware update we have all been wanting for ProSeries Panels. ProSeries System Update Version 3.591.92.0 for PROA7PLUS, PROA7PLUSC, PROA7, and PROA7C introduces local programming mode, as well as other system enhancements.

First, we want to cover how to receive the update. Only monitored ProSeries Systems can be updated. You must have your ProSeries System online and connected with the AlarmNet servers in order for the over-the-air (OTA) update to go through successfully. The system must be connected with a WIFI network, as the update cannot be sent across cellular. Remember that while the PROA7PLUS and PROA7PLUSC both come with integrated WIFI network cards, the PROA7 and PROA7C can only connect to WIFI if a PROWIFIZW or PROWIFI has been added separately.

As a one-time event Alarm Grid is planning to send down the new firmware update to all its monitored customers with ProSeries Panels sometime in the coming days. This OTA update is being done in one mass shot to try to update as many users as possible all at once. No special action should be required on your part. Just have your ProSeries Panel powered on and connected to WIFI. While this process isn't perfect, and there will inevitably be some users who miss out on the update for one reason or another, this is the best way for us to ensure that as many end-users as possible have their panels updated. Remember, we can only update ProSeries Systems that are actively monitored by Alarm Grid. If you have a different monitoring provider, then ask them to help you update your system.

If your automatic OTA update fails for whatever reason, or if you didn't have your panel ready at the time of the mass OTA update, then you can request that the update be sent down manually. Alarm Grid customers can email support@alarmgrid.com to request a manual OTA update. Please make sure that you have your ProSeries Panel powered on and connected to WIFI when we push down the OTA update, or else the update process will fail. Our support hours run from 9 am to 8 pm ET M-F, so keep that in mind when contacting us. Furthermore, we cannot push down a manual OTA update to your panel if you receive alarm monitoring service from a different provider. If you are monitored by a different company, then you should instead reach out to your provider for further assistance.

There are some big highlights here in ProSeries Firmware Update 3.591.92.0. Obviously, the elephant in the room is the introduction of local programming mode. Previously, users were forced to have all system programming completed remotely by their monitoring provider. This included basic system setup tasks like enrolling sensors and configuring zone settings. Not only will the introduction of local programming make activations easier for professional technicians, but it will also empower end-users and give them greater control over their systems. This is a huge deal, as it officially makes the ProSeries Panels DIY-friendly alarm systems.

There are other major introductions in ProSeries Firmware Update 3.591.92.0, though they are likely to be overshadowed by the introduction of local programming. Nonetheless, we are still very excited about these smaller, but still important, introductions. For one, there is a boost to system partitioning, as a common lobby partition option is now available. You can set Partition 3 or Partition 4 as the common lobby, depending on how many partitions are being used. The highest number partition will always be the common lobby, and you must have at least 3 partitions in order to enable the common lobby feature.

There are some principles to keep in mind regarding the lobby function. You cannot set both Partition 3 and Partition 4 as the common lobby. Only one can be the common lobby partition at any given time. The way that the common lobby partition works is that disarming any other partition will also disarm the common lobby partition. Additionally, if ALL other partitions are armed, then the common lobby will also automatically arm. The only way you can arm/disarm the common lobby partition independently is if all the other system partitions are in an armed state. All system users have authority over the common lobby partition. Finally, any 24-hour zones assigned to the common lobby partition will sound on keypads of all partitions, but you can only silence alarms and troubles from these zones using the common partition keypad. Any faulted zone in the common lobby partition will be automatically bypassed when the common lobby partition is armed, even if it is armed automatically due to all other partitions being armed.

The ProSeries Firmware Update 3.591.92.0 brings support for some upcoming PROSiX Sensors that we hope to have available on our site very soon. Specifically, we are talking about support for the PROSiX Wireless Repeater (PROSIXRPTR) and support for the PROSiX Wireless Heat (PROSIXHEAT).

A local alarm mode is now supported, meaning you can trigger a localized system alarm, complete with siren, but without the system reporting out. This can be good for scaring away on-site intruders, while also resting easy in knowing that the authorities will not be sent to the premises. This is basically how the system behaves if an intrusion alarm occurs on a system that is not being monitored. When local alarm mode is enabled, all communication to AlarmNet is halted, including access to Total Connect 2.0 features.

The panel will now provide severe weather alerts. This feature requires that the system is set up with Total Connect 2.0 and the corresponding weather package. Remember, this is only possible if the system is monitored and set up with Total Connect 2.0. Ask your monitoring company about receiving weather alerts on the panel.

If you are using the system in Canada, you can now use the PROTLE-CN Communicator. This communicator may be carried by Alarm Grid in the future. Alarm Grid is not provided with the option to sell the Resideo and Honeywell Home lineup of Canadian communicators, however, we can get potential customers in touch with a Canadian distributor. Once you obtain a PROLTE-CN elsewhere, then we will be able to set it up for monitoring.

On the PROA7PLUS and PROA7PLUSC only, you can now stream the live video feed for Total Connect 2.0 IP Cameras and SkyBell Video Doorbell Cameras from both the Panel, as well as any PROWLTOUCH or PROWLTOUCHC Keypad. The PROA7PLUS and PROA7PLUSC also now both support disarm photos from the PROWLTOUCH and PROWLTOUCHC Keypads. Again, these two (2) features are for use with the PROA7PLUS and PROA7PLUSC only.

For all ProSeries Panels, there is backlight timeout improvement. You can now set the backlight timeout for a ProSeries Panel or a PROWLTOUCH/PROWLTOUCHC Keypad to Disable and have the screen go completely dark. This is instead of going to the "inactivity screen" that shows the weather, time & date, 1st thermostat temperature, partition arming status, panic icons, and CELL/WIFI/AC/BLE status.

Other updates include:

  • You can now have Partition 1 Disarm automatically when a Z-Wave Door Lock is UNLOCKED.
  • There are improvements to the 7-Day Z-Wave Thermostat Schedule on Total Connect 2.0.
  • There is now optional device supervision for PROWLTOUCH & PROWLTOUCHC Keypads.
  • The PROSIX Wireless Technology is now more accurate in displaying signal strength and remaining battery life.
  • There is now improvement in enrollment range for PROSIXSMOKEV and PROSIXHEATV.
  • There is now improved multi-language display on the PROSIXLCDKP Keypads.
  • If you use a cellular communicator in Canada then you may notice Cellular Roaming Improvement.
  • Updates to the ProSeries Cyber Security.
  • The PROINDMV Indoor Motion Viewer and Z-Wave Devices are now supported during the AlarmNet360 Panel Replacement Process. This is only for the PROA7PLUS and PROA7PLUSC.

Are you excited about this new update? What do you think about local programming finally being available for the ProSeries Panels. Is there some other new feature that you're also really eager to check out. Let us know in a comment down below. And stay tuned to the Alarm Grid Blog for more news and updates coming soon.

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

Comments


Posted By

Alarm Grid is here with another video recap! This recap marks the return of Jorge to our videos after a long absence. Each video in this week's edition covers the 2GIG Edge, and we feel like we have some really helpful content to share with you. Anyway, let's get started with the video recap!

2GIG Edge: Activating on Alarm com

Jorge shows you how to activate the 2GIG Edge System with the Alarm.com service. Getting the 2GIG Edge set up with Alarm.com is an important part of getting the system monitored. All system alarms and other notifications are sent to the Alarm.com servers before being passed on to a central station and/or the end-user via text and/or email, depending upon the user's alarm monitoring plan. The 2GIG Edge comes ready to activate with Alarm.com using its built-in LTE cellular communicator. You can also set up optional IP connectivity using the panel's integrated WIFI card. Adding WIFI allows the use of the 2GIG Edge Remote Keypad as well as the Live Streaming feature for Alarm.com cameras.

2GIG Edge: Deleting a Zone

Jorge teaches you how to delete a zone on the 2GIG Edge. Zones are never really deleted from the 2GIG Edge. The system always has 100 wireless zones. But whether all of them are currently active or not is another story. When someone talks about "deleting" a zone, they mean clearing out the zone settings so that the zone can be used with a new sensor instead. This is normally done if you run out of zones and need to free one up, or if you simply want to stop using a sensor with the 2GIG Edge, or need to replace a sensor on the system.


2GIG Edge: Deleting Door/Window Sensors

I show you how to delete a door/window sensor from a 2GIG Edge. The process for deleting a door/window sensor from the Edge is the same as any other sensor type. You need to enter into zone programming, select the zone associated with the sensor you want to clear from the system, and then tell the Edge to reset that zone. The zone would then need to be reprogrammed from scratch in order to support the same sensor, or a new sensor programmed in its place. This could be another compatible door/window sensor, or any other type of compatible sensor.


2GIG Edge: Changing the Master Code

I show you how to change the Master Code on your 2GIG Edge Security System. The Master Code is the system's primary code for disarming, and also arming if Quick Arm is disabled. Changing this code is very important for security purposes, and it is one of the very first things you will do after getting the 2GIG Edge System. The 2GIG Edge default Master Code is 1111, and you will certainly want to change it to prevent a savvy intruder from trying that code to disarm your system.


2GIG Edge: Programming a Zone

Jorge shows you how to program a zone on your 2GIG Edge. Programming zones is an important task for setting up the system. This is the act of assigning sensors to empty system zone slots. You must configure the zone settings so that the system responds as intended when the sensor is faulted or activated. You will also set various settings for the zone, like its chime sound, whether or not RF supervision will be used, whether the system will report if the zone causes an alarm, and even the zone name.


2GIG Edge: Bypassing Zones

I teach you how to bypass zones on the 2GIG Edge. Bypassing zones is the act of telling the system to temporarily ignore specified zones so that they do not cause any system response when activated. Later, when you are ready to use the bypassed sensors again, you can then un-bypass them so that they are again used with the system like normal. This is a good alternative, and honestly much quicker and easier than having to delete zones entirely and then reprogram the zones from scratch.

Tags: , , , , , ,

Comments