Prepared by the Dwellwise Picks editorial deskUpdated July 2, 2026
Quick answer
The practical answer
A product family can include Wi-Fi, Bluetooth, HomeKit, Matter, or Thread versions. Match the ASIN, model label, and selected retailer option before planning controllers.
A product family can include Wi-Fi, Bluetooth, HomeKit, Matter, or Thread versions. Match the ASIN, model label, and selected retailer option before planning controllers.
Name the Matter controller and border router
Write down the actual compatible device that will commission the lock and connect the Thread mesh. A Matter logo does not mean the lock operates without infrastructure.
Plan the first ecosystem and sharing
Multi-admin support can share a Matter device with another ecosystem, but the commissioning and sharing flow still matters. Decide which platform owns the first setup.
Preserve local entry
Enroll fingerprints and codes carefully, keep a physical-key or documented fallback available outside, and test low-battery behavior before depending on remote control.
Confirm the exact lock, doorbell, thermostat, controller, and ecosystem versions before buying.
Check what remains available locally when Wi-Fi, cloud service, or a subscription is unavailable.
Map wiring, door dimensions, radio coverage, storage, and household access before installation.
Common mistakes
Treating Matter, Thread, Zigbee, Wi-Fi, and Bluetooth as interchangeable labels.
Buying an ecosystem feature before confirming the required hub, controller, or border router.
Ignoring subscription boundaries, batteries, replacement access, and emergency fallback controls.
Category checks
Measure the door and existing deadbolt before comparing unlock methods.
Keep at least one dependable local fallback entry method.
Confirm which hub or controller unlocks remote and cross-platform features.
Decision rule
Choose the device with the clearest compatibility and local fallback path; add premium ecosystem features only when they remove a recurring household problem.