U200 Smart Lock with Keypad – Critical Issues Since Firmware v80 (June 2025)

Same here. Homekey continued to work for few days and today I noticed exactly the same behaviour: nothing happens when pressing my Apple Watch or iPhone against the keypad. I tried the thing with removing batteries from keypad and plugging back in but it didn’t change anything.
I hence reset Matter and homekey with it. Seems to work for now. But seriously, please fix it asap, it was a pain to do all these workarounds…

2 Likes

I reinstalled both profiles this morning, hoping the issue will occur again so I can capture and share the relevant logs.

1 Like

Hello,

Thank you for the information. We are currently investigating this issue.

Have you tried removing and reinserting the Li-battery in the lock to see if this restores HomeKey functionality?

1 Like

Thank you Fei_Ye. No, I only did it for the keypad. For now it is still working (after Matter reset).

1 Like

Hi i_olivier,

Could you please share the iOS logs when the issue recurs? This will help us address the root cause.

Log collection details:
• Requires installing specific configuration profiles on your iOS device (for log collection only)
• These profiles will not collect any personal user information
• I can provide the profile installation guide at your convenience

1 Like

Sure, where can I transmit them to you, do you need error and normal logs? I have the .zip which I downloaded before proceeding with the reset fix

1 Like

Hi,

I encountered the HomeKey issue again today — the lock didn’t respond at all to my iPhone or Apple Watch.

The issue occurred between 11:00 and 11:06 AM (Paris time) .

I’ve sent the logs by email to Kinsey, including:

  • Aqara Home app logs
  • iOS sysdiagnose
  • Apple TV diagnostics

You may need to ask your colleague to share those logs with you.

Also, earlier this morning, the lock played a melody when opening or closing — which is unusual, as that doesn’t normally happen in my configuration.

Fortunately, I was able to enter using my fingerprint. I haven’t encountered the full lockup or calibration loss this time.

Thanks again for following up.

1 Like

Hi Hans,

Could you please share the newest lock log( not iOS/tvOS log ), that will help us investigate what happened since 2025/07/04 11:00:00 to now.

1 Like

Hello
I’ll share the logs as soon as I get home from work.

For your information, I installed the v81 beta firmware on July 4th around 5:00 PM, and so far, I haven’t encountered any issues.

Regards

2 Likes

Hi,
I’ve emailed the logs to your colleague.
I hope you find the solution.

Thank you again for your help.

Regards

1 Like

Hello,

I’m writing because unfortunately, the lock has started behaving strangely again and displayed the messages:

“Deadbolt lock is abnormal”
“Please close the door to recover.”

However, the door was properly closed. I thought maybe it was because I hadn’t recalibrated the lock after updating to firmware v81, so I attempted both a manual and automatic calibration — but that actually made things worse.

The lock began to change status without physically moving, and at times, I thought it was working — but I could hear the motor running too far when unlocking.

After at least 20 minutes of attempts, I finally managed to get it calibrated.

During those attempts, I also removed the battery to force a reboot.

I’ve extracted the latest Aqara app logs from today , as well as iOS and tvOS diagnostics .

I will send your colleague the logs for the past 24 hours — the issue started at 9:30 PM and I managed to complete the calibration at 9:50 PM (Paris time).

PS: The first logs I sent earlier today correspond to the requested period from July 4th to now. The second set of logs, sent this evening, relates specifically to the issue encountered during calibration.

I hope these logs will help you identify the root cause of the issue.

Best regards,

Hans

1 Like

Hello,
I have the same issue with v80. Homekey works day or two, then stops working for some time, then it works again few days. Very frustrating. Luckily, I am able to use fingerprints to open the door.
I have tried removing from matter and add it again but same issue starts after some time.
FYI, using apple TV as hub. I have also email contact support on this issue, but it was not really helpful:
Good day ~
Will inform once getting any update news from R&D team ~

I chime in. I already had issues with v79. Yesterday I could open the lock with my Apple Watch for the first time since quite a while. Today it does not work.
I have 2 U200, both with same issue. HomePod mini as matter router.
Several Apple devices do not work for my family. Finger prints work fine, HomeKit also works fine with the U200. Only home keys have issues. No „success“ signal.
Any help appreciated.

Hi everyone,

Just a quick update following my exchanges with Kinsey from Aqara support:

The engineering team has identified the root cause of the HomeKey issue we’ve been experiencing. A fix will be included in an upcoming firmware update.

Thanks again to the team for their responsiveness — and hopefully this will resolve the problem for all U200 users soon.

Regards

2 Likes

I’m experiencing the same issues after updating from v77 to v80, so I am glad to read that there will be a fix. I’m also experiencing calibration failure as described in another topic on this forum though, so I hope this will also be covered.

Hi,

Just to share my experience — I also updated to firmware v81 (beta) but unfortunately, the same issues persisted: HomeKey not working reliably, calibration failures, and occasional lock error messages like “Deadbolt lock is abnormal.”

After encountering these issues again under v81, I sent Aqara the full logs from the past 7 days (including Aqara Home logs, iOS, and tvOS diagnostics).

Following their analysis, the engineering team confirmed they were able to identify the root cause, and a proper fix should be included in a future firmware update.

However, I haven’t received any information yet about when this next firmware version will be released.

So the problem is still present in v81, but a solution is on the way. Fingers crossed :crossed_fingers:

2 Likes

Dear Aqara Team,
any ETA for the fix?
Thx