Industry News and Discussions Posts

Posted By

Alarm Grid is happy to announce that the Honeywell Home PROSIXRPTR Wireless Repeater is now available for purchase. The wireless repeater works with Honeywell Home and Resideo PROSIX Sensors and Honeywell SiX Sensors used with the ProSeries Security Panels, including the PROA7PLUS.

If you aren't familiar with wireless repeaters, these devices effectively double the range of compatible wireless sensors. This works by taking the wireless signal sent out from a wireless sensor and sending it out a second time, thereby effectively repeating the signal and doubling the sensor's range, assuming that the repeater module is placed strategically. The PROSIXRPTR is the first wireless repeater released from Resideo since the Honeywell 5800RP Wireless Repeater which is used to repeat the wireless signals of Honeywell 5800 Sensors. The new PROSIXRPTR is also the first-ever encrypted wireless repeater released by Resideo. Up to two (2) PROSIXRPTR devices can be used with a ProSeries System, with each repeater being placed in a different direction from a centralized ProSeries Panel.

There's a lot to take in with the PROSIXRPTR, so we'll do our best to cover everything here. The first thing we want to note is that the PROSIXRPTR is not a "plug-and-play" device, as you may be accustomed to with most wireless repeaters. In other words, the PROSIXRPTR will not begin repeating wireless signals until it is enrolled with a ProSeries Panel. These panels include the aforementioned PROA7PLUS, the Resideo PROA7PLUSC, the Resideo PROA7C, and the Honeywell Home PROA7. Any ProSeries Alarm System in need of a PROSIXRPTR Wireless Repeater must be on at least Firmware Version 3.591.92.0, which you can read about in greater detail here. The reason why the PROSIXRPTR needs to be enrolled with the alarm panel is because it is interacting with encrypted signals, and it needs to know sensitive network information to do its job successfully. Although you can have two (2) different PROSIXRPTR modules paired with a single ProSeries Panel, the two units will not communicate or "talk with" each other in anyway, and you cannot use a "series" setup to "triple" the range by having a sensor signal bounce off of one PROSIXRPTR to another PROSIXRPTR on its way to the panel. The PROSIX or SiX wireless signal will only be recognized by a single PROSIXRPTR, it will get repeated once, and will then end up at the ProSeries alarm panel.

There are other limitations affecting the PROSIXRPTR Repeater that should be discussed. While the unit can repeat SiX Sensors used with a ProSeries Alarm Panel on a high enough firmware version, the PROSIXRPTR cannot repeat the signals for SiX Series Sensors used on a Honeywell Lyric Security System. Remember, the PROSIXRPTR must enroll with the panel it is being used with. The unit has no way of integrating with the Lyric, and it cannot repeat wireless SiX Series signals used with that system. Unfortunately, Resideo never released a repeater for the Lyric and SiX Sensors, so that is just a limitation that Lyric users will have to live with, at least for now. The PROSIXRPTR also cannot repeat the signals of any legacy sensors that are being used with the Honeywell Home PROTAKEOVER Module. There are various legacy wireless repeaters available, so please reach out to us at support@alarmgrid.com during our usual 9am to 8pm ET M-F business hours if you need help figuring out which one to get for your alarm system.

One other thing we want to note with the PROSIXRPTR is that while it comes with its own transformer and backup battery, it does not come with any cabling for connecting the transformer. Make sure you have some around when you go to set it up. The unit supports a wire run of up to fifty (50) feet (~15.2 meters) when using 18 AWG cabling, and the maximum distance goes down if thinner cabling is used, so make sure to observe the permitted wire runs. Alarm Grid offers alarm wiring on its website if you need some. We even offer 10 ft., 15 ft., and 25 ft., pre-cut lengths of 22 gauge, 4-conductor wire. Or, you should be able to find some at your local hardware store. You can also use a Honeywell LT-Cable if you don't want to prepare your own wiring.

The PROSIXRPTR can be purchased on our website now! Please email us if you have any questions. Also, don't forget to leave a comment down below to share your thoughts on this new unit. We would love to hear what you have to say. And of course, keep paying close attention to the Alarm Grid Blog if you want to hear the latest security news, tips, and product releases. We'll be back soon, so stay posted!

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

Comments


Posted By

