wow, that’s very nice of you. I am excited to see if you are able to extract that info. would definitely be nice to react to the specific user code or entry method. in the meantime, how can I check if I am using an edge driver for my zwave lock?
You can open the SmartThings mobile app and open the device you are interested in. Give the screen a moment to load, then tap the ... in the top right and if you see a ‘Driver’ option, it’s on an Edge driver.
From what I understand, as of today, you’ll only be on an Edge driver if you’ve explicitly reonboarded the device recently (removed it and re-paired it to SmartThings). The exception to that is if you are part of the Edge Driver Betas in which case they have automatically migrated some drivers already. I believe the plan is to start the automatic migration for regular SmartThings users sometime late August through end of September.
Hi! Groovy refugee working on transitioning my handful of live WebCore pistons. Similar to @RichB, I want to enable a lock code for my cleaners during scheduled visits. I originally had mine tied to a GCalSearch presence sensor which I’m working on mimicking in IFTTT. On the Rules side, I need to add the code when that presence is active.
My input arguments appear to show in the opposite order from your screenshot, with the numeric value coming last. I’ll try it out with the reverse sequence when I get home and can confirm the code enters properly but wanted to raise it here given the discrepancy withwhat you just posted.
Are you moved over to the next-generation integration? Keep in mind, the next-gen connection is only enabled for new users by default, so if you had a legacy connection to SharpTools at some point in the past, you may still be using that.
If you’re just getting started with SharpTools and don’t have many rules/dashboards built-out yet, you can deauthorize your existing legacy connection which would then make the next-gen connection available to you (proceed through auth, select the location, and tap deny).
Alternatively, we can get you added to the beta so you connect connect the next-gen connection side-by-side your existing legacy connection.
I would also add that the Groovy platform has an oddity where when it is asked for the list of parameters, they don’t always come across in the right order. You can fix it by tapping the ‘Advanced’ toggle in the top right of the Device Action in your rule and then change the parameter types as you see fit.
Got it in one. I didn’t realize the different connection would lead to a different presentation of the options. I set up an account ages ago and am just now making an effort to use it, so re-linking the couple of rules I started setting up was no big deal.
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.
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