Aqara U400 lock - not yet supported

I paired to my Apple Home, then paired to Hubitat. Looks like Hubitat only recognizes it as a generic matter device. Happy to provide logs/details if Hubitat can help with adding support.

Eventually looking for a solution that lets me set lock codes remotely for this lock.

dev:3112026-01-09 09:38:45.478 AMinfofingerprint endpointId:"02", inClusters:"001D,002F", outClusters:"", model:"Aqara Smart Lock U400", manufacturer:"Aqara", controllerType:"MAT"
dev:3112026-01-09 09:38:45.477 AMinfofingerprint endpointId:"01", inClusters:"0003,001D,0101,1349FC03", outClusters:"", model:"Aqara Smart Lock U400", manufacturer:"Aqara", controllerType:"MAT"
1 Like

Have you tried switching to the "Generic Matter Lock" driver to see if that works? (Be sure to run "Configure" after.)

I'm guessing you might be missing at least battery events (or lock events) that way based on a quick look, but at least the commands should work for a standard device. Assuming so, you could you also share the value of "Endpoint Id" in the "Device Details" table on the "Device Info" tab? (If one of these things is the only problem, that's an easy fix for a future version!)

There's also something in the fingerprints I don't recognize, which I assume is a manufacturer-specific cluster ( 1349FC03), but hopefully there's nothing important there. :slight_smile:

1 Like

Currently I have yet to find a matter lock that supports code management.

1 Like

NUKI lock likely supports code management, but I do not have a keypad to test it.

1 Like

I can add codes though HomeKit, wouldn’t that infer this one does?

It all depends on two things, what the lock actually supports, and if the device is brought in via a matter bridge, if the bridge and the device supports it.
The aqara locks (zigbee) brought in via an m3 hub using our generic matter bridge don't suport it, other matter locks (thread) via HK I've tested don't support it either.
So I'm interested in a lock that does, but haven't found one yet, though to be honest I've only tested like 5 matter locks so far, and three of them were Aqara, one Yale and the other an Eufy
The Yale, Eufi and Aqara U200 can use our Generic Matter Lock driver and for sure do not support code setting or code reading.

2 Likes

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.

5 Likes

And they still got their certificate? Seems Matter is not yet magical, I guess.

2 Likes

The Matter specifications are very complex; I can't judge... It seems that Nuki is not the only manufacturer using this approach - while they expose a variety of attributes, the FeatureMap ultimately determines which functions are enabled and which are not.

1 Like