I’d like to share my experience with the Aqara U200 smart lock with keypad, and see if anyone else is facing similar problems since the firmware v80 update.
My issues started on June 1st, 2025, and I reached out to Aqara support on June 3rd, but unfortunately, nothing has been resolved. The issue has now occurred three times.
The most serious incident happened on June 22:
I tried unlocking the door using my Apple Watch Home Key, but the lock didn’t respond.
In the Aqara app, I saw that the status changed from unlocked to locked via Matter, but the motor never turned.
I couldn’t unlock it even via Bluetooth with my iPhone.
Since my physical key was inside, I was almost forced to call a locksmith — but luckily, an automatic calibration made the motor turn in the opposite direction, and I was able to enter ( Fortunately, I had my smartphone with me.).
Other observations:
After calibration, the lock was able to lock but wouldn’t unlock .
I had to switch between US and EU modes multiple times before it started working again.
I also removed the lock from HomeKit and regenerated the Home Keys — but the issue remains.
Since firmware v80, I’ve completely lost trust in the product’s reliability . It puts my home access and security at risk .
Questions for other users:
Are you also having issues since the v80 update?
Has your lock ever become unresponsive or failed to unlock?
Did anyone manage to solve the problem or roll back to v78, which was working fine for me?
Thanks in advance for any feedback — I’d like to know if I’m alone in this situation or not.
Thank you for sharing your detailed experience with the Aqara U200 smart lock and the challenges faced since the firmware v80 update. It’s clear that these issues are quite frustrating, especially when they affect your home security and convenience.
From the insights I have, it seems that firmware updates occasionally bring unforeseen issues, and your case with the U200 lock is a prime example. While there isn’t a direct reference to a rollback to v78 specifically, here are a few suggestions based on similar scenarios:
Calibration Issues: If the lock occasionally responds through automatic calibration, you might want to attempt a manual recalibration through the Aqara Home app. Navigate to “Settings” > “Calibrate Lock” to see if this stabilizes the behavior.
Mode Switching: You mentioned toggling between US and EU modes. Ensuring that the lock is firmly set in one mode might prevent further confusion in the system.
Firmware Update: While rolling back isn’t directly mentioned, you might want to check if there are any new updates or beta versions available that address these v80 issues. In the app, go to Profile > Firmware Update and enable beta updates.
Connectivity Checks: Verify your network connections as inconsistencies can sometimes affect smart devices, even though this seems more like a firmware glitch.
If these steps don’t resolve the issue, and considering you’ve already reached out to support, it might be beneficial to continue engaging with them for a more tailored technical solution. Sharing your experience here is also valuable, as it helps gauge if other users face similar issues, potentially leading to a collective resolution.
Thank you for your patience and for contributing to the community. Let’s hope for a swift resolution so you can regain confidence in your smart home setup!
Thank you for sharing your detailed experience with the Aqara U200 smart lock. We sincerely apologize for the inconvenience caused by the firmware v80 update.
We’re currently investigating this issue, but out of 60 testers in our group, only one other user has reported a similar problem. To help us better understand and resolve this, would you be willing to share your lock’s log files with us? Your data could be invaluable in identifying the root cause.
As a token of appreciation for your cooperation, we’d like to offer you a small gift for your time and effort. Please let us know if you’re able to assist, and we’ll guide you through the log extraction process.
Here are the details we need from you:
Which firmware version did you upgrade from to v80?
What iOS version is your phone running?
How many shared users are there besides your Home Keys? Have you set up a Schedule PIN Code in Apple Home?
Please follow the instructions below to provide the lock’s log files for our analysis.
Please make sure you go to the Aqara Home app>Profiel> firmware>"…"on the right upper corner>enable beta firmware> then reproduce the issue and upload the log on the Aqara Home app, please check the video and screenshot to upload. Please send the Log file to kaiming.yu-a1550@aqara.com
Please provide your address so we can send you a small gift
Your help is greatly appreciated. Let us know if you need any assistance. Thank you for supporting Aqara!
I want to emphasize that when buying any smart lock with a design like the U200, we must understand the risks associated with this device. For example, I hid a spare key for the door in a secret place in case of emergency opening of the lock.
With this comment I do not want to justify the shortcomings that you found in the U200 smart lock.
It was quite difficult to implement a M100 hub. I had to factory reset the U200. Then install in Aqara App. Then bind with the M100 hub in the Aqara App. After that I added the U200 back to Apple Homekit, then using matter sharing to SmartThings, Google Home and Alexa.
It took a while to configure it all, I am very happy I can now approach the front door, my face is recognised and the lock unlocks.
The only issue I have had with firmware V.80 is Alexa announces a random,’ the front door is locked’, at random times of the day. The lock logs doesn’t tell me anything useful.
Thank you again for your support and your interest in resolving this issue.
I’m now able to provide all the requested information, as well as the log files.
Here are my answers:
Firmware version before v80:
I upgraded from firmware v78, which was working reliably without any issues. After checking my logs, I realized I made a mistake — it seems I actually upgraded from firmware v77 to v80
iOS version:
I’m using iOS 18.5 (22F76) on my iPhone 13.
Additional users and Apple Home setup:
I have 4 additional users besides my Home Keys:
• 1 user with both fingerprint and code access (admin)
• 1 user with both fingerprint access only (admin)
• 2 users with fingerprint access only (users)
I also have a PIN code set up in Apple Home, in addition to the Home Keys.
Log files:
I’m attaching the log file to an email sending it to kaiming.yu-a1550@aqara.com as requested.
Additionally, I’m also attaching the video showing how my lock operates: the latch automatically extends when the door is closed, and it retracts when the handle is turned. The lock mechanism actively blocks the handle from turning when the door is locked.
It seems to me that I heard the watch make the success sound.
For now, it’s working again (for a few days). I do get the success message and the door opens, and if it’s open, it closes with the Apple Watch HomeKey.
To lock the door, I usually press the lock button; I don’t use the watch for that**
In my case, I don’t have an Aqara hub — I’m using my Apple TV 4K as a Matter bridge. So far, I haven’t set up any sharing with Google, Alexa, or SmartThings.
My priority right now is to make everything stable and reliable again. Once that’s the case, I might try integrating it with a home automation system like Home Assistant or Jeedom, but for now I prefer not to add any extra complexity.
My main goal is simply to get the lock working again as it used to before the v80 update or latest.
Thank you for the information. Based on what you’ve provided, the HomeKey verification was successful, but the lock failed to unlock. If this issue occurs again, please let us know and observe whether the keypad plays a successful unlock sound when using HomeKey. If possible, recording a video would help us analyze the problem more effectively. Thanks!
I just experienced a similar issue at 10:12am. Neither my watch nor my phone is recognized. There is a sound, but it comes from the lock itself and it’s not the success sound…
The watch doesn’t make any sound, and the same goes for the phone — nothing happens, even if I open the Wallet app and manually select the key.
This time, I was able to enter using my fingerprint. I even managed to lock the door using the Apple Home app.
This afternoon, it started working again — honestly, I have no idea why. It’s really strange.
I’ve been having similar issues with my U100. My level of trust in the lock has become so low that I won’t even take out the trash without grabbing my keys out of fear of lockout. Despite, with the exception of an NFC tag, every method of entry being configured, the physical key is the only one I’m confident in. Home Key, fingerprint, keypad all fail more than 50% of the time and the lock will sometimes lock itself, even though I have disabled that feature. I had such high hopes when i bought it. It wasn’t perfect, but it sure seemed like it could be with a few firmware updates. Now, it’s just a headache.
I successfully installed the diagnostic profile on my iPhone.
However, I’m having trouble installing the one for the Apple TV.
When I transfer the HomeNetworkDiagnostics_tvOS.mobileconfig file to my iPhone, it only offers to install it on the iPhone or the Apple Watch — there’s no option for the Apple TV.
I tried downloading the file multiple times but the result is always the same.
I also compared the Home Network Diagnostics for tvOS and Home Network Diagnostics (HomePod) for tvOS profiles — the contents of the files appear to be exactly the same. This makes me wonder if there might be an issue with the profile available on Apple’s website.
Would you happen to have a working version of the profile specifically for Apple TV?
I’d really like to retrieve the logs from it, as I don’t have a HomePod — only an Apple TV 4K.
Thank you for your support. To install the diagnostic profile on your Apple TV, please refer to the attached guide: Home_Network_Diagnostics_Logging_Instructions_tvOS.pdf.
I successfully activated the diagnostic profile for the Apple TV using the guide.
Now I’m waiting for the issue to occur again so I can collect the logs.
Please note that the log file is quite large — I won’t be able to send it by email.
(I did a test with the iPhone logs, and the file is over 318 MB.)
Could you please contact us via the Slack App? Using Slack allows you to share large log files more easily.
Additionally, please note that the profile will expire in 7 days. If you don’t use it within this period, it will be automatically deleted from your phone. Therefore, please ensure the profile is still in your device before capturing the logs.
As a software developer myself, two questions come to mind that don’t seem to have been asked:
Are all of the people having trouble using Matter? I have a U100, a U300 and an M1 hub and frankly I gave up on using the hub because of problems like this. Going back to direct HomeKit connection made all of these issues disappear for me.
To Aqara. I’m very concerned that:
A. You only have 60 beta testers. You should have a lot more people with “doors” that are just a piece of wood with a lock in it that they interact with multiple times a day. That said, if > 1% of your testers ran into problems, you should have tracked this down before releasing the firmware. That translates to a lot of users in the real world.
Questions for other users:
