| Bluetooth Low Energy 5.4 | Wireless connectivity | Approximately 10–30 m in a typical home; walls, metal doors, and interference can reduce this considerably. | Usually a direct phone-to-lock connection. A compatible gateway can provide remote access. | Very low | No, when used locally with a phone; yes, for remote control through a gateway. | Fast local unlocking with a nearby phone or authorized accessory. | Battery-powered locks where long battery life and simple local access are priorities. | Direct remote access is not built in. Bluetooth range is strongly affected by building materials and phone placement. |
| Wi‑Fi 2.4 GHz | Wireless networking | Approximately 30–50 m indoors under favorable conditions; the practical range depends on the access point, walls, and congestion. | Connects directly to a home network and can use the local network or cloud services. | High compared with Bluetooth Low Energy and Thread; frequent battery replacement is common in continuously connected designs. | Usually yes for remote features; local operation may continue if the home network remains available. | Convenient remote access without a separate lock hub, subject to network availability. | Homes with permanent power, frequent remote access, or an existing strong 2.4 GHz network near the door. | Higher energy use can shorten battery life, and weak Wi‑Fi at the entrance can cause delays or disconnections. |
| Thread | Low-power IPv6 mesh networking | Approximately 10–30 m per radio hop indoors; multiple powered devices can extend coverage through the mesh. | Self-healing mesh network using border routers to connect the Thread network with other IP networks. | Low | Not necessarily for local control; remote access normally requires a border router and an internet-connected home network. | Reliable local control when the mesh is properly formed; coverage can improve as compatible powered devices are added. | Modern smart homes seeking low power, better whole-home coverage, and scalable local automation. | A lock needs a suitable Thread border router and compatible control ecosystem; a single Thread device does not automatically create a strong mesh. |
| Matter over Thread | Application standard using Thread as the radio network | Uses Thread’s approximately 10–30 m per-hop indoor range; overall coverage depends on the mesh and border-router placement. | Standardized device interoperability over a local IP network; Thread provides the transport. | Low | Not required for local control; remote access depends on the home’s Matter controller, border router, and internet connection. | Consistent local control across compatible platforms, with setup and performance dependent on the controller. | Battery locks that need low power plus multi-platform smart-home compatibility. | Matter does not increase radio range or battery life by itself. Thread coverage and controller support remain essential. |
| Matter over Wi‑Fi | Application standard using Wi‑Fi as the radio network | Uses the home Wi‑Fi network, typically approximately 30–50 m indoors under favorable conditions. | Uses the existing IP network; device behavior depends on Wi‑Fi coverage and the Matter controller. | High for battery-powered locks compared with Matter over Thread; more suitable for mains-powered equipment. | Not required for local control, but normally required for remote access and cloud-connected features. | Broad controller compatibility when certified and configured correctly; performance follows the Wi‑Fi network. | Powered access-control hardware or locations with excellent Wi‑Fi and limited need for battery operation. | Matter is an application standard, not a radio. Using Matter over Wi‑Fi does not provide Thread-level energy efficiency. |
