So, does the condition of “pressing the tag” appear in the Automation page, meaning the only missing part is the ability to unlock the doors after triggering it?
I ask because for a device to appear in the Automation view, it needs to have something configured on its device presentation.
I can take a look at the smart lock’s configuration to see if something’s missing, I just need the following information:
Support access to your account
Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
Where are you trying to set this up? You should be looking in the “Smart button action tab” and selecting “Pressed” or “Held” under the Automations label.
I think that Zigbang lock is a Wi-Fi lock that is accessed in ST through Linked Services. Wondering if that might be why it’s not being exposed for automations.
The type of integration shouldn’t affect this way, but it’s a good point.
Checking its device presentation, I see it only has a configuration for “conditions” using the “battery” capability and has no options for “actions”:
So, that must be why it doesn’t appear in the “control devices” section.
In this case, @Ben_Bibbings, you need to contact Samsung’s Customer Support to ask if they have more information about why the device doesn’t this configuration since the manufacturer is the one that defines the device presentation.
Note: Are you using an official integration? I see the device includes custom capabilities with a generic namespace like: absoluteweather46907.lockstaterelease. Generally, custom capabilities from Samsung devices have a particular namespace .
Devices have capabilities and those are exposed in the ST app via the device Presentation. The Presentation has sections that define what is exposed when viewed in a list of devices (Dashboard), what is exposed on the device card/details page (Detail View), and what is exposed via automations/Routines (Automations). The device developer(s) decide what is available in each of those views of the Presentation. So, the ability to lock/unlock can be exposed on the Dashboard and Detail View, but still not be made available in the Automations. I’ve never seen a good explanation for why certain capabilities aren’t included in the Automations section of the Presentation, but it’s a fairly common occurrence.
One suggestion to solve for your use case would be to create a virtual lock that can be associated with your tag. You could then use that as a proxy in a 3rd party rules engine like sharptools.io and create a rule that when the virtual lock is unlocked, sharptools would send an unlock command to ST’s API. If your lock has an integration with a voice assistant like Alexa, you can do something similar with the ST Alexa skill and Alexa routines.