Kwikset Lock

[joshua_lyon (Josh, SharpTools.io Dashboard)]

That’s really more of a question for the specific device handler and how it works. It looks like you have the second and third parameter backwards in your example though. Reading their spec, the first parameter is the code ID, the second is the code, and the third is the code name.

Also make sure the default data types are right. The first is a number, and the second and third are strings.

If that doesn’t help, I would start by checking the attributes mentioned in the other thread… as well as watching the SmartThings IDE live logs when you send the command.

Reading through the other thread, it sounds like there are various attributes that would be helpful to check including lockCodes, codeChanged, and codeLength.

@duncan

setCode(int id, String code, String name) – Programs code code into code slot id – if the code is successfully set on the lock, it will update the lockCodes attribute value to indicate that code id is named name . The code parameter is generally a string of numerical characters, such as “0485” or “7777”. A codeChanged event will also be sent with the result of the operation, which is useful if you are editing an existing code or if the setCode fails.