Training Posts

Posted By

Power over Ethernet, also known as PoE allows power to be sent to a device using the same ethernet wire and RJ45 connector that is used for the network connection. Originally designed with VoIP phones in mind, PoE has quickly become a desirable option for IP cameras and other networked equipment.

Before we talk about PoE, we should discuss network cabling. Category 5 (Cat5), Category 5e (Cat5e), and Category 6 (Cat6) cables all consist of four (4) twisted pairs of wire, or a total of eight (8) conductors. The differences between these various categories of cable have to do with their ability to transfer data, over what distance, and at what speed. Generally, Cat6 is faster than Cat5 or Cat5e, and is less prone to crosstalk or noise issues.

The main point we want to make about network cabling, though, is this: With eight (8) conductors, any device that connects to a network using one of these cables, without using PoE, is wasting a number of wires. In fact, there are now cheaper cables out there that only have four (4) conductors, rather than the full eight (8). So, that brings us to two points. It makes sense that PoE has come into existence, and if you're preparing to use PoE devices, be sure you run cabling that will handle both data and power.

In PoE, there are a number of abbreviations commonly used:

Abbreviation Meaning Description
PD Powered Device Any networked device receiving PoE
PSE Power Sourcing Equipment Devices that send both power and data over Ethernet cable to a PD. Referred to as either "Midspan" or "Endspan".
Endspan or Endpoint A typical example of this is a PoE network switch. It provides power to Powered Devices (PD).
Midspan If a switch is used that doesn't provide PoE power, then a power source will need to be added between the switch and the PD. A common example is a PoE Injector. This is considered a Midspan PSE device.

The benefits of PoE are numerous, as you can imagine. Rather than having every camera in an installation require the use of an outlet, a PoE switch using a single outlet can provide both power and Ethernet to a multitude of cameras with a single Cat5 or Cat6 wire going to each. In many cases, Ethernet cabling may already be installed, particularly in commercial installations, thereby lowering installation costs for PoE equipment. Another benefit is that when each powered device is receiving its power from a PoE capable switch, it is often possible to restart a PoE-powered device remotely, without having to go to the device itself.

The IEEE 802.3 standard governs PoE Switches and PoE Injectors. There is no special cabling required with the exception that the standard called Ultra-PoE uses all eight (8) pins of the RJ45 connector, so this would be one instance where a cheaper 4-pin cable would not work.

The table below shows the IEEE 802.3 standards and their requirements:

PoE Standard Minimum Cable Required Pins Required Supported Modes
IEEE 802.3af Cat5 4-pins or 2 Pairs Mode A, Mode B
IEEE 802.3at Cat5 4-pins or 2 Pairs Mode A, Mode B
IEEE 802.3bt Type 3 Cat5 8-pins or 4 Pairs 4-pair
IEEE 802.3bt Type 4 Cat5 8-pins or 4 Pairs 4-pair

There is a type of cable called CCA or Copper Clad Aluminum. Although this cable is fine for networking, it is not suitable for use with PoE. This is due to the aluminum core. Aluminum doesn't conduct as well as copper and has a higher DC resistance. This causes it to lose more power over distance and to get hotter. When working with PoE, stick with 100% copper cabling.

One of the things you may find difficult about using PoE is figuring out if you have enough power from the PSE for a PoE device. These specs are usually listed in Watts, rather than in the available current, which can further complicate things. Here, knowing which standard each device uses is most helpful.

Below, see the various PoE standards, and the power both supplied and required for each:

PoE Standard Voltage @ PD Voltage @ PSE Minimum Power for PD Minimum Output @ PSE Maximum Cable Length
IEEE 802.3af 37-57 V 44-57 V 12.95 W or 350 mA 15.40 W 100 m
IEEE 802.3at 42.5-57 V 50-57 V 25.5 W 30 W 100 m
IEEE 802.3bt Type 3 42.5-57 V 50-57 V 51 W 60 W 100 m
IEEE 802.3bt Type 4 41.1-57 V 52-57 V 71 W 100 W 100 m

The variations in voltage and current at the PD (Powered Device) in the table above have to do with the length of the cable run. The longer the cable, the more power is lost. You may have noticed in the above table that the maximum cable length for each PoE Standard is 100 m (328'). This is actually a limitation of both Cat5 and Cat6 cables, as the maximum length of a single run for either type of cable is 100m. The minimum voltage and available power listed above assume a cable run of the maximum length.

So then, what if you need to run a cable further than 100m? For PoE devices, you would add a PoE extender. Specifications may vary, but usually, each PoE extender can add another 100 m of cable length between the PSE and the PD. Usually, each PoE extender is only good for a single PD. Not all PoE extenders are the same, though, and some may not support daisy-chaining, while others do. Check out the specifications of any PoE extender you choose to use if you find yourself in a position to need longer cable runs.


Tags: , , , , , , , ,

Comments


Posted By

One of the good things about an alarm system is the fact that there are redundancies built-in. This prevents a single point of failure. To be certain that everything is working as it should, proper testing is required. Life-safety devices should be functionally tested on a regular basis.

There are numerous aspects to an alarm, that's why it's called a system. The senors are its eyes and ears, the keypad and sirens are its mouth, the alarm panel is its brain, and the communicator is how it calls for help. Whether that's by an old-fashioned POTS line, or cellular, or IP. It is recommended that all the basic aspects of the system be tested once a month. That means putting the system on test with the monitoring station, if necessary, then setting off an alarm and making sure that it both shows up locally at the keypad, causes the siren to sound if applicable, and communicates successfully to the monitoring station.

When an alarm system is first installed, it should be tested in such a way that every single facet of the system is verified to be working properly. That means every zone should be tested, and verified to have performed as programmed, including sending a report to the monitoring station, if central station monitoring is in use. It is important to do this properly because it sets a starting point. When you know that everything was working on a particular date, then later tests may be spot tests, without having to test every single zone. If you keep good records, then if a problem does arise, you'll be able to look back and know when was the last time this particular portion of the system was known to be working, and begin troubleshooting from there.

Smoke detectors and carbon monoxide (CO) detectors are considered life-safety devices. They can be wired to the alarm system, but they are often battery powered and some may be wireless, but still connected to the alarm system. There may be others that are battery powered, stand-alone devices that only sound locally, and are not tied to the alarm system. When moving into a home where an alarm system is already installed, it's very important to determine what life-safety sensors are present, whether they are stand-alone or tied to the system, and if possible, get any testing records, and any information you can on battery maintenance. If there are no life-safety sensors, or if there are none that are tied into the system, make it a priority to change this as soon as you can. Always follow the recommended guidelines when laying out the life-safety portion of your system.

Smoke and CO detectors can be tested in two ways. Each device usually has a push-button on the device itself. Depending on the device, pressing this button will cause the detector to sound locally and test its own battery. With newer devices, testing one smoke or CO detector in this way will cause all of the associated life-safety devices on the system to sound. This is called one-go-all-go by some manufacturers. There is usually an LED that provides feedback with this test, with some detectors actually speaking their status. If this happens to be a life-safety sensor that is tied into an alarm system, then pressing the test button should also cause an alarm condition to show up on the system keypad, and if the system is being monitored by a central station, a signal will be sent. If a low battery condition exists, it should be displayed via LEDs, or spoken, on the detector itself, and will show up on the alarm keypad if the detector is tied to the alarm system.

The above test is fine for the monthly system test, but at least twice per year, life-safety devices should undergo a functional test. A functional test is where you actually cause a smoke or a CO alarm. With smoke detectors, you can sometimes do this by lighting a 3-wick candle then blowing it out right under the smoke detector. Functional testing of a CO detector is more difficult, but still possible. We offer both canned CO for testing, and canned smoke. When testing, it may be helpful to hold a bowl upside-down over the detector to be tested. Make the bowl only as large as is necessary to cover the detector completely. Spray the canned smoke or canned CO into the area covered by the bowl. This should result in an alarm with a minimum of the canned product being wasted. It will also prevent you from possibly breathing it in. It is recommended to perform the functional test during the Spring and Fall, at the same time that the clocks are changed for Daylight Saving's Time. This Fall, that's going to happen on November 7, 2021.

Once you've caused an alarm to occur either with actual smoke, or with canned smoke or canned carbon monoxide, you can perform a disarm at the panel keypad to silence the system. It is possible that the system will begin sounding again if there is still smoke in the sensing chamber of the smoke detector, or canned CO in the sensing chamber of the CO detector. To stop the alarm, you need to clear the chamber. That means removing the bowl or other covering you used during the functional test, and blowing out the chamber. Be careful not to breathe in the canned test product. It is noxious! It may be helpful to have a fan handy, or possibly some canned air but be careful not to damage the sensing chamber. If using canned air, hold it at a distance of eight (8) inches or more from the detector.

Testing CO detectors is particularly important at this time of year. Carbon Monoxide buildup is caused by the inefficient burning of certain types of fuel. Natural gas, oil, kerosene, gasoline, wood, and charcoal are all fuel sources that can cause CO poisoning when not burned efficiently. As we head into the colder months, the use of all of these types of fuel for heating and recreation will be on the rise. If you're interested in how carbon monoxide detectors work, you can learn more here.

Above is a general guideline for how to functionally test smoke detectors and CO detectors. Follow the instructions found with the product literature for proper testing and be sure, if your system is monitored by a central station, that you call and put the system on test with them prior to causing an alarm. There are a number of ways that you can accomplish this. You can call the monitoring station, provide verification of your identity, then ask the operator to put your system on test. If you are an Alarm Grid customer, you can use the myalarms.com feature to put your system on test and take it off. If you are an Alarm.com subscriber, you may be able to put your system on test, or take it off, through the Alarm.com app. Alarm Grid has many guides, both written and video, to various specific smoke detectors and CO detectors. Check out our Youtube channel, or search the site for information on your devices. If we don't have information on a device you need to test, if it's one we sell leave us a comment below and we'll be happy to create content for that specific device.

Tags: , , , , ,

Comments


Posted By

We missed an opportunity to recap videos last week, but that just means we have more videos to cover this week. Six (6) today, with more to follow. Michael and Jorge share their knowledge of the 2GIG Edge and the Honeywell Home PROA7PLUS. Summer's almost over but wade in, the water's fine.

Honeywell Home PROA7PLUS: Resolve WIFI Connection Issues

In this video, Michael discusses the various reasons why the Honeywell Home PROA7PLUS might not connect to WIFI. Reasons can include range, environmental issues, and even bad equipment. In addition, there is a specific setting to watch out for on Ubiquiti Access Points. Having this setting enabled can prevent your Honeywell Home PROA7PLUS from connecting to WIFI.


2GIG Edge: What To Expect During AC Loss

During an AC Loss condition, the 2GIG Edge will go into power conservation mode. After a few seconds, the touchscreen will go dark and only illuminate when something occurs that needs to be displayed, or when a user touches the touchscreen. Jorge tells and shows users what to expect as normal behavior when an AC Loss condition occurs.


2GIG Edge: Powering Down Properly

Believe it or not, there is a right way to properly power down an alarm system. In this video Jorge will show you how to properly power down a 2GIG Edge alarm panel. Begin by removing the set screws, pulling the panel off its base then unplugging the battery. Next, unplug the transformer, either at the barrel connector on the panel side, or by unplugging the transformer from the wall. If you can't find the transformer, you can power down by turning power off at the breaker.


Qolsys IQ Remote: Behavior On a Partitioned System

In this video Michael shows you how the Qolsys IQ Remote behaves when it is used on a partitioned system. The IQ Remote will only display the status of the partition to which it is assigned. It will only allow the user to control the assigned partition as well, and only a user with a User Code that has been given access to the assigned partition will be able to interact with the system from the IQ Remote.


2GIG GC3e: Installing the XCVR3 GC3

Michael shows users how to install the 2GIG XCVR3-GC3 to the 2GIG GC3e panel. Unlike with the 2GIG GC2 panel, the installation of the 2GIG XCVR3-GC3 does not require that anything be removed from the GC3e panel first. This transceiver module simply adds 900 MHz 2-way communication capability between the GC3e and the 2GIG TS1 as well as the 2GIG Image Sensors.


Honeywell Home PROA7PLUS: Installing PROTAKEOVER

Michael shows users how to set the dial for legacy RF devices, and then properly install the Honeywell Home PROTAKEOVER module into a PROA7PLUS system. This module allows the PROA7PLUS to support one (1) of five (5) legacy RF frequencies. This allows the panel to support previously existing sensors from Honeywell or 2GIG 345 MHz sensors, existing Qolsys and/or Interlogix/GE 319.5 MHz sensors, DSC 433 MHz sensors, or Bosch 433 MHz sensors. This module allows a user to replace an older panel with the newer PROA7PLUS without having to replace all the existing wireless sensors that are still working.



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

Comments


Posted By

It's time for our weekly video recap, this time covering releases from Monday and Tuesday of last week. We only have four (4) new videos for now, but we promise there are many more on the way. This week's releases all feature myself, and they cover the Honeywell Home PROA7PLUS. Let's begin!

Honeywell Home PROA7PLUS: Add a Z-Wave Device

I show you how to add a Z-Wave device to a Honeywell Home PROA7PLUS. The PROA7PLUS has a built-in module called the PROWIFIZW that provides the system with both WIFI and Z-Wave control. Paired Z-Wave devices can be controlled from the panel, and remotely from Total Connect 2.0 if the system is monitored with a plan that includes automation services. You can also use TC2 to create smart scenes for your Z-Wave devices so that they activate automatically based on a schedule or with system events.

Honeywell Home PROA7PLUS: Remove a Z-Wave Device

I show you how to remove a Z-Wave device from a Honeywell Home PROA7PLUS. Removing a device clears out its Z-Wave network data so that it can be paired with a new network. That is why you typically remove, or clear, a Z-Wave device before you attempt the pairing process when adding it to the network. This is done even if a Z-Wave device is brand-new, as many Z-Wave devices have residual network data leftover from factory testing.


Honeywell Home PROA7PLUS: Adding a Z-Wave Lock

I show you how to pair a Z-Wave door lock with a Honeywell Home PROA7PLUS. Like all other Z-Wave devices, a Z-Wave lock is paired with the PROA7PLUS by putting the system into its Z-Wave pairing mode and then activating the inclusion/exclusion function on the lock. For best results, it is advised that you clear the lock from the network before attempting to pair it. Most Z-Wave locks have a button that is used for inclusion/exclusion, or they require you to enter in a specific pairing command code using a push-button or touchscreen keypad.

Honeywell Home PROA7PLUS: Resolve WIFI Connection Issues

I explain some of the reasons why a Honeywell Home PROA7PLUS may be experiencing WIFI connection issues. One reason is that the password for the WIFI network may have been entered incorrectly. Another reason is that you are using a Ubiquiti Access Point (AP) with the PROA7PLUS, and you have the Auto-Optimize feature turned ON for the Ubiquiti device. Lastly, there could be something wrong with the PROWIFIZW module inside the PROA7PLUS, and it may need to be replaced.

Tags: , , , , , , , , ,

Comments


Posted By

We have a quick and easy tip for those using Z-Wave locks with Honeywell and Resideo ProSeries Panels like the Honeywell Home PROA7PLUS. You can have your panel user code pushed down to your Z-Wave lock, and you can also have your system automatically disarm when you enter that code into the lock.

Setting this feature up will offer some great convenience in your life. You can imagine walking up to your home, entering your panel code into your Z-Wave lock, the door unlocking, and then your system disarming, without you needing to interact with the panel at all, and then going about your day. We'll show you how to make it happen.

You can set this feature up for any panel code that you have programmed on your ProSeries System. Begin from the main screen, and choose the three (3) horizontal bars button at the bottom, followed by Settings, then User Management. Enter your Master Code (default 1234, but usually changed) or your Installer Code (default 4112) to get in. Then select the user with the code you want to use at the lock. Scroll down to Z-Wave Lock Control, and you can choose one of the following three (3) options:

  • None - Turns the feature off
  • Sync User Code to Lock - The code will be pushed to the lock so that you can unlock using the code.
  • Sync User Code to Lock & Disarm - The "money" option! The code will be pushed to the lock so that you can unlock using the code, AND the ProSeries System will disarm when you enter the code and unlock the lock!

Just choose the option that you want for that code (you know which one we recommend), and then press the black Save button in the upper-right corner. You will need to provide the system's Master Code to confirm the change, and then you're all set! We can't state enough how cool this feature is, so take advantage of it!


But before you go and make your life more convenient, why not make your life more EXCITING by leaving a comment on the Alarm Grid Blog? Let us know what you think of the feature. Have you tried it out before? Are you going to test it now. Do you need to buy a Z-Wave lock first? How about the Yale YRD226? We think that's a handsome lock, and it will look great in your residence. We promise! Anyway, stay tuned for more great content like this on the Alarm Grid Blog, coming soon!

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

Comments


Posted By

We have a quick tip today for users setting up Notifications on Total Connect 2.0, specifically regarding Notification Triggers for IP cameras. The HD cameras offer a much more diverse selection of Notification Triggers than legacy cameras, which have "Video Events" as their only option.

If you are not familiar with Total Connect 2.0 Text and Email Notifications, then the term "Notification Triggers" is used to identify the action(s) that cause text and/or email alerts to be sent to designated users. In the case of security cameras, you will likely want to be notified if your camera records a video clip. That way, you will know to check out the clip and make sure that everything is alright.

However, the selection of Notification Triggers is much wider if you are working with an HD camera versus and older legacy camera. For an HD camera, you can choose specific types of video captures for notifications, while leaving other types of video captures off the trigger list so that you aren't necessarily notified for every type of camera recording. For instance, you might want to be notified if your camera records a clip for an alarm event or due to detecting motion, but not if your camera begins recording due to sound-based detection.

Note the available selections in the list below. You can pick and choose which of these notifications you want to use with your Total Connect 2.0 HD camera, and which ones you do not. If you choose all eight (8), then it will essentially serve as the greyed out "Video Events" option, which is the only viable option when using legacy cameras.


But as you will notice for legacy cameras, only "Video Events" can be selected as the Notification Trigger. This is pretty much a cover-all option that includes all the individually selectable options that you would have for an HD camera. In other words, if you want to set up Notifications for any legacy cameras, then you will have to make it so that any and all camera activity will trigger a notification. For that reason, it is extra important that you adjust the sensitivity levels for your legacy cameras so that you aren't bombarded by alerts!


For reference, the only HD cameras used with Total Connect 2.0 are the Honeywell IPCAM-WIC1, the Honeywell IPCAM-WIC2, and the discontinued Honeywell IPCAM-WOC1. All other IP cameras used with TC2 are legacy devices. There is hope and speculation that Resideo (formerly Honeywell) will unveil some new HD cameras at upcoming ISC West 2021, but that is a story for another time.

This doesn't mean that if you mix and match legacy and HD cameras on a single TC2 account that you are restricted to "Video Events" for your Notification Triggers. You can create separate sets of notifications as needed so that you have fully customized alerts for your HD cameras, plus the "Video Events" Notifications set up for your legacy cameras.

Don't forget that Total Connect 2.0 allows you to have up to eight (8) HD cameras per account, plus a maximum of six (6) legacy cameras. You may want to refer to this helpful FAQ for more information on Total Connect 2.0 Clip Limits. We know that it can be a bit confusing regarding all the separate rules for HD vs legacy cameras on Total Connect 2.0, so definitely refer to that guide if you need a refresher!

Also, make sure to read our complete guide to setting up Total Connect 2.0 Notifications. That will show you exactly how to create TC2 Notifications the way you want so that you and those around you are properly alerted to events and activity on your security system, which includes any security cameras you have set up. Don't forget to leave a comment down below with your thoughts on Total Connect 2.0 Notifications and Alerts. We're very interested to hear what you have to say. And remember to stay tuned to the Alarm Grid Blog for more security content, news, and tips coming soon!

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

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

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

Welcome to a special Tuesday edition of an Alarm Grid Video Recap! We normally do these on Mondays, but we pushed this one back a day due to the time-sensitive nature of yesterday's post. Make sure to go and check that one out if you use the Nest Thermostat integration for Alarm.com.

As for today's video recap, it's mostly just business as usual. We have three (3) new videos today, all of which feature the 2GIG Edge. This innovative and feature-rich security system has certainly kept us busy and given us a lot to explore and share with you. We have even received some comments from users on YouTube asking us to cover specific 2GIG Edge features and functions. If you have anything that you would like to see from Alarm Grid, then make sure to leave a comment on this post down below. There's a great chance that you will see it in a future Alarm Grid video!

We know that you're on the EDGE of your seat waiting to see these new 2GIG EDGE videos, so let's get started! Here are the latest tutorial videos from Alarm Grid:

2GIG Edge: Clearing a Tamper Error

I show you how to clear a tamper error trouble condition from the 2GIG Edge. A tamper error occurs when the panel's internal tamper switch is not held down probably. This is usually the result of the panel being opened. When the issue occurs, a trouble notification will appear as a yellow circle with number inside it. Also, the panel will begin emitting a soft beeping sound. Once you properly close the panel so that the tamper switch is pressed down, the trouble notification will go away, and the beeping will cease.


2GIG Edge: Adding a Z Wave Device

I show you how to pair a Z-Wave device with a 2GIG Edge. Inside every 2GIG Edge is a Z-Wave Plus V2 700-Series Controller. This allows users to enroll a wide selection of Z-Wave peripherals, such as smart lights, door locks, programmable thermostats, and more. Z-Wave devices can be controlled locally at the panel, plus remotely from Alarm.com if the system is monitored with a plan that includes automation services. You can also create customized Alarm.com Smart Scenes to have your Z-Wave activate automatically.


2GIG Edge: Removing a Z Wave Device

I show you how to clear a device from the Z-Wave network using the 2GIG Edge. When you remove, or clear, a Z-Wave device, you are wiping out all its Z-Wave network data. This will allow the device to pair with a new Z-wave controller or hub. A user will typically remove a Z-Wave device if they no longer intend on using it. However, a user should also perform the clearing process before attempting to pair a device. This will ensure that no residual Z-Wave network data remains lingering inside the device.

Tags: , , , , , , , ,

Comments