U200 & HA Lock status sometimes delayed by 20–130 seconds

Aqara Products
, , , , ,
1

Hi everyone,

I’m trying to understand whether anyone else is experiencing delayed status updates from the Aqara Smart Lock U200 when connected to Home Assistant through Matter over Thread.

The lock itself unlocks physically without any noticeable delay. However, Home Assistant sometimes continues showing it as locked for a long time after the door has already been unlocked and opened. Eventually, the state changes to unlocked, but the delay can range from approximately 20 seconds to more than two minutes.

This is especially problematic for some of my automations because I need to confirm that the lock was genuinely unlocked.

My current setup:

  • Aqara U200 firmware: 085
  • Home Assistant Core: 2026.7.4
  • Matter Server app: 9.1.1
  • Matter Server implementation: matter.js 1.3.3 / matter.js 0.17.7
  • Connection: Matter over Thread
  • The U200 is shared with both Google Home and Home Assistant using Matter multi-admin
  • The Thread network has Google/Nest infrastructure and a Home Assistant OpenThread Border Router

I compared the entrance-door contact timestamp with the time at which Home Assistant received the U200 unlocked state.

Some results:

  • Normal reports: approximately 1–2 seconds
  • Several reports took more than 30 seconds
  • Worst confirmed report: approximately 134 seconds

The issue is intermittent. The same lock can report almost instantly several times and then take one or two minutes on another attempt.

A relevant detail is that the problem became much more frequent after updating the Home Assistant OpenThread Border Router app from 3.0.2 to 3.1.0. However, I had already observed some delayed reports before that update, so I cannot conclude that OTBR 3.1.0 caused it.

The installation also migrated from the older Python-based Matter Server to the new matter.js-based Matter Server 9.x around the end of June. Unfortunately, my Home Assistant recorder no longer contains enough historical lock events to compare the behavior before and after that migration.

The U200 battery was between approximately 55% and 47% during these observations. Delays occurred at both higher and lower battery levels, so there is no clear battery correlation.

I would appreciate hearing from other U200 users:

  1. Do you see an immediate state update after manually unlocking the lock?
  2. Have you noticed delays of 20–120 seconds in Home Assistant, Google Home, Apple Home, or another Matter controller?
  3. Are you using Matter Server 9.x or another matter.js-based controller?
  4. Is your U200 connected to more than one Matter ecosystem?
  5. Which U200 firmware and Thread Border Router are you using?
  6. Did the behavior change after a recent Matter Server, Thread Border Router, or U200 firmware update?

At this stage, I don’t know whether the delay originates in the U200 firmware, the Thread network, the Matter subscription/reporting path, or the controller. I’m mainly trying to establish whether this is isolated to my installation or a wider U200 issue.

Thanks!

1 Like
2

@Expert Could you help with this topic please?

3

As you are using home assistant and Google for your matter control, would you know which is the main controller? Do you have a controller stick connected directly to home assistant?

The delay sounds to me like a potential ip6 routing issue and I’m not saying it is but just sounds like it with the delay.

Generally, home assistant should be instantaneous as everything should be running locally. So if there is a massive delay, I would check and possibly reboot your thread devices / Matter controllers

4

Does the open thread controller enable you to connect to the Google thread controller i.e. create a single thread network?

If you’ve no other powered thread devices then signal strength could also be an issue

5

Remove Google from the sequence and see if the network problem goes away.

6

Hi!

I had a similar problem today and my lock kept reporting inconsistent status in Home Assistant even though it showed the correct status in the Aqara App. I’m using Apple TV 4K 3rd gen as my Thread Border router.

I’ve just updated to 9.2.0-version lately in HA when it was released, and this is the first time i noticed the problem with one of my Aqara U200 locks. The other of my Aqara U200 locks works fine and reported the status o.k.

I fixed the problem by pressing the physical set button on the lock and recalibrated the lock. It would show Unlocked, even though the lock was locked and then it also showed locking when in Home Assistant. Now everything is back to normal and the status is reported as expected. Don’t know if this helps but just something which perhaps you could try?

2 Likes