# Multiple Zwave controllers for better lock code management?

**URL:** <https://community.smartthings.com/t/multiple-zwave-controllers-for-better-lock-code-management/18049>\
**Category:** Connected Things\
**Created:** [June 18, 2015, 2:29pm UTC](https://community.smartthings.com/t/multiple-zwave-controllers-for-better-lock-code-management/18049 "2015-06-18T14:29:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JDRoberts](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/jdroberts/32/56577_2.png) [@JDRoberts](https://community.smartthings.com/u/JDRoberts)\
**Post date:** [June 18, 2015, 2:40pm UTC](https://community.smartthings.com/t/multiple-zwave-controllers-for-better-lock-code-management/18049/2 "2015-06-18T14:40:30Z")

</div>

A zwave or zigbee device can only belong to one primary controller.

It’s technically possible to set up SmartThings as a secondary controller to Vera (much like the Aeon Minimote becomes a secondary to SmartThings), but the results are rarely quite what people want, so it isn’t done often.

For example, many devices rely on Association to report status, but can only be associated in one group. So even if Vera and ST agree between themselves that one is primary and one secondary, only one would get the status updates from say, an eco-link sensor.

Also, locks are a separate category because of the security requirements and this also tends to mean they will only report to the primary. You can sometimes get around that with virtual switches as status indicators but it gets really complicated.

> **[Z-Wave General Info](https://support.smartthings.com/hc/en-us/articles/204392790-Z-Wave-General-Info)**
>
> General Information
> The SmartThings Hub is a Z-Wave-certified central static controller. It can be included in any Z-Wave network and operate with Z-Wave certified devices from other manufacturers....

Before we get too far down the path of what you might do with multiple controllers, there are community developed smart apps and device handlers that provide a lot of custom code management for locks. They are certainly worth looking at.  
But they still don’t give you all of the functionality the lock is designed for, so it comes down to exactly what you need.

Lock Code Manager is very popular, for example:

> [@\[Depricated\] Lock Code Manager](http://community.smartthings.com/t/lock-code-manager/12280):
>
> There’s a new app! Please go to [this thread](https://community.smartthings.com/t/release-lock-manager/63022/) for the new Lock Manager App, which is in active development. ##Legacy App: This app is no longer being maintained. Support and bug fixes are no longer being provided. Welcome to Lock Manager! Now with custom device type! Use the attached device type zwave-lock.groovy for added functionality. Minimal changes to SmartThings code. More reliable code set/delete. Codes will be reconciled on each poll() event. App will function without custom device type, but not as well. Features: Assign Codes to Multiple Users. Manage Multiple Locks. See what codes are active. See how many times a code is used (reset usage manually) Be notified when a user uses their code. Delete codes after they are used\*. Optionally Schedule Users so that they only have ac…

---

_[View the full topic](https://community.smartthings.com/t/multiple-zwave-controllers-for-better-lock-code-management/18049)._
