I am working on a Matter-over-Thread door lock. I am able to commission it using the SmartThings app, but the app does not show options to set the access code, toggle auto-lock on/off, or configure the door position sensor. However, when I commissioned the same device with the Apple Home app, these options were available.
Does the SmartThings app not support these features for Matter lock devices? If it does, how can I enable them?
Codes are set in the SmartThings Guest Access applet within the SmartThings app. Install that, then open the applet and click top left to switch from Locks to Lock Codes
Auto-lock and other vendor specific features are not required by the Matter specification and may not be implemented by ST. I see no Matter lock profiles that contain an auto lock or door position sensor capability. What is the make/model of the lock?
If you don’t have access to SLGA, then you won’t be able to manage access codes via the ST app. The only locks that have a specific profile that allows for adding codes via the device panel are the Aqara U200 and U300.
As to why Apple Home finds those features, it could be that they determine a device’s capabilities dynamically or perhaps have a larger number of vendor specific definitions. The vast majority of Matter devices in ST require a static definition of the device’s capabilities based on either the vendorId and productId or matching generically based on the deviceTypeId(s) identified in the exposed endpoints.
Auto Relock attribute and auto lock events are part of the Matter standard and the SmartThings SDK supports them but the stock matter-lock driver does not handle those so they’re not exposed to the app. Just like happened with the unbolt feature of Matter 1.2 which is taking a long time to be exposed to the user.
The solutions are either a custom driver (not the way to go in my opinion being standard features) or convincing Samsung to implement it, but usually they only modify drivers if it’s to support a Works With SmartThings certified device (and even then that doesn’t mean they’ll add the standard features).
The auto lock event is actually handled by the driver, it emits a locked event with the data being “auto” as the source of the lock operation. I don’t know if that’s displayed to the user though or if it can be used in automations, I guess not.
The driver has to be modified to have a profile that supports those capabilities and handlers developed, if there aren’t default handlers, to process but events to/from the device and the mobile app.
Yeah, it’s in the Door Lock cluster section of the spec and the attribute is called AutoRelockTime. Maybe you weren’t looking in the Application Clusters Specification document?
That only seems to be supported for the locks that use the new-matter-lock subdriver which in the current fingerprints are just the Aqara U200 and U300. However, the profile for those locks is the lock-user-pin profile which doesn’t seem to expose anything about the source of the lock/unlock event (nor much of any of the subdriver capabilities) much less having preferences to set the capabilities.