The leading keypad option for the Qolsys IQ Panel 2 Plus is unquestionably the Qolsys IQ Remote. This innovative touchscreen keypad mimics the screen of an IQ2 or IQ2+, and it allows for security and automation control from a second on-site location. But sadly, it lacks a replaceable battery!

To be clear, the Qolsys IQ Remote does have a backup battery. When AC power for the IQ Remote is lost (either due to the transformer being unplugged or an electrical outage), the backup battery will keep it running for several hours. But like any rechargeable battery, the one inside the Qolsys IQ Remote has a limited useful life. And once that useful life is up, the battery cannot be replaced with a new one. This means that the IQ Remote Keypad will need to be plugged in at all times in order to be used. If AC power becomes lost for any reason once this happens, then the IQ Remote will immediately power down. Also, the keypad will then always show a low-battery warning that can never be cleared. While not completely debilitating, it is an unfortunate aspect of the Qolsys IQ Remote device.

When we spoke with Qolsys about this issue, they assured us that the IQ Remote battery is "very long lasting", and a user shouldn't encounter this issue for at least ten (10) years from the initial manufacture date, assuming that the battery is cared for properly. Additionally, the company has stated that they have not received any excessive reports of IQ Remote battery failures since its release more than five (5) years ago. But it's fair to expect that Qolsys might be hearing about this issue more frequently in about five year's time when a large number of Qolsys IQ Remote batteries begin failing! At least most IQ Remote Keypads are not carried or transported around, and most users just leave them mounted in a single location. If a user gets a backup generator for the device, then the issue might not cause serious problems.

Still, this is definitely a disappointing limitation of the Qolsys IQ Remote Keypad. We hope that Qolsys will see this message and consider updating the IQ Remote to support an end-user replaceable battery. A well-constructed device can certainly be used for more than 10 years, but it needs a replaceable battery option so that it can truly go the maximum distance. Also, for anyone considering the IQ Remote for use with an IQ Panel 2 or IQ Panel 2 Plus, we still think it's a great keypad option, and we still recommend using it. Just be aware that after ten (10) years or so, the battery will probably stop holding a charge and will begin not working as intended. The keypad will need to be plugged in and receiving power at all times once this happens, or else it will power down immediately. Our hope is that Qolsys redesigns the IQ Remote Keypad to put an end to this issue. Then a user can buy a new battery once the original reaches its end-of-life, install the new one, and keep using this great keypad!

For now, we would love to hear what you have to say about the Qolsys IQ Remote lacking a replaceable battery. Does this issue influence your decision in buying this keypad? Or do you think that it's not a major concern? Please let us know your thoughts in a comment down below. We're sure that many users who buy this keypad, and also those who have bought it in the past, may be surprised to learn that the device's backup battery cannot be replaced. And if we ever learn of Qolsys updating the IQ Remote to fix this issue, or releasing a successor keypad with a replaceable battery, then we will be sure to let you know in the Alarm Grid Blog so that you can make an informed buying decision. Please stay tuned for more security news and updates coming real soon!

And before we forget, we wish everyone in the United States a Happy Independence Day (4th of July) over this upcoming weekend! We are open today, Friday, July 2nd, and we will also be open for business as usual on Monday, July 5th. We look forward to serving you!

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

In an effort to reduce false alarms, the city of Asheville, NC has revised existing policies regarding security systems. Central station operators responding to alarms in Asheville must now use Enhanced Call Verification (ECV) before dispatching. New fines and fees have also been introduced.

Asheville has had an alarm ordinance in-place since at least 2002. The newly revised ordinance was passed unanimously by the Asheville City Council during a recent meeting on June 22. No comment was made by the council in response to the unanimous passing of the revised ordinance. However, some local police representatives at the meeting spoke out in favor of the revised ordinance. For a complete look at the revised policies, you may review this staff report uploaded by the city of Asheville.

As part of the revised policies, the use of ECV is now required before a central station operator is permitted to dispatch the authorities in response to an alarm. This means that an operator must make a minimum of two (2) attempts to contact the end-user for alarm verification purposes before they can request that local Asheville authorities visit the scene. The use of ECV is not required for fire alarms or user-triggered panic alarms. It is also not mandated in cases where it has already been confirmed that a crime has been committed.

