Aqara U300 Smart Lock

Great thread here. I still struggled to get this working on my end, so sharing how I finally got there too!

Setup:

  • HA with Thread, Matter enabled
  • Eeros as Thread Border Routers for the Thread network
  • Aqara app

Steps:

  • Use Aqara app to setup the lock as instructed in manual, using local control with Bluetooth.
  • Have 1 admin user setup
  • On the lock, press “Set” firmly, the lock prompts for admin password/fingerprint so do that, then it gives menu options, choose Matter (#4 as of today)
  • In HA, under Matter integration, choose “Add device”, and then scan lock Matter QR code (you might have to prepare that step before doing the step above so it doesn’t time out)

After a minute or so, the lock appeared in HA!

Now I’m trying to add a HomeKey for my partner’s iPhone/watch (I’m an Android user so don’t know much about that), I haven’t figured that part out yet.

I see there are these triggers for the U300 in HA:

  • locking
  • opening
  • unlocking
  • {device name} locked
  • {device name} opened
  • {device name} unlocked

The locked/unlocked triggers work, but the opened one doesnt seem to trigger. I already activated the functionality in the U300 device to know when it is opened or closed and in the aqara app it shows correctly when I open the door.

Does anyone has the opened trigger working correctly in HA?

I use the zigbee based door sensors to know when the door is open or closed in HA as I only have the lock/unlock states in the matter intergration at this time and have other work arounds already setup as per a previous reply in this thread.

I noticed today that HA is telling me that there’s a new firmware update V1027 (and I am on V1025 at the moment). I was wondering any capability added to this FW?

Personally I want a capability put the lock to “Passage Mode” through HA rather than pressing the physical button. By the way I don’t have/use any aqara hub.

The Aqara app says:

Added: Static collection with dry battery power level change and reporting.

…whatever that means…

I just got my U300 yesterday. setup and already updated firmware. I didn’t aware of any change. OTA update from HA is failed though but update from Aqara app over bluetooth works just fine.

I want to make automation that change U300 operation mode from normal to “Night Latch” or “Passage Mode” but the mode change in HA doesn’t seems to change according to the U300 behavior and also setting in Aqara App.

My setup is

  • U300 / BT / Aqara App - for adding people and fingerprint
  • U300 / Matter over Thread via Nest Hub / HA - want to do some automation.

Anyone can guide me on how to make U300 change mode?

User code temporary disable time and Wrong code limit as well as the operating mode were the additions on 1027 update through HA.

Hmm I don’t have operating mode enity. What are the options there?

Were you able to update the lock through HA? Mine gives error after a while.

Mine updated to 1027 without issue at the time.

My Aqara Home app simply refused to set it up unless I had a thread border router and did not offer any local control / bluetooth option.
I put in a nest hub today and that got it into HA all good, and tried to share it to the Aqara home app but then it goes back to saying “you need a hub” and won’t go any further. Wonder what I’m doing wrong?!

BT is only used for the phone connection and management via the app, thread is needed to connect it to HA.

The option used to exist in HA 2025.12.2 but was removed in HA 2025.12.3 as the passage mode option did not conform to the Matter standard, apparently.

Just a quick update to this thread in regards to battery life for this lock based around my usage of it.

It's only taken till the date of this reply (almost 1 year exact since initial install date) to need to install new AA batteries in the unit so battery life overall has been satisfactory.

I’ve suddenly started seeing long periods of unavailability with my U300. I’m away from home so can’t check in the Aqara app. I was previously really reliable.

It’s on the latest version of it’s firmware:

Anyone know a possible cause of the issues? I haven’t found anything useful online as yet.

Do you have other thread devices on the network for meshing? I stopped having a similar issue with my P2 door sensor when using only just the one device soon as I added the lock.

No, this is the only device. It's not far from the hub though. I never had this issue until the last week or so (months of solid connectivity).

I recommend to invest in at least one other thread based device for the mesh to stabilize a little when it comes to making sure.

If you need, take out the batteries and put them back in to power cycle the lock just to refresh things and see if the issue persists.

Yeah ok, I'll see what is around that I could potentially buy. The thing is, most are end devices and not routers right? EDIT: I'll go and grab an IKEA Matter plug I think, cheap and easy test.

The connectivity seems to be fine for many hours, then long periods of unavailability.