Hello
Exact same problem for me … Apple sends me a notification and whatever I try (automation through devices or entities) it doesn’t work in Homeassistant
There is something in GitHub (new feature or issue)
https://github.com/home-assistant/core/pull/151310
I don’t master GitHub so not sure if a new feature or issue
Is there anyone that knows what does the autorelock time function do? I am testing the aqara U200 Lite and using matter device integration it shows this option which i cannot relate to the app version.
BTW, something no one has reported here is that some functionalities only will show up after pinging the unit :P. While I did suceed pairing the device to my matter OPTBR (an sonoff usb-E dongle), it never showed the option to lock and unlock the door. It still cannot show status, but after sending a ping to the unit via matter integration, magically it showed the control option.
How did you pair your lock to the Sonoff? I currently have my lock using an Amazon Echo as a OTBR which I want to get rid of and use the Sonoff instead.
Hi Chris,
First I did flash the sonoff dongle using the official web tool to flash it as a thread coordinator device. Be aware that the device cannot be used anymore as a zigbee coordinator if that is the device primary role. Here is the link to the sonoff official guide
While I don’t remember all steps, they are reported elsewhere if you google “how to add a matter device using OTBR” (open thread border router). But this is why I did:
- Remove device from the aqara integration fully.
- Get your OTBR in place in home assistant, and this is quite of a “try and error” depending how you pair your devices. I did suceed because I have an iphone which I used to get the credentials but may be different if you pair devices using an android device.
- Once all above, pair the device using matter link and here I don’t remember if I did it first on the official app or on the IOS home app that never had used before.
- If your matter device shows up in HA, then just try to ping to it and refresh. This was usefull to me because before that, the only entity will show to me was “autorelock time function” and “push update”. Then after that ping, the entity to lock/unlock the door shows up.
1 Like
This is with a zbt-2 in Thread setup btw… still cannot see who opened/closed the lock though. That would be nice.
Even if you cannot see the exact user that opened/closed the lock, are you able to see the method it was opened with in any of the events?
I’d like to be able to tell if it was opened by somebody manually using the indoor latch vs someone unlocking it from the outside via a valid code, fingerprint etc
Thanks
i cant really tell, i t just says it was triggered. If you have the lock attached to homekit and then expose it via matter, you do get a message from homekit saying that another integration opened the door. So possibly this might be seen but i would not to test and testing time is limited atm. There is also a matter bridge https://matterbridge.io/ which might be usefull too. Have not tried it but will give it a shot too.
I recently installed the U400 Aqara lock. I attached the lock to HomeKit, then exposed it via matter to HA.
The lock entity that is created exposes a “Changed By” attribute which I have successfully used in automations to take action depending on the method of unlock. My rough notes on this value that are working so far:
- Keypad (unlocked externally with a code)
- Alira (unlocked externally with UWB)
- Remote (unlocked via HA or HomeKit over Matter)
- Unknown (unlocked externally via fingerprint)
- Unspecified (unlocked internally via latch)
Setting up an automation looking for the lock moving to a state of unlocked with conditions of the Changed By value matching these seems to work fine - for example, I am disarming my alarm automatically whenever the lock unlocks via Keypad, Remote, Alira etc but not Unspecified (so unlocking internally can’t disarm it).
The values of Unspecified vs Unknown are a bit odd - it could be because I added the fingerprint on the lock itself so it comes through as Unknown rather than a user ID I might get if I set this up via another method… but it’s working OK like this so far.
I’ve been testing the Aqara Smart Lock U200 with Home Assistant via Matter, and while the hardware is genuinely solid and the price point is attractive, the Matter implementation is unfortunately incomplete. Based on real‑world behavior and a full Matter diagnostic dump, several core features of the Door Lock cluster are simply not implemented correctly.
1. PIN codes via Matter do not sync to the keypad
Home Assistant successfully writes credentials into the Matter Door Lock cluster, and maybe the U200 stores them internally. However, I think the motor unit does not reliably push these credentials to the external keypad over Bluetooth. Result:
- HA shows the PIN as “set”
- The keypad never accepts it
- No error is reported
Creating the same PIN in the Aqara app works instantly, which confirms the hardware is fine — the issue could be in Aqara’s Matter stack or somewhere else. I don't know exactly and the longer I am investigating the more unclear it is for me.
The U200 does not expose any of the required Matter events like:
- unlock source
- user index
- credential type
- PIN usage events
- failed attempt events
- programming events
That means there is no way for HA to know who unlocked the door.
This is why Home Assistant always shows the attribute changed_by: unspecified when looking into the HA dev-tools.
This is what matter server says:
2026-07-05 22:08:02.686 INFO ... Received event doorLock.lockOperation ... lockOperationType: 0 operationSource: 0 userIndex: null ...
The lock is not sending any ClientID oder attributes.
3. Thread connectivity is fine
The Thread cluster reports stable routing and normal behavior. This confirms the issue is not related to Thread or the border router. I am using a ZBT-2 with nothing else than a Thread-Network.
Conclusion
The Aqara U200 is mechanically okay and very affordable, but its Matter implementation is objectively incomplete. PIN management via Matter is not working, and the lock does not expose the required door Lock events that Home Assistant automations would depend on. Even on the latest firmware, the device behaves like a partially implemented prototype rather than a fully compliant Matter lock. Which is even more frustrating since this is one of Aqaras "works with home assistant" certified locks.
For anyone relying on Matter for PIN management or automation, the U200 is currently not suitable. The Aqara app works, but Matter does not.
Or am I missing something here? Since I have no Apple border router here I can't test this Apple first and then link the whole subset to home assistant.
2 Likes
It might be a bug on HA code management; codes do work well via Apple Home (Matter).
Hi guys.
I’ve recently installed this lock and added it to home asssitant. This is my first matter device running on a sonoff thread dongle.
I the matter server log I see this every so often
peer-unresponsive
2026-07-11 21:24:04.665 INFO InteractionMessenger @1:2•06e9⇵fbe1 Error sending success after final data report chunk [peer-unresponsive] Peer is no longer responding to active session (timed out after 32.8s)
Is this normal or is there a problem?
I would really appreciate any advice