Managing Lock Codes without Groovy

[Scott_Levin]

Just following up. Any luck getting access to event.data?

[josh]

The data property is there on the Z-Wave Lock Edge Driver in the next gen platform and has the codeId property in it (along with codeName and method = keypad). I won’t be able to get to it right away, but since the data is there the good news is it’s possible.

[just_jake]

@josh

I took a look through the Z-wave Lock Edge Driver and it still has some references to event.data, so I just put in an order for a Kwikset 910 and will try it out.

Is that based event data from a subscription?

[josh]

@Scott_Levin

Any luck getting access to event.data?

Update: ‘Extra’ event data is now available in production! Extra event 'data' properties

We’ve exposed the data attribute from events in beta - I sent you a PM with access. There’s a new ‘Extra Data’ option in Context Variables for Event → Device which will prompt you for the extra data ‘property’ that you are trying to access.

Like other context variables, you can use this in conditions as well as actions like notifications. In the case of door locks, it looks like common properties include:

• codeId - which code ‘slot’ was used to unlock the door
• codeName - the name of the code (if you named it while creating it in SmartThings)
• method - indicates if it was unlocked with a keypad or manual

@just_jake

Is that based event data from a subscription?

Yes, it’s based on event data from subscriptions

[plb44]

Could I be add to the beta

Would like to test this feature!

[Nathan_Davis]

I would like that feature as well!

[just_jake]

@josh

Yes, most lock devices will offer a setCode() command. If I remember correctly, the parameters are:

1. Code Slot
2. Code PIN
3. Code Name (Description)

@josh is this the argument structure your using to sent the codes using the API?

"arguments": [Slot,"Pin","Name"]

[josh]

The commands are dynamically built with the Rule Engine. This allows for introspection of custom capabilities so we can expose the commands from those devices.

It also allows for customization of the order and type of arguments in ‘advanced’ mode when a command is ‘overloaded’ with different parameter types.

[Richard_Coomber]

I just want to let you all know how useful these posts have been. My LUM died today and I lost all my lock codes trying to fix it.

The Samsung Smart Lock Guest Access isnt available in New Zealand.

I came across this chain, installed sharptools and was able to recode my locks in about 3 hours.

Thanks so much for your work and documenting this.

Richard

[Martin_Lavoie]

I would definitely like this feature as well. Can you add me to the beta please.

Thanks.

[josh]

Hi Martin-
The ‘extra’ event data is available directly in production:

Extra event 'data' properties

Some events, like unlocking a door with a code on the keypad, store additional metadata about the event in a data attribute when the event is generated. The data attribute from events is now exposed in the ‘Extra Data’ context variable in rules! [image] When using Context Variables for Event → Device, you’ll now see an ‘Extra Data’ option which will prompt you for the extra data ‘property’ that you are trying to access. If you’re not sure what property to use, see the ‘How to find data proper…