I will also chime in here and hope this is fixable. I currently have the need for UWB to always function in a multi door/lock scenario. I have a side entry door into the garage, a garage entry door into the kitchen, and of course a front door. Very frequent entry and exits to all doors and UWB “Should Just Work” in these cases without these scenario limitations stated above
2 Likes
I’ve contacted Samsung a few times today through different channels and I’m being told that there are certain versions of the Samsung Digital Key Framework and Google Play Services needed to use UWB for door locks. I can confirm that I have versions that exceed the minimum yet I don’t have UWB. One of the individuals told me that a firmware update on the lock may be needed to enable UWB as well as repairing the lock to the ecosystem. Could anyone provide a timeframe for when this will happen, in Samsung’s footnotes it states April 2026.
2 Likes
We’re currently looking into a proper fix for this issue.
Right now, a quick workaround would affect battery life on both your phone and the lock, so we’re working on a smarter, more optimized solution instead.
2 Likes
From what I understand, Samsung phones currently only support Aliro NFC; their UWB function hasn’t been launched yet.
Aqara’s UWB already supports both Aliro 0.9 and 1.0 protocols, and firmware V3104 / V3110 are both full versions with complete UWB support.
3 Likes
Kinsey - Thank you for the update!
1 Like
For me the Aqara app does not show the V3110 update. I have my lock setup using Matter in Apple Home, and then from there in Home Assistant. It shows update in Home Assistant but not in either Aqara app or Apple Home. Is there something I am missing? Is it safe to do the upgrade in HA ?
2 Likes
V3110 has passed the Matter and Apple Home certification tests and is now in rollout phase.
Aqara Home users can download and update via the Aqara Home app. Currently we are releasing the update in a gray-scale rollout, with only 20% of users eligible to receive it. The full official release is scheduled for May 22nd.
In addition, the official firmware has been uploaded to Matter. Updates are expected to be visible on all compatible ecosystems within these few days, though the release timeline may vary slightly across different platforms.
3 Likes
Thanks for the update which explains why I do not see on the app. My lock is working perfect, so I will wait until I can install from the app because I heard it is much faster.
1 Like
Hi Kinsey, I am currently running V3110 on my U400, and have unable to get UWB approach to work. I am on a Samsung S26 Ultra with the latest updates. I have a m100 hub, a Smartthings station, and a Nest 2 which are all connected to the same thread/matter. The U400 Digital key does generate into my Samsung Wallet, but there is no option for UWB. All I get is NFC. I know USB in general works as I have a digital key for my Ioniq 5N which uses USB unlock on approach. Any ideas why Samsung Digital wallet isn’t triggering the UWB?
1 Like
Any updates for Google Wallet support? Would love to use my pixel watch to unlock my door and that’s currently the only thing preventing me from purchasing
2 Likes
Suggestion: On my U100 even with auto lock enabled, when you close the door from the outside, the lock icon flashes red to give you the option to lock immediately. Can we enable that feature on the U400?
1 Like
It’s apparently supposed to come in Android 17, hence why they aren’t even giving hints about when it’s coming. But Android 16 launched in June, so hopefully 17 will too.
1 Like
Kinsey,
Has there been any progress or update on this issue? Please let me know when a solution has been found or an update to firmware for this is available.
THANK YOU!
1 Like
Has there been any progress or update on this issue for selectively disabling UWB at the lock level in a multi lock u400 home?
1 Like
I asked about this earlier. Turns out if you enabled auto-lock in the Aqara app, the lock will NOT display the lock icon when door is closed. You have to pick one or the other. I think it is very inconvenient.
If this is indeed your problem, the half-workaround is disable auto-lock in the app, but enable auto-lock in Apple Home App. This however, will not use the gyro in the door to detect the door is actually ‘closed’. It is purely timer based. Really hope Aqara can give us the option to always display the lock icon…
3 Likes
I have a question for Aqara Team. I’m living in the Netherlands and I have the Aqara U400 in combination with the Aqara G410 door cam. I had to set my Aqara profile to region United States in order to connect with the U400 doorlock. However I had to do the same with the G410 in order to connect with the lock. The problem now is that the live feed from the doorcam also goes via the server in the US, which give a uge lag (only up to 500 kb/s maximum). Is there already a solution to have my account connected to the European server in combination with the U400 doorlock. When received, a couple of months ago it wasn’t, hope there’s bin a solution in the meantime.
1 Like
Hi,
I would like to have a separate PIN setup so that I can use this to trigger my garage door to open, is there any functionally to achieve this via the current software or automations? Additionally a duress PIN code feature would be great too.
1 Like
I am on the latest firmware and am having issues with UWB unlocking being inconsistent. My door/installation seems fairly standard, and I currently have the following UWB options configured:
- All approaching directions enabled, since I can approach from either side
- UWB Distance: 1.6 m
- Sensing Time: 120s (increased from the 60s default)
- Signal Search Time: 10s (default)
The behavior is fairly repeatable.
If I walk approximately 20–25 ft away and immediately walk back, UWB generally works exactly as expected and unlocks the door before I can reach the handle.
However, if I walk away and remain away for a minute or longer, the lock frequently does not react as I approach. I can get all the way to the handle without the UWB indicator illuminating. If I then touch the keypad, the keypad lights up, approximately one second later the UWB indicator comes on, and approximately another second later the door unlocks.
Because of this behavior, I initially suspected that the lock or UWB subsystem may be entering some kind of sleep state and not waking quickly enough. I don’t get the impression that this is a loose/damaged UWB cable because when UWB does engage normally, its range appears to be very good.
I captured diagnostic logs while intentionally reproducing the issue. I am not particularly familiar with Aqara’s internal log format, so I uploaded the front-panel and back-panel logs to ChatGPT and asked it to compare successful and unsuccessful UWB sessions. I want to be transparent that the interpretation below comes from ChatGPT’s analysis of those logs rather than my own understanding of the firmware.
The most interesting sequence ChatGPT identified occurred around 16:12:
- ~16:12:02:
Aliro BLE L2CAP Opened - Aliro authentication/exchange completes
- ~16:12:03: a UWB session/task is created
- ~16:12:28:
Initiate_Ranging_Session - ~16:12:30:
UWB_SESSION_STATE_ACTIVE - The first useful range measurement is approximately 690 mm
- The reader triggers and the door begins unlocking almost immediately afterward
So according to ChatGPT’s interpretation, there appears to be roughly a 25-second gap between the UWB task being created and actual UWB ranging being initiated. Once ranging starts, positioning and unlocking happen very quickly.
ChatGPT also identified another interesting sequence around 16:53. In that case:
- Aliro BLE opens
- Authentication/exchange completes
- A UWB session/task is created
Initiate_Ranging_Sessionapparently never occurs- The Aliro connection eventually closes
- The UWB session is terminated while still showing
UWB_SESSION_STATE_UNINIT
There are also successful sessions in the same logs where the UWB task is created and ranging begins almost immediately, so this delay does not appear to happen consistently.
The logs contained another useful comparison that ChatGPT pointed out. During one successful approach, UWB was already actively tracking the credential from approximately 5.9 m away and continued measuring the approach through several intermediate distances before triggering the reader near the configured unlock distance. That seems to suggest the UWB hardware/range itself is capable of working very well when ranging starts early enough.
So the pattern ChatGPT sees in the logs seems to match what I am observing physically:
Successful case:
Aliro/credential detected → UWB ranging starts early → credential is tracked while approaching → door unlocks around the configured distance.
Problem case:
Aliro/credential communication appears to occur and a UWB task may already exist → ranging is delayed for many seconds or does not start → by the time UWB becomes active I am already at the door → it then unlocks very quickly.
I don’t know enough about the protocol to determine whether the U400 itself is responsible for that delay or whether it is waiting for some event/command from the Apple device. ChatGPT also noted that there is received data immediately before Initiate_Ranging_Session in the delayed example, so I don’t want to incorrectly conclude that the lock itself is definitely causing the pause.
But based on both the repeatable physical behavior and ChatGPT’s parsing of the logs, it seems like the interesting area for investigation may be between Aliro discovery/authentication and the point where actual UWB ranging is initiated, rather than the ranging performance itself.
I haven’t attached the full diagnostic logs to this post, but I have them available and would be happy to provide the front-panel/back-panel logs to the Aqara developers, along with exact timestamps from additional controlled tests if that would be useful.
2 Likes
Thank you very much for your detailed testing and feedback!
The current U400 is designed with a sleep mechanism to prevent accidental unlocking when users linger in front of the door. In our upcoming firmware update, we plan to add a new customizable option in the Aqara Home app. This will allow users to shorten the device sleep duration. While this brings a slight power consumption increase, it will greatly optimize the overall user experience.
We truly appreciate your in depth usage feedback. We will post the new firmware update announcement on our forum once it is ready.
3 Likes