Correct Z-Wave Lock API Command

Developer Programs Support
, ,
25

I’m bumping and tracking this, as this is a pretty significant issue with the stock Z-Wave Lock Edge driver. I’m hopeful @nayelyz will be able to get resolution.

My experience is the same as yours in that I’ve found that the setCode command, as described in the CLI:

setCode(codeSlot, codePIN, codeName)

completely ignores the codeName. The only way I’ve found to set the codeName is to use the nameSlot command instead:

nameSlot(codeSlot, codeName)

That provides a rather clumsy workaround as it requires two commands to set both a code and give it a proper name, but even with that workaround, there is another problem, because the data returned upon a keypad event is wrong. Instead of using the codeName established by the nameSlot command, the response creates it own, as shown in this partial snipped where “Weekend Guest” in incorrectly presented as “Code 1.”

 "data": {
    "codeId": "1",
    "codeName": "Code 1",
    "method": "keypad"
  }

This creates an issue when creating Rules intended to provide accurate notifications of keypad events, or to be able to act on those events based onthe user name (i.e., when the name contains “guest.”)

3 Likes