I owned my U200 for over a year before I could use it as a smart lock. Here’s what I’d tell a beginner. StarterTips
I bought an Aqara Hub M3 and a Smart Lock U200 with keypad without understanding two things: that Matter needs IPv6 on your local network, and that remote access depends on a working Matter controller path. For more than a year, that lock was an expensive way to lock my door by hand at the door. Fingerprint and keypad worked. Everything that made me want a smart lock didn’t.
The one thing I got right from day one — a dedicated IoT network.
When I set up my UniFi network, I created a separate network for all my smart devices rather than dropping them onto the same one as my laptops and phones. I’d recommend that to anyone starting out. Smart home gear is a mixed bag security-wise, it generates a lot of chatter, and keeping it separate means one flaky device can’t cause problems elsewhere. It also makes troubleshooting far easier — when something breaks, you know exactly where to look.
One thing to know if you do this: whichever network your smart devices live on is the one that needs IPv6 enabled, and your phone needs to be on that same network while you’re pairing anything over Matter. Segmenting is the right call, but it does mean being deliberate about which network you’re on when you set things up.
Tip 1 — Matter needs IPv6 on your local network, even if your internet provider doesn’t offer it.
This is the one that cost me the year.
I’m on Bell, which doesn’t provide IPv6 on residential lines. I assumed that was the end of it. It isn’t. Matter only needs IPv6 locally, between your own devices — your internet connection isn’t involved.
UniFi leaves IPv6 off by default. Enabling it on my IoT network unlocked two things at once: remote access to the U200 through the Aqara Home app, and the ability to connect my devices to Google Home. No error message anywhere had ever pointed at this.
If you’re on a provider-supplied router, this is usually handled for you. If you’ve built your own network and your Aqara devices won’t work remotely or won’t share out, check this first.
Tip 2 — the M3’s Matter bridge doesn’t pass your lock through.
Connect the M3 to another platform and it shares Zigbee and IR devices. Your lock isn’t one of them, so only the hub appears on the other end.
The U200 is its own Matter-over-Thread device and has to be shared directly. In the Aqara Home app, open the lock’s page — not the hub’s — and generate a new pairing code there. The QR code printed on the lock won’t work: that’s the factory code, valid only on a device that’s never been paired. Once your lock lives in Aqara Home, every additional platform needs a freshly generated code.
Tip 3 — research what you want the lock to do before you buy, not after.
Once IPv6 was sorted, I finally worked out what I actually wanted and what it would take. That research should have come first.
Where it left me: I still can’t set up a Samsung Wallet digital key, because that needs Aliro hardware the U200 doesn’t have — it’s a U400 feature, and no firmware update changes it. I also spent an evening failing to add the lock to Samsung SmartThings before discovering the SmartThings hub built into my Samsung TV has no Thread radio at all. Half my “network problems” were hardware limits I could have checked in two minutes.
One honest gripe: calibration. Mine drifts and needs redoing on a regular cadence. If yours starts reporting the wrong state or missing a turn, recalibrate before assuming something worse.
Where I landed: the U200 running through Aqara Home and Google Home, remote access finally working, and I can lock and unlock from my Galaxy Watch through Google Home on Wear OS. Not the setup I imagined when I bought it, but genuinely useful now.
If you’re about to buy your first Aqara device: segment your smart devices onto their own network, make sure that network has IPv6, and check what your other platforms’ hubs can actually talk to.