According to representatives of the Asheville Police Department (APD), the use of ECV reduces false responses by 40%. A report produced by the APD states that local Asheville authorities responded to more than 15,600 burglar alarms from January 2018 to May 2021. Of these, burglar alarms, 97% of them were concluded to be false. This equates to 15,132 false alarms. While those figures might seem very high at first glance, the reality is that many other jurisdictions also report similar issues. One example can be seen in Panama City, FL.

In addition to mandating the use of ECV, the city of Asheville has also introduced new fines and fees in relation to false alarms and the general use of alarm systems. Anyone who wants to legally operate an alarm system in the city must obtain a permit, at a cost of $25. This permit must then be renewed annually, at a cost of $10 per renewal.

The revised ordinance also carried over existing fines and penalties in relation to the misuse of alarm systems. Any registered user is basically given a warning for their first two (2) false alarms in a calendar. But any third or subsequent false alarm is deemed a "public nuisance", and a user will be charged fines of $50 for their third, fourth, and fifth false alarms within that time period. From there, the sixth and seventh false alarms will result in $100 fines, the eighth and ninth false alarms will result in $250 fines, and any tenth and subsequent false alarms in a single calendar year will result in $500 fines.

In situations where a user is found to be more than thirty (30) days late in paying a fee or fine will be fine an additional $25 as a late fee. A user may formally appeal any fine, though this will result in an "appeal hearing fee" of $50. This fee will be reimbursed in the event that the appeal is upheld. All appeals must be submitted in writing and filed in the police chief's office within ten (10) days of a fine being issued.

Furthermore, the city may elect to formally suspend all emergency service responses to any user responsible for more than ten (10) false alarms in a calendar year, as well as any user who is more than ninety (90) days behind on any alarm-related fee or fine. In order to have services reinstated, a user must have their alarm system formally inspected, receive training on the use of alarm system, complete an online alarm awareness class and test, and pay all outstanding fees and fines, plus a reinstatement fee of $50.

Overall, it's easy to understand why the Asheville City Council would feel compelled to toughen their policies against alarm systems. When roughly 97% of alarm responses are deemed to be the result of unnecessary false alarms, it makes sense to feel a bit frustrated. Perhaps even more unfortunate is the fact that most jurisdictions throughout the United States likely experience similar problems and issues in regards to false alarms.

However, policies like these often make it more difficult for responsible, law-obeying citizens to obtain and operate security systems. The truth is that the vast majority of security system users do not cause excessive false alarms. It's usually a very small minority of system users who ruin it for everyone else. At Alarm Grid, we believe that the best solution is to train alarm system users so that they can operate their equipment responsibly and not add to a growing problem. We do our part by training our monitored customers in the responsible operation of security systems and false alarm prevention. We strongly encourage every security system user to review our guidelines for preventing false alarms. Following those tips will go a long way towards easing the burden placed on police forces and discouraging local jurisdictions from taking the matter into their own hands by enacting policies like this one in Asheville, NC.

Fortunately, the policies in Asheville seem to be reasonable for the most part. Giving users warnings for the first two (2) false alarms caused in a year is appreciated. Mistakes happen, and usually the embarrassment of causing even just one (1) false alarm is enough to make a user extra cautious moving forward. On the other end of the spectrum, the fines for causing excessive false alarms - particularly the $500 fine for every tenth and subsequent alarm beyond that - are some of the most extreme that we have ever seen. But that being said, we totally understand the reasoning here. A user who is causing that many false alarms in a one-year period is clearly not operating their system in a responsible manner. Punishing such end-users for this reckless and careless behavior can certainly be argued as fair. Also, while we're never fans of charging users fees for basic system registration, the $25 initial fee and $10 annual renewal fee isn't worth getting upset over.

What we would like to see as part of any alarm ordinance policy enacted by Asheville, NC, or any other jurisdiction for that matter, is some protection against monitoring companies like Alarm Grid. The formal staff report put out by Asheville outlines the responsibilities and duties expected of alarm companies, and it doesn't mention fining them in any way. But on that same note it doesn't mention any specific protections for monitoring providers. We have seen some states enact specific laws that prevent local jurisdictions from levying fines and fees against monitoring companies. For example, Tennessee signed such a law in 2019, Iowa started enforcing one last year, and Georgia's new policy from earlier this year put an end to a controversial situation in Sandy Springs, GA, where alarm companies were being fined by the city.

