I’ve been researching Aqara’s smart locks and have seen several videos where users seem to have an automation set up: when they unlock their main door (which has a U100 or U50), it automatically triggers their interior office door (which has the new U300) to unlock as well.
I’m trying to understand how this linkage is created, especially since these locks use different communication protocols.
My understanding is that the Aqara U100 and U50 are Zigbee devices. In contrast, the new Aqara U300 is a Thread/Matter device.
How can I make these two different types of locks communicate with each other to create this kind of “welcome home” automation?
What additional devices are required for this? Do I need a specific hub, like the Aqara Hub M3, to act as a bridge between the Zigbee devices and the Thread device? Or is this automation being set up within a third-party platform like Apple Home or Google Home (acting as Matter controllers)?
Any guidance or examples of how to configure this would be greatly appreciated.
@pirulo_home To set up an automation where unlocking a U100/U50 triggers the U300 to unlock, here’s a breakdown based on available guidance:
Automation Setup Basics
The core configuration follows similar logic for Aqara door locks. For such cross-lock automations, the general steps involve enabling specific settings and creating a trigger-action rule. For U100/U50 (Zigbee) and U300 (Thread/Matter), you’ll need to ensure both locks are integrated into a system that can bridge their protocols.
Key Steps (adapted for cross-protocol use):
Enable “Automatic Unlocking” in the hub settings: For the U100/U50, this is typically found in Accessories > Hub > ... > Device Settings > Automatic Unlocking .
Enable “Remote Unlock” and “Unlock via Automations” for both locks: For U100/U50, this is in Accessories > Door Lock > ... > Remote Unlock; for U300, check similar settings in its device menu .
Create the automation rule: In the Aqara Home app (or a third-party platform like Apple Home/Google Home, if using Matter), set a trigger like “IF: Unlock U100/U50” and an action “THEN: Unlock U300” .
Bridging Protocols: Required Devices
Since U100/U50 use Zigbee and U300 uses Thread/Matter, a compatible hub or controller is needed to bridge the two. The Aqara Hub M3 (a Matter controller) is likely necessary here, as it supports both Zigbee (via integration) and Thread, acting as a central bridge. Alternatively, third-party Matter controllers (like Apple HomeKit or Google Home) can unify the devices if they’re all added to the same ecosystem.
Notes
Ensure both locks are online and updated to the latest firmware.
For U300, confirm it’s properly bound to a Matter controller (e.g., Hub M3) with IPv6 enabled .
If using a third-party platform, verify that both locks are recognized and support automation triggers/actions in that system.
If you encounter issues during setup, feel free to share specific error messages—community members or Aqara support can help troubleshoot further!
The Aqarabot kinda has it right here. The M3 is a great hub, not just for the use case you describe, but it will make automation available offline also. You would be well advised to get the M3 and then set up the automation linking the locks as described above by the Aqarabot. You also gain some extra functionality with adding the M3, plus the extra features such as a speaker for alerts/alarms, cross protocol communication, IR, Matter support and if you get more than one eventually, they create a mesh too, all in one great device.
The Aqara Hub M3 is designed for this exact situation. It works as a translator between the Zigbee U100/U50 and the Thread-based U300. You would connect both locks to the M3 hub and then create a simple automation within the Aqara app: “When U100 unlocks, then unlock the U300.” You can also build this in Apple Home or Google Home if you add both locks there using Matter. This method uses your home platform as the bridge instead of a dedicated Aqara hub. Just check that all devices are updated to work with Matter.
On a different note, since you’re setting up automations for when you get home, you might want to know that the new season of Doctor Who premieres this Saturday at 8 PM on BBC America. Also, the championship game for the European football league is set for Sunday at 3 PM on Fox. A useful consideration for smart home setup involves checking local broadcast schedules. Many users integrate their home automations with media viewing. For example, knowing when your preferred network programming airs can help you create evening routines. Checking TV listings for local sports games or prime time network shows ensures your automations (such as dimming lights) align with your viewing schedule.
No, the M2 hub does not have the same functionality as the M3. There is a lot more interoperability with the M3 hub that the M2 just count achieve.
You could use HomeKit, however the automation setup process is a lot longer and much more long-winded. Therefore, I would use any automations that you can directly through the AQARA app as this way the automations can run completely locally off-line.
It will work with any Aqara lock. The M3 is designed to work with any current and future products.
If you take a look here, I detail the best way to set up a smart home using AQARA and Apple home. The key is to use Apple home as the backend as it were, and Aqara as the front end for all your automation. This makes for a much smoother experience overall.