SmartThingsCommunity / SmartThingsEdgeDrivers

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Z-Wave Lock Driver not Setting & Using codeName Correctly

TheMegamind opened this issue · comments

The setCode command, as described in the CLI:

setCode(codeSlot, codePIN, codeName)

ignores the codeName string and doesn't set it. The only way to set the codeName is to use the nameSlot command instead:

nameSlot(codeSlot, codeName)

That necessitates using two commands to set a code AND give it a friendly name. However, even though the name is established and can be view in the CLI, the data returned by the driver upon a keypad event is still wrong. Instead of using the codeName established by the nameSlot command, the response provides or creates one of its own as shown in this snipped where “Weekend Guest” in incorrectly presented as “Code 1.”

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

This creates issues when building Rules intended to provide accurate notifications of keypad events, or act on those keypad events based on the user name (for example, when the name contains “guest.”).

ETA: This issue has been discussed and confirmed by other users in the ST Community. My locks are Schlage Connect BE469.