Smart Home Products & Project Support in Canada & US | SmartAccess ·
The voice assistant is the same; the lock connection may be different
Identify the actual smart-lock integration before applying a platform’s command or security limitation to it.
Two households use the same voice assistant but report different smart-lock behaviour. Before assuming one lock is defective, identify how each lock is connected. The device, manufacturer's app and platform integration together matter more than the assistant's name alone.
Schlage's Encode Plus integration page describes Google Assistant compatibility through the Schlage Home app. Google's Matter documentation separately describes restrictions for Matter door locks in its ecosystem. A statement about the Matter path should not automatically be applied to a different integration just because both involve Google.
Make a short connection record for the actual household. Name the exact lock, the manufacturer's app used, the platform connection and the command being considered. If the route is unknown, mark it unknown and ask the relevant support team. Do not label a device Matter-enabled from a familiar product name or the appearance of its app tile.
Read the support statement for the actual path. Keep basic compatibility separate from particular commands, remote behaviour and any security requirements. A page saying a lock works with an assistant does not answer every question about setup or authorisation, and a rule for another connection does not establish the answer either.
Before enabling an access-related feature, follow the manufacturer's and platform's current instructions and preserve ordinary access arrangements. Do not weaken a protection merely to make a demonstration command succeed. If documentation appears inconsistent, ask support about the exact model and route rather than experimenting with security settings without understanding them.
Describe a check precisely if one is performed: the command, application path and observed result. One successful local command does not establish every away-from-home function. Likewise, a failed command on one integration does not prove that all control routes for the lock are unavailable.
Use the shop to compare access products after deciding the needed behaviour and supported connection. A hub purchase cannot be justified solely by two users reporting different results. The useful comparison starts with the actual integration and its requirements, so the household buys for a defined capability rather than a shared platform logo.
Sources and further reading
- Schlage Encode Plus Works With | Find Integrations · Read 2026-11-10
- Supported device types | Matter | Google Home Developers · Read 2026-11-11
This is general information. Check the relevant authority or manufacturer for the rules, compatibility and terms that apply to your situation.
More practical guides