Setting Up a PIN Code for Matter Smart Locks

[shun1017]

Matter-enabled door locks cannot currently be unlocked using Google Home and Google Nest Hub. I have already reviewed Google's policy, which states that unlocking requires a PIN code.

https://www.googlenestcommunity.com/t5/Smart-Home-Developer-Forum/matter-smart-lock-with-Google-Home...

How does Google Home expect Door Lock devices to register and manage the PIN code? If the method involves using the "Set Credential" command, it raises concerns about whether the door lock device can distinguish between a PIN code used for remote unlocking and one used for a numeric keypad on an outdoor unit. As we are in the process of developing smart door locks, we believe that our smart lock should maintain a clear separation between PIN codes used for Matter unlocking and those used for numeric keypads.

[armen_dpe · Accepted solution]

In the current setup, remote unlocking is not enabled for Matter door locks within the Google ecosystem unless a PIN code is mandated. If the setting "requirePINForRemoteOperation" is set to false, Google Home users will receive a message stating that the device cannot be unlocked remotely. However, if "requirePINForRemoteOperation" is set to true, indicating that a PIN code is necessary for remote unlocking, users must adhere to Google Home requirements by implementing a PIN. If a PIN code hasn't been previously set up through Google Home, typically, there's a master PIN code established on the lock just before the Google Home setup (some users shared using Apple’s Home App to set up the PIN). Users should utilize this PIN code for remote unlocking via Google Home, ensuring that only authorized users can access this feature.

I will share your feedback with internal teams for consideration. Google smart home ecosystem is constantly evolving, with new features being developed. Users should stay tuned for any changes within the Matter lock setup and usage. 

[shun1017]

Thank you for your reply. 

Could you please provide guidance on how to set "requirePINForRemoteOperation" to true within the Google echosystem? According to the Matter Application Cluster Specification, when the setting "requirePINForRemoteOpeation" is enabled:

"If the RequirePINforRemoteOperation attribute is True, then the PINCode field SHALL be provided, and the door lock SHALL NOT grant access if it is not provided."

Based on this specification, I understand that when "requirePINForRemoteOperation" is true, a PIN must be provided for both locking and unlocking. However, our intention is to require a PIN only for unlocking while allowing locking without a PIN. To achieve this, we believe that toggling the "requirePINForRemoteOperation" setting between locking and unlocking may be necessary.

Is it correct to assume that changes to "requirePINForRemoteOperation" are operated on the Google Home App side?

[Mell1947]

I'm beginning to believe that all this technology is getting ahead of the creators.

[hackztor]

no it is just Google being stupid. Show a warning if you are afraid of something but a user should be able to do what is wanted. Every other lock lets you unlock without a passcode from the app. Not complicated. Apps even let you set pin codes for users but not Google with Matter. This is Google's one chance at a unified ecosystem and Google is messing it up. how typical.