Do you have any thoughts on the revised alarm policy in Asheville, NC? Does your city have any similar provisions put in place. Would such provisions discourage you from getting your home or business monitored. Share your thoughts in a comment down below. We would love to hear what you have to say. And stay tuned to the Alarm Grid Blog for more security news and updates coming soon!

Tags: ,

Comments


Posted By

Alarm Grid would like to make you aware of a possible issue when using a ProSeries Panel (PROA7PLUS, PROA7PLUSC, PROA7, or PROA7C) with an Ubiquiti Wireless Access Point (AP). Connection problems may occur if Auto Optimize is turned ON for the AP. To avoid issues, turn Auto Optimize OFF.

You may recall a similar issue that affected the predecessor panel from Honeywell Home and Resideo, the Honeywell Lyric. In that case, users had to disable the Auto Optimize Network feature for an Ubiquiti UniFi AP in order for a Lyric System to connect successfully. If a Lyric Panel was connected with an Ubiquiti UniFi AP, and then the Auto Optimize feature was enabled on the AP, then the Lyric would lose its WIFI connection with the Ubiquiti device. This would occur even if the Auto Optimize feature was turned ON due to an automatic update for the Ubiquiti AP. It was then later reported that Ubiquiti corrected the issue so that security systems were not booted from the network when the Auto Optimize feature was enabled.

In this case, it is the Honeywell Home and Resideo ProSeries Security Panels that are having issues with the Auto Optimize feature for Ubiquiti AP devices. Reports indicate that if the Auto Optimize feature for the Ubiquiti AP is turned ON, then the system may have trouble maintaining a stable WIFI connection. When the feature is enabled, a ProSeries Alarm Panel may be unable to connect with the network, or it may fail to reconnect with the network if the connection becomes lost. With that in mind, it is advised that you keep the Auto Optimize feature turned OFF for an Ubiquiti Access Point if a ProSeries System is connected. Please refer to the manual for your Ubiquiti AP for more information on how to do this. Alarm Grid has also released a very general FAQ outlining potential WIFI issues for ProSeries Panels, which you can view here.

Don't forget that a ProSeries Panel needs a WIFI card in order to connect with a WIFI network. This can be a Honeywell Home PROWIFI, which is a standalone WIFI module, or a Honeywell Home PROWIFIZW, which doubles as both a WIFI card and a Z-Wave Plus home automation controller. The Honeywell Home PROA7PLUS and Resideo PROA7PLUSC both contain a PROWIFIZW from the factory, so no add-on module will be needed. On the other hand, the Honeywell Home PROA7 and Resideo PROA7C do not have a WIFI module pre-installed from the factory, so you will need to add one of the aforementioned units in order to get one of those systems connected to WIFI.

Hopefully this post has helped at least one user in correcting issues between their ProSeries System and their Ubiquiti Access Point. If you have any experience using a Honeywell Home or Resideo ProSeries Security System with an Ubiquiti Access Point, or if you just want to discuss ProSeries Alarm Panels in general, then please share your thoughts in a comment down below. We are always interested to hear what you have to say. And remember to stay tuned to the Alarm Grid Blog for more helpful news and updates 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

The Security Industry Association (SIA) recently announced the winners of the 2021 SIA New Product Showcase Awards. We are pleased to say that the 2GIG Edge was named as an Honorable Mention in the field of Smart Home Solutions. Congratulations 2GIG and Nortek for your continued success!

Determined by a panel of experienced judges, the New Product Showcase Awards, also called the NPS Awards, have been presented since 1979. The purpose of these awards is to recognize innovative security products, services, and solutions that benefit the industry and end-users alike. This year, 35 judges determined the award winners in more than 25 product and service categories. 2GIG, along with their parent company of Nortek, was recognized as an Honorable Mention in the Smart Home Solutions Category for the new 2GIG Edge Panel.

It's no surprise that the 2GIG Edge would be recognized for its smart home capabilities. The alarm panel and smart home controller is a force to be reckoned with in terms of automation. It includes a built-in Z-Wave Plus V2 Controller, which is also known as a Z-Wave 700-Series Controller. This represents the latest and greatest Z-Wave technology, as the 700-Series Z-Wave devices can go at least ten (10) years between battery changes, and they support signal hops of up to (200) feet each for extended wireless range.

That's not to mention that all Z-Wave 700-Series devices support the powerful S2 Security Protocol for greater wireless protection. 2GIG has even released a 700-Series Z-Wave Smart Thermostat, the 2GIG STZ-1, that pairs perfectly with the 2GIG Edge Alarm System. To learn more about 700-Series Z-Wave in general, please check out this blog we put out on the subject when the technology was still brand-new. The blog was written before we fully understood the protocol, but it should still do a pretty decent job of explaining it if you are totally unfamiliar with the subject.

As you may know by now, the 2GIG Edge also connects with the Alarm.com platform when the system is monitored. This platform makes it possible to control connected smart devices remotely from anywhere in the world. Any smart device paired with a monitored 2GIG Edge Security System will appear on the Alarm.com platform for remote access. You can then use the Alarm.com Mobile App on your phone to control the connected devices. You can also create powerful Alarm.com Smart Scenes and automations to have the connected devices respond automatically to predetermined system events and/or operate on a set schedule. This is great for saving money on energy bills, while also making your life much more convenient. Alarm.com even allows for geo-fencing through their Geo-Services technology so that smart devices activate once you are within a predetermined radius of your home.

Alarm Grid offers congratulations to 2GIG and Nortek for the continued success of the 2GIG Edge. This system is truly exceeding expectations, and it is one that we think can be a staple in the security and automation industry for many years to come. If you have any thoughts on the 2GIG Edge, please leave them in a comment down below. We would love to hear what you have to say. And remember to stay tuned to the Alarm Grid Blog for more news and updates coming soon!

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

For anyone watching Samsung SmartThings it's impossible not to notice that the platform has experienced a substantial shift in identity. While the platform was once developed upon physical hardware, that is no longer the case, as SmartThings is now largely built around intangible software.

This change in focus can be seen in multiple facets of SmartThings. The legacy "Classic" SmartThings App has been left behind, and developers have instead put their resources into SmartThings Labs and the recently re-titled Matter initiative, which was previously known as Project CHIP. It's obvious that Samsung still sees value in the SmartThings platform, if only from a virtual aspect. This can be especially seen in Matter, as initial Matter-speaking devices are set to release later in 2021.

But while Samsung clearly has interest in the software side of SmartThings, the hardware side has been relatively quiet. The original 1st-gen SmartThings Hub stopped working nearly a year ago. Meanwhile, Samsung has been attempting to pass the hardware development side to others, as Aeotec has released the first third-party SmartThings Hub. Stock for SmartThings hardware is down, and it is becoming increasingly difficult to find basic equipment. What it all suggests is that Samsung wants its focus to be on their SmartThings ecosystem, not on the equipment itself.

To make this possible, Samsung is pushing the SmartThings platform to rely even more heavily on the wireless protocols that allow for connectivity and communication between the different equipment. These wireless protocols include WIFI, Z-Wave Plus, Zigbee, and even more obscure wireless networks like Thread, and their own pet-project, Matter. Simply put, Samsung wants to focus on building the smart wireless ecosystem making automations possible, and not necessarily on the sensors and smart hubs that users physically set up and hold in their hands. Apparently its in the intangible aspects of a smart home where Samsung feels they can bring the most value.

SmartThing users often say that the platform is one of the easiest and most proficient ways to design and maintain a smart home. It's obvious that Samsung still views SmartThings as a crucial component of their brand. However, while the SmartThings division was once largely an endeavor of tangible hardware, that appears to no longer be the case. The future of SmartThings as developed by first-party Samsung appears to be that of a virtual focus, in which software development reins supreme. Elsewhere, the actual legwork of building the physical hardware components can apparently be left to whomever will step up in their place.

What do you think about this change of focus for Samsung? Do you think this is a good move for the company to primarily focus on the intangible software components of SmartThings? Do you believe that other third-party companies can properly step-up and handle the hardware development and manufacturing steps of the process in their place? Also are you a fan of SmartThings in general, or do you prefer other smart home automation platforms? Let us know your thoughts in a comment down below. And stay tuned to the Alarm Grid Blog for more security and automation discussions 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