Excluding A Yale Z-Wave Lock

5 years ago
109

In this video, Joe demonstrates the process for excluding a Yale Z-Wave Lock from a Z-Wave network. There are a few good reasons why a user might want to exclude a Yale Z-Wave Lock. These reasons include wanting to pair it with a new Z-Wave controller, troubleshooting the device and initial pairing.

A Yale Z-Wave Lock will pair with a Z-Wave network. This way, the user can control the lock from a hub or remotely from an app. They can also include the lock in with smart scenes for automatic operation based on a schedule or with certain predetermined system events. For example, a Z-Wave lock can be controlled through popular interactive service platform like Total Connect 2.0 or Alarm.com. You can access it through an associated app on your phone to unlock the device if a friend needs to get in while you are away. You can then lock the device remotely after they leave.

There are several situations in which you would want to clear a Yale Z-Wave Lock from a Z-Wave network. The first is if you are initially pairing the lock with a Z-Wave network. Even locks that are brand-new from the factory may have been previously paired with a Z-Wave network for testing purposes. By clearing the lock from the network first, you can ensure that it will pair successfully.

You will also need to clear the lock if you want to take the device from one Z-Wave network and pair it with a new one. A Z-Wave device can only be paired with one Z-Wave network at any given time. If you need to bring the lock to a new Z-Wave hub, then you will need to clear it first. If you try to pair a Z-Wave device with a new Z-Wave network while it is still paired with an old one, then it will not work properly.

Another reason to clear a Yale Z-Wave Lock is if the device is not working properly. Clearing the lock from the networking and pairing it again may fix certain problems and issues. This is a popular troubleshooting step that can be performed if your lock is ever not operating as it should.

http://alrm.gd/get-monitored

Loading comments...