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
- Pair U200 with Aqara Hub M3, enable multi-admin to Home Assistant.
- Monitor
state_attr('lock.<your_lock>', 'changed_by') in HA 2025.09.
- Perform unlock with fingerprint, key, Aqara app, HA app, Apple Home Key.
- 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
1 Like
@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:
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!
@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!
@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:
. 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!
@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.
