Unfortunately, it turns out that Nuki Lock 4.0 also does not support user and PIN code management over Matter.
What makes this especially confusing is that the device claims it does. The Door Lock cluster reports the following AcceptedCommandList:
[00, 01, 0B, 0C, 0D, 0E, 0F, 10, 1A, 1B, 1D, 22, 24, 26, 27, 28, 29]
which includes all the user and credential commands (SetCredential, GetCredentialStatus, SetUser, GetUser, etc.).
However, in practice any command other than lock/unlock/unbolt either produces no response or causes the device to reset its Matter session, after which Hubitat immediately re-initializes and re-subscribes.
At the same time, the Door Lock FeatureMap attribute returns 0x00, which means:
- no user management
- no PINs
- no schedules
- no credential features
— only the mandatory basic lock/unlock functionality.
So in reality, FeatureMap is telling the truth, and the credential commands listed in AcceptedCommandList (0xFFF9) are effectively unusable.
This creates a very inconsistent and misleading implementation:
- Some features (like unbolt) work even though they are not declared in the FeatureMap.
- Other features (users, PINs) are declared in the AcceptedCommandList but do not actually work.
So there is no reliable way for a controller to know what is really supported unless it tries and breaks the session.
I found this the hard way after several hours of testing, hoping Nuki might be one of the few Matter locks that really expose full credential management — unfortunately it does not.