Thanks for that. Must have been a bit dense the other day since I am using the Maker API, but just for the HSM calls.
I ended up making a quick driver for multiple buttons and then adding devices for each family member so they had their own unique identifier.
In NFC Tasks (you don't need NFC Tools for everyone else), I added 3 user variables:
{VAR_URL} http://10.0.0.10/apps/api/15/devices/
{VAR_DEVICE} USER DEVICE FROM THE DRIVER
{VAR_ACCESS} ?access_token=OUATH
Using NFC Tools, made a GET task (this is for pushing button #1):
{VAR_URL}{VAR_DEVICE}push/1{VAR_ACCESS}
Now if anyone reads that tag, it's a bunch of useless variable names. If the user has NFC tasks installed and those variables set, they get the desired outcome.
Works really slick, and allows per-user filtering of the button presses to RM actions. Any random person gets or learns anything from the tag.
