Anyone know the IFTTT ingredient for the user code?

Wiki Projects & Stories
#1

Hi all,

I am new to IFTTT and started looking at it at the suggestion of smart things tech support because their app only shows 7 days of notifications and I needed more history to see when caretakers were coming in and out for my mom. Each person has their own code. I have an applet running where I write out to a google spreadsheet with the door is unlocked or locked. The lock happens automatically so I don’t need to tie a user code to that but does anyone know the “recipe” for the user code so I can write that to the spreadsheet? something like… {{UnlockedAt}} ||| {{DeviceName}}|||Unlocked|||{{UserCode}} perhaps?

Right now I just have {{UnlockedAt}} ||| {{DeviceName}}|||Unlocked and want to tack on the extra cell.

thanks in advance!

#2

@rboy might have a suggestion. He offers a paid third party lock management app and is also very active on these forums. He knows a great deal about lock management, although I don’t know if he’s used it with IFTTT.

1 Like
#3

IFTTT should allow you to access your locks (lock and unlock only AFAIK) through its channel however I’m not aware of any recipes that use this as we haven’t experimented with it (yet).
Here is one suggestion, if you’re using one of our lock user management apps or you can configure a rule in CoRE to seen an SMS when a door is locked or unlocked along with the user slot/name etc. now enter a google voice number here and you should be able to get notifications to your google account. Next would be to integrate the google voice with a database or spreadsheet.

#4

This reminded me that I was working on logging this and left it half way done.

I first created four momentary button tiles, one for each code.
Then a CoRE Piston I’ve created:

Pasted image320×950 13.1 KB

You could use variables of course to do internal stuff with ST, but I want this to log to my InfluxDB. So the VS’s are allowed into that.

The problem is, it doesn’t work.

CoRE doesn’t push the buttons, doesn’t even seem to see it unlock. I’ve tried Changes, Changes to, and Is, with no luck.

Live logging sees the code on the lock, ULM logs it as well. @ady624 I think I may have brought this up to once before, sound familiar?

#5

Is the piston triggered at all by an unlock?

#6

It sees the event but nothing happens:

7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:47 PM: trace ╔═══ Piston done in 488ms
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:46 PM: trace ║╔══ Task processing took 51ms
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:46 PM: trace ║║░░ Removing any existing ST safety nets
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:46 PM: trace ║║░░ Rescheduling time triggers
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:46 PM: trace ║╚══ Processing tasks (v0.3.167.20161206)
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:46 PM: trace ║╔══ Event processing took 163ms
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:46 PM: trace ║╚══ Processing event lock for device Front Door Lock with id 5a9543fb-61d7-40b3-8304-5082b7fc5346, value locked, generated on Sun Dec 18 19:18:43 UTC 2016, about 2619ms ago (v0.3.167.20161206)
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:46 PM: trace ╚═══ Received a primary block device event
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:45 PM: trace ╔═══ Piston done in 377ms
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:45 PM: trace ║╔══ Task processing took 44ms
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:45 PM: trace ║║░░ Removing any existing ST safety nets
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:45 PM: trace ║║░░ Rescheduling time triggers
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:45 PM: trace ║╚══ Processing tasks (v0.3.167.20161206)
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:45 PM: trace ║╔══ Event processing took 119ms
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:45 PM: trace ║╚══ Processing event lock for device Front Door Lock with id 5a9543fb-61d7-40b3-8304-5082b7fc5346, value unlocked, generated on Sun Dec 18 19:18:41 UTC 2016, about 3645ms ago (v0.3.167.20161206)
7452d652-0ad2-4ccb-b43f-c65d2ead15dd  12:18:45 PM: trace ╚═══ Received a primary block device event
#7

This is what the lock registers:

5a9543fb-61d7-40b3-8304-5082b7fc5346  12:18:51 PM: debug "zw device: 02, command: 9881, payload: 00 71 05 13 01 " parsed to ['name':'lock', 'value':'unlocked', 'descriptionText':Front Door Lock was unlocked with code 1, 'data':['usedCode':1], 'isStateChange':true, 'displayed':true, 'linkText':'Front Door Lock']
5a9543fb-61d7-40b3-8304-5082b7fc5346  12:18:45 PM: debug "zw device: 02, command: 9881, payload: 00 71 05 15 01 " parsed to ['name':'lock', 'value':'locked', 'isStateChange':true, 'displayed':true, 'linkText':'Front Door Lock', 'descriptionText':Front Door Lock lock is locked]
5a9543fb-61d7-40b3-8304-5082b7fc5346  12:18:42 PM: debug "zw device: 02, command: 9881, payload: 00 71 05 16 01 " parsed to ['name':'lock', 'value':'unlocked', 'isStateChange':true, 'displayed':true, 'linkText':'Front Door Lock', 'descriptionText':Front Door Lock lock is unlocked]

Looks like maybe it’s sending that important code bit too late?

#8

I have the same exact scenario. Did you find a solution for recording user code in a spreadsheet? Thanks!