Kwikset Lock

[joshua_lyon (Josh, SharpTools.io Dashboard)]

Thanks for the tag @jkp

SharpTools exposes whatever commands are made available by the device. In most cases, these commands follow the capability definitions created by SmartThings and you can find details in the official capabilities documentation or by searching this community.

For example, you can find details on the lockCodes capability in this thread:

Capability lockCodes (update)

In preparation for the long-delayed official lock code management solution, we’re making some changes to how the “Lock Codes” capability works. The main difference is that we’re removing the actual unlock codes from the events and storage for security reasons. Also, the setCode command will add an optional name argument that will let you give meaningful names to your codes so you know which code to delete or change when you need to. We decided to store this at the device level so you can eventually manage codes directly in the device preferences. The proposed spec is below – let us know if you see anything missing or any issues that may hurt its usability. Attributes lockCodes – JSON object mapping code IDs to code names. If a code hasn’t been set it won’t appear in the mapping. Example…

And if it’s a community developed device handler, your best resource is usually in the original thread that the DTH was posted in or with the developer of that DTH.