Lock Code Manager: Compatible Locks...?

[salieri]

Hello,

For the built-in lock code manager application within Hubitat, which locks are compatible with it? I tried looking around for this answer (as well as the documentation) and was unsuccessful.

Is it for just locks that have a built-in keypad that are Z-Wave or Zigbee compatible? And locks with separate keypads (such as Dana or August) would not be compatible?

Thanks for the insight....

[danabw]

You'll find them listed here:

List of Compatible Devices

[csteele]

I believe that LCM (Lock Code Manager) is an Application "wrapper" around Locks in general. In other words, any Lock Driver that supports the features of LCM, will work because LCM doesn't talk to the Locks. LCM talks to the Driver, which talks to the locks.

[aaiyar]

@salieri

Is it for just locks that have a built-in keypad that are Z-Wave or Zigbee compatible? And locks with separate keypads (such as Dana or August) would not be compatible?

See what @csteele wrote.

Any lock whose driver supports the following commands will work with LCM:
deleteCode()
getCodes()
setCode()

[danabw]

@aaiyar

Any lock whose driver supports the following commands will work with LCM:

And wouldn't the list of locks that meet those requirements be represented by the locks in the Compatibility list? (Aside from some that may be supported by a community integration.) Maybe I'm missing something in this conversation? (May have happened once before in my entire life.)

[aaiyar]

@danabw

And wouldn't the list of locks that meet those requirements be represented by the locks in the Compatibility list?

No, there are locks on that list that are not compatible with LCM. For example the built-in driver "Virtual Lock (no codes)". And possibly others - like the keypad less locks. They all support lock() and unlock(), but no code operations, which LCM needs.

[danabw]

Did not know that (obviously)...assumed that "compatible" would include working w/LCM as well. Wasn't aware that LCM would barf if it doesn't see a keypad capability. Thanks.

[salieri]

Thanks. How would one know if the driver supports these commands before buying the lock?

[csteele]

I use my Get Attributes App to acquire the info...

That info is for the built-in Virtual Lock driver as an example.

[aaiyar]

@salieri

the driver supports these commands before buying the lock?

If the lock has a physical keypad (like most common z-wave/zigbee locks), and is listed as a compatible device, it will work with LCM.

[danabw]

@aaiyar

If the lock has a physical keypad (like most common z-wave/zigbee locks), and is listed as a compatible device, it will work with LCM.

And if either of those requirements aren't met, you can search the forum here for the lock in question and see if anyone has developed & posted a community driver/integration to support the lock you want.

Safest bet is to buy something officially supported, as community drivers and integrations are at some risk over time to "lose" their developer if he/she moves on to a different HA platform, or gets a new device and stops supporting the original one, etc.

[mike.maxwell]

@salieri

And locks with separate keypads (such as Dana or August) would not be compatible

correct, these devices do not report any lock code information via their zigbee and z-wave interfaces.

[salieri]

Thanks to everyone for taking the time out to help me better understand with these explanations. Really helped clear things up for me.