Expose unlock method/user in Matter events for U50 (DoorLockOperationType)

[shanegreaves]

Describe the enhancement

I'm using the Aqara Smart Lock U50 with Home Assistant via Matter, and I've discovered that all lock/unlock events show changed_by:
"Unknown" - meaning I cannot determine how or who unlocked the door.
The Issue

The Matter specification includes the DoorLockOperationType attribute and door lock operation events that should report:

• How the lock was operated (keypad, fingerprint, key, manual thumb turn, remote/app, HomeKey, etc.)
• Which user triggered the unlock (user ID for registered fingerprints/codes)
• I can see these events in the Aqara app.

Home Assistant 2025.9 added support for displaying this information from Matter locks, but the Aqara U50 does not appear to expose these events through Matter. Interestingly, the Aqara app event log does show "opened from inside or key" vs other unlock methods - so the lock clearly detects and records this information internally. It's just not being exposed through the Matter protocol.

Why This Matters

This missing functionality prevents several important use cases:

These features worked for users on SmartThings before migrating to Matter, and they work in the native Aqara app - losing them when using Matter is a significant regression.

Device or feature details

No response

Use cases

1. Security auditing - I cannot see who unlocked the door or when
2. User-specific automations - Cannot trigger different actions based on which family member unlocked (e.g., "Dad arrived home" vs "Kids arrived home")
3. Unlock method automations - Cannot distinguish between someone entering a code vs using a key vs unlocking from inside

Anything else?

home-assistant/core#149861
The PR author @jvmahon had done the work to implement the feature and, the chosen method #3 was rejected.

1. Possible architectural change to allow user_index and eventually user_name as "standard" properties of the base lock entity.
2. Add a sensor entity that conveys user_name after matter.js allows it.
3. And you already know this, using the extra_state_attributes. Though I accept that's been rejected.

Reviewing the PR there was a solution implemented that could have given us the feature. While I am sure the reasons are valid, five months later we are still waiting for the feature to be implemented. Could we not have had the feature while the perfect solution is implemented in the future? Could this have been perfect being the enemy of good?

[jvmahon]

I had previously submitted a PR that shows "how" the lock was unlocked (Remote, PIN, Manual, etc.), but not who unlocked it.

My plan is that, once the matterjs server is done, I will re-submit my PR and will, once again, try for the use of the "extra state attribute" feature to see if I can better convince Home Assistant team to allow it in this limited case.

The information could be conveyed by a sensor, but that is a poor solution since the attribute information is then not conveyed in the trigger data when the lock changes its state (making it difficult to write automations, particularly automations that may trigger for multiple different locks and want to process the user name information).