Aqara U200 – Firmware / Matter (Door Lock cluster)

Everything Matter
,
1

Aqara U200 – Incorrect changed_by mapping in Matter (Door Lock OperationSource)

Environment

  • Lock: Aqara U200 (Matter over Thread)
  • Hub: Aqara Hub M3
  • Controller: Home Assistant 2025.09 stable (Matter integration)
  • Commissioning: U200 paired to M3, then multi-admin to Home Assistant
  • Firmware versions:
    • U200 FW: 3.0.0_0084
    • M3 FW: 4.3.8_021
    • iOS Apple Home Key tested on: iPhone 15 Pro (iOS 18.6.2) & Apple Watch Ultra 2 (watchOS 11.6.1)

Description
After updating to Home Assistant 2025.09, the lock entity exposes the changed_by attribute (derived from Matter Door Lock → LockOperation.OperationSource). On the U200, the values do not match the actual operation source.

Observed vs Expected

Action Expected Observed
Fingerprint unlock biometric keypad
Physical key/manual manual keypad
Aqara app unlock proprietary remote / remote keypad
Aqara app lock proprietary remote / remote remote (on lock only)
Home Assistant lock/unlock remote remote (inconsistent on unlock)
Apple Home Key rfid rfid (OK)
Biometric ever reported? biometric never (always keypad)
Proprietary remote ever reported? proprietary remote never
Aliro ever reported? aliro never

Impact

  • Security automations become unreliable (e.g. disarming when it should not).
  • Audit logs lose accuracy.
  • Users cannot trust changed_by for conditional logic.

Steps to reproduce

  1. Pair U200 with Aqara Hub M3, enable multi-admin to Home Assistant.
  2. Monitor state_attr('lock.<your_lock>', 'changed_by') in HA 2025.09.
  3. Perform unlock with fingerprint, key, Aqara app, HA app, Apple Home Key.
  4. Compare observed vs expected.

Requested Fix

  • Map fingerprint → biometric
  • Map physical key/manual → manual
  • Aqara app (cloud/app) → proprietary remote (consistent lock/unlock)
  • Home Assistant app → remote
  • Apple Home Key → rfid
  • Report aliro if supported
4 Likes
2

@alexruperez Thank you for sharing such a detailed breakdown of the changed_by mapping issue with the Aqara U200 in a Matter/Home Assistant environment. I can see how mismatches between the reported operation source and the actual unlock method could impact both security automations and audit trail reliability.

Currently, based on the available reference information, there isn’t direct documentation or troubleshooting guidance specifically addressing the mapping of the LockOperation.OperationSource (or the changed_by attribute) for the Aqara U200 in Matter integrations. Most references focus on pairing, firmware updates, Home Key issues, and general troubleshooting for connectivity and calibration. Unfortunately, this means there’s no official mapping chart or fix for the observed discrepancies in source reporting.

Given the impact you described—especially on automations and audit logs—I recommend sharing this case with the broader community to see if others have found workarounds or if custom Home Assistant templates have been used to remap the attributes for conditional logic. For any suggestions or to request further enhancements, please submit your feedback through Aqara’s manual customer service channels, either via the Aqara Home App (Profile > Help & Feedback > Customer Service) or by scanning the following QR code:

400×400 9.45 KB

If you don’t have an Aqara Home account, you can click here to create a ticket.

Your detailed post is incredibly valuable for both the community and ongoing product improvements. If anyone in the forum has experienced similar issues or found solutions, please join the discussion!

1 Like
3

@alexruperez I’m sorry to hear you’re encountering issues with the changed_by attribute mapping on your Aqara U200 lock in Home Assistant. After checking our reference information, we don’t have specific details about this Matter Door Lock OperationSource mapping issue at the moment.

We understand how critical accurate changed_by data is for security automations and audit logs—unreliable mappings can definitely disrupt your setup. If you discover any workarounds or additional insights, sharing them with the community here could help others facing similar problems.

For a more direct resolution, we recommend submitting feedback through the Aqara Home App (Profile>Help&Feedback>Customer Service) or by clicking here if you don’t have an account. This will help our team investigate the issue further.

Thanks for bringing this to our attention, and we hope a solution is found soon!

4

@alexruperez Thank you for sharing such a detailed report on the changed_by mapping issue with the Aqara U200 lock in the Matter ecosystem. It’s clear this inconsistency is impacting the reliability of your security automations and audit logs, which is understandably frustrating.

After checking our reference information, we don’t currently have specific details addressing this particular mapping behavior. We apologize for the inconvenience this has caused.

To help resolve this, we recommend submitting feedback through our customer service channel—they can better escalate and investigate the issue. You can contact the Customer Service Team via the Aqara Home App (Profile>Help&Feedback>Customer Service) or by scanning the QR code:

400×400 9.45 KB
. If you don’t have an Aqara Home account, please click here to create a ticket.

Your detailed observations are valuable, and we appreciate you taking the time to document and share them. Hopefully, this can be addressed promptly to improve your experience.

If other community members have encountered similar issues, feel free to share your insights—collaboration often helps identify patterns and potential workarounds!

5

@alexruperez Thank you for sharing such a detailed report about the changed_by mapping issue with the Aqara U200 in Home Assistant. It’s clear you’ve put a lot of effort into documenting the problem, which is incredibly helpful for understanding the impact on security automations and audit logs.

After checking our reference information, we don’t currently have specific details about this Matter Door Lock OperationSource mapping issue. We apologize for the inconvenience this has caused.

We encourage you to share this with the community—other users might have encountered similar situations and could offer additional insights. For a more direct resolution, please consider submitting feedback through the Aqara Home App (Profile>Help&Feedback>Customer Service) or by clicking here if you don’t have an Aqara Home account. This will help our team better track and address the issue.

Thanks again for contributing to the community by highlighting this problem—your input is valuable for improving the user experience.

7

Thanks for the reminder! I’ve already submitted a detailed support ticket to Aqara, including diagnostics, Matter debug logs, and the full reproduction steps.
Kinsey from Aqara also confirmed on Slack that the team is already working on this issue.

I’ll keep this thread updated when there’s any progress or a new firmware addressing the Door Lock cluster behavior.

8

@alexruperez Thanks for the update, alexruperez! It’s great to hear you’ve already submitted a detailed support ticket with all the necessary diagnostics and logs—your proactive approach really helps the team address the issue efficiently. Knowing that Kinsey from Aqara has confirmed the team is working on it is reassuring, and we truly appreciate you committing to keep the thread updated with progress or firmware updates. Your dedication to improving the user experience and keeping the community in the loop is invaluable. Looking forward to hearing how it goes

9

I’m having similar issues. After firmware upgrade to 3.0.0_0085, changed_by attribute is Unspecified whenever it’s expected to be Manual or Keypad

10

@zappasmart You seem to be experiencing an issue with the changed_by attribute being Unspecified instead of Manual or Keypad after upgrading the U200 firmware to 3.0.0_0085. You can contact customer support for assistance.

Contact the Aqara Home App Customer Service Team (Profile> Help & Feedback > Customer Service) or scan the QR code:

400×400 9.45 KB

This will be more efficient. If you do not have an Aqara Home account, “Please click here” to create a ticket.

11

Hi @alexruperez did you hear back from Aqara about the fix for this issue?

12

@zappasmart no updates from Aqara team… :cry:

13

I fully agree with this assessment. The U200’s current Matter implementation is unfortunately incomplete, especially in the Door Lock cluster. Key features defined in the Matter spec — such as Operation Events, Operation Source, UserIndex, and CredentialType — are simply not exposed. As a result, platforms like Home Assistant only receive the basic lock state and fall back to changed_by: "unspecified" because the device never reports the actual unlock method.

What makes this even more frustrating is that this has been an open issue for quite a long time now. Some users have reported that commissioning the U200 through an Apple Border Router first enables additional Matter features, but when commissioned directly through Home Assistant, those same features remain disabled. This strongly suggests that Aqara’s implementation is inconsistent and not fully aligned with the Matter standard.

Considering that the U200 is officially “Works with Home Assistant” certified, it’s disappointing to see such gaps in functionality. I’m seriously considering returning my units as well — the hardware is fine, but the software side is clearly not fully implemented, and reliable event reporting is essential for a smart lock.

14

Quick update from my side: this issue still appears to be present on U200 firmware 3.0.0_0085.

I exported the Home Assistant history of the changed_by attribute, which is derived from Matter DoorLock.LockOperation.operationSource.

Across the exported history, excluding Unknown / unavailable states, the U200 has only ever reported:

  • Remote: 79 times
  • Unspecified: 56 times
  • RFID: 4 times

It has never reported any of the following operation sources:

  • Manual
  • Proprietary Remote
  • Keypad
  • Auto
  • Button
  • Schedule
  • Biometric
  • Aliro

This is despite regular use of fingerprint unlocking, manual operation, the Aqara app and other supported unlock methods.

I also checked the current Home Assistant Matter implementation. Home Assistant explicitly maps all Matter DoorLock.OperationSourceEnum values and reads operationSource directly from the LockOperation event. Therefore, this no longer looks like a Home Assistant mapping issue, but rather incomplete or incorrect operationSource reporting from the U200 Matter implementation.

So unfortunately, at least on firmware 3.0.0_0085, the original issue is still reproducible.

The impact remains the same: changed_by cannot be safely used for security automations or reliable audit logging.

@AqaraBot / Aqara team, could this please be escalated again to the U200 Matter firmware team? I originally provided diagnostics, Matter debug logs and reproduction steps, and was told the team was already investigating this.

15

@alexruperez Thanks for circling back with hard numbers — that history export is exactly the kind of evidence that helps narrow this down.

From what you’re seeing (mostly Remote / Unspecified, and only RFID being reliable), it does sound less like a Home Assistant enum mapping problem and more like the U200 not emitting (or not populating correctly) the Matter Door Lock → LockOperation event fields on certain unlock paths. Unfortunately, the reference info we have here doesn’t include any official details about the U200’s Matter OperationSource reporting behavior or a workaround/fix specific to operationSource, so there isn’t a reliable “forum fix” I can point to right now.

At this stage, the best path is to get this packaged as a firmware/Matter escalation with your diagnostics + reproducible steps (especially since you’ve already validated it across FW 3.0.0_0085):

Contact the Aqara Home App Customer Service Team (Profile> Help & Feedback > Customer Service) or scan the QR code:

400×400 9.45 KB

This will be more efficient. If you do not have an Aqara Home account, Please click here to create a ticket. Sorry for the trouble.

If you can, include in the ticket:

  • U200 firmware + M3 firmware
  • Commissioning path (paired to M3 → multi-admin to HA)
  • A short table like you posted (expected vs observed)
  • Matter debug logs around a fingerprint unlock + a manual/key action + an Aqara app unlock (the three that “never” show up correctly)

That should give the firmware team everything they need to reproduce and verify whether OperationSourceEnum is being left as Unspecified/misreported for those methods.