A phone can now help onboard a lock, carry the door credential, unlock the door, and let an owner remove that credential if the phone goes missing. That sounds like one feature. It is actually several systems stacked on top of one another.

The practical shift behind Samsung SmartThings adopting Aliro is not simply that a Galaxy phone can become a house key. It is that buyers now need to evaluate two separate compatibility layers: Matter for smart-home command and control, and Aliro for the credential exchanged between a phone or wearable and the lock. A badge on the box is useful, but it does not prove that your exact phone, wallet, lock model, region, radio mode, household setup, and fallback plan all work together.

1. Matter runs the lock; Aliro carries the key

Samsung's Digital Home Key announcement makes the division unusually clear. Samsung says a compatible lock is first set up in SmartThings using Matter. The user can then add a Digital Home Key to Samsung Wallet during onboarding. Depending on the phone and lock, entry may use NFC for tap-to-unlock or UWB for hands-free proximity; Samsung also describes remote unlocking through the app.

Allegion's Aliro 1.0 overview describes Aliro as the standardized mobile credential and device-to-reader protocol linking trusted phones and wearables with locks and readers. Read beside Samsung's Matter-based SmartThings setup, the architecture is clear: the smart-home control relationship and the mobile door credential are separate compatibility questions, even when one onboarding flow makes them feel unified.

That distinction changes the buying question. “Works with SmartThings” does not necessarily tell you which wallet can hold the key. “Aliro-ready” does not necessarily tell you whether the lock exposes the routines, state, notifications, and remote controls you want in Apple Home, Google Home, Alexa, Home Assistant, or SmartThings.

2. Compatibility is now a matrix, not a logo

Before buying, check four rows independently.

The exact lock model. Certification and support attach to particular hardware and firmware, not an entire brand. Samsung says Digital Home Key compatibility can vary by model and region, with partner rollouts following their own schedules. A product-family logo or a retailer's broad compatibility claim is not enough.

The exact phone and wallet. NFC and UWB are different entry paths. Samsung limits NFC and UWB support to selected devices and notes that availability expands by region and partner timing. A household with mixed Galaxy phones, iPhones, watches, and older devices needs a per-person check, not a platform-level assumption.

The smart-home controller. Matter support still depends on the controller and network architecture required by the lock. It governs how the lock participates in routines and remote control; it does not make every wallet credential portable across every ecosystem.

The administration path. The owner needs to know where residents, guests, revoked phones, and lost-device recovery are managed. Samsung says its keys are stored in Samsung Wallet and that access can be managed or removed with Samsung Find, with biometric or PIN authentication protecting key management. Buyers should still verify what happens for non-Samsung household members and which controls remain in the lock maker's app.

3. “Ready” and “supported” are not the same promise

Aqara's January Smart Lock U400 announcement is a useful example of why wording matters. Aqara called the lock Matter-certified and Aliro-ready. The release documented Apple Home Key use, Matter-over-Thread integration, and several physical and digital fallback methods. It also pointed to Samsung Wallet support on a future timetable.

That is not a reason to distrust the product. It is a reason to read the tense. “Certified,” “compatible,” “ready,” “planned,” and “rolling out” describe different states. If phone-as-key is the reason you are buying, require a current support page for the exact lock, phone, wallet, country, and unlock mode before treating it as delivered.

The same caution applies to hands-free entry. UWB can provide more precise direction and distance than ordinary proximity detection, but it only helps when both ends of the system and the current software path support it. Otherwise the practical mode may be NFC tap, an app action, a keypad, or a mechanical key.

4. A smart lock needs a recovery design, not just a happy path

The front door is a poor place to discover that the “interoperable” experience assumed a charged phone, a particular resident's account, or an online service. The better products expose several independent ways home.

Aqara lists fingerprint, passcode, NFC card, app, voice-assistant, and mechanical-key options alongside wallet access for the U400. Those options are product-specific, but the broader lesson travels: choose at least one fallback that does not share the primary credential's failure mode. If the primary path is a phone wallet, a keypad or physical key is meaningfully different; a second app on the same dead phone is not.

Power recovery matters too. Ask how the lock warns about a low battery, what powers it temporarily from outside, and whether the physical cylinder remains usable. Then test those paths before the first real lockout. A standard can improve interoperability without replacing basic door-hardware discipline.

Builder/Engineer Lens

Treat smart access as three planes.

Credential plane: Who is allowed through, which wallet or device holds that authority, and how is it revoked? Aliro is aimed here.

Control plane: Can the home report lock state, issue remote commands, provision users, and trigger routines? Matter and the chosen controller operate here.

Recovery plane: What works when the phone, battery, network, account, hub, or cloud path fails? Keypads, physical keys, external power, local administration, and tested household procedures live here.

A robust installation does not collapse those planes into one vendor account. It also avoids dangerous automation shortcuts. An “arrive home” routine can turn on lights after an authorized unlock, but disarming alarms or opening secondary doors deserves narrower conditions and a review of who can issue the triggering credential. Convenience should follow authentication, not substitute for it.

For builders and tinkerers, log the exact model, firmware, controller, border router if required, wallet, supported transport, resident roles, and recovery method. That small compatibility record is more useful than remembering that the box once carried two logos.

What to verify before checkout

1. Model and region: Find the manufacturer's current support page for the exact SKU and country. 2. Wallet and phone: Confirm whether each resident gets NFC tap, UWB hands-free entry, app-only control, or no wallet support. 3. Matter behavior: List the controls and state exposed to your chosen platform; do not assume advanced lock features cross ecosystems. 4. Guest and lost-phone handling: Identify who issues, expires, and revokes credentials and where that administration happens. 5. Independent fallback: Keep and test a keypad, physical key, or other path that survives a dead phone and network outage. 6. Power recovery: Verify low-battery warnings, external emergency power, battery replacement, and manual access before installation day.

The takeaway

Aliro can remove a real layer of mobile-key fragmentation, and Samsung's implementation shows how it can sit beside Matter rather than replace it. That is progress. It also makes vague compatibility shopping less defensible.

Buy a smart lock only after the credential plane, control plane, and recovery plane all fit your household. The best phone-as-key system is not the one with the most impressive unlock demo. It is the one every authorized resident can use—and the one you can still recover when the demo conditions disappear.