Matter Smart Lock Not Responding to App or Voice Commands

Problem Description

Your Matter-certified smart lock shows as connected in your controller app but does not respond to lock or unlock commands sent from the app, Siri, Google Assistant, or Alexa. The lock responds normally to the physical keypad and works when physically present, but remote and voice commands fail silently or return an error. Matter lock unresponsiveness is almost always a Thread connectivity issue — locks use Thread rather than WiFi, and Thread mesh gaps cause command delivery failures that look identical to a hardware problem.

Symptoms

• Lock shows online in controller app but lock and unlock commands produce no response
• Voice commands to lock or unlock fail with device not responding error
• Lock responds at close range but fails when commanded from another room or remotely
• Lock status updates are stale — app shows locked when lock is actually open
• Lock responds to some commands but not others, with no consistent pattern

Recognize these? Here's what usually causes it.

Common Causes

• Thread border router is too far from the lock, causing unreliable mesh path
• Lock battery is below the threshold needed to maintain Thread radio communication
• Controller hub lost the device's fabric entry after an update
• Thread mesh has too few repeater nodes for the lock's location in the home
• Lock firmware update changed the Thread network configuration

Tools & Requirements

Step-by-Step Solution

1

Replace Lock Batteries Immediately

Smart lock Thread radios are power-hungry and are the first function to degrade as battery voltage drops. A lock can operate its physical motor and keypad on lower battery voltage but lose its Thread radio connection before the low battery indicator triggers. Replace all batteries with fresh name-brand alkaline AA or AAA batteries — do not use rechargeable batteries, which run at 1.2V versus the required 1.5V per cell. After replacement, wait 60 seconds for the Thread radio to re-register on the mesh, then test a remote command from the controller app.

Needed for this step

Energizer Ultimate Lithium AA Batteries, Long L...

$83.98

Get It on Amazon

2

Check Thread Mesh Coverage at the Lock Location

Matter smart locks use Thread for communication, not WiFi. Thread has a range of approximately 30 to 50 feet indoors, but walls, metal doors, and concrete reduce this significantly. The lock needs a reliable path to a Thread border router — Apple TV 4K 3rd gen, HomePod mini, HomePod 2nd gen, Amazon Echo 4th gen or later, or Google Nest Hub 2nd gen. Check the distance and obstacles between the lock and the nearest border router. If the lock is on an exterior door far from interior hubs, add a Thread border router device in the room adjacent to the lock.

Needed for this step

Door Latch Strike Plate, Stainless Steel Door L...

$7.49

Get It on Amazon

3

Check Thread Network Status in Your Hub App

Apple Home shows Thread network status under Home Settings then Home Hubs and Bridges — look for your border routers and confirm they show as Connected. Google Home shows Thread status under Settings then Matter and Thread. If any border router shows as Offline or Not Connected, that border router is not contributing to the Thread mesh and may be the missing link for your lock. Bring an offline border router back online before expecting the lock to reconnect. Amazon Alexa does not expose Thread network status directly — use the Alexa app to confirm your Echo hub is online.

4

Power Cycle the Controller Hub and Wait for Thread Mesh Rebuild

A stale Matter hub state can cause commands to be sent to a device address that is no longer valid on the Thread mesh. Unplug your primary Matter controller hub — Apple TV, HomePod, Echo, or Google Nest Hub — for 30 seconds. Plug it back in and wait 3 to 5 minutes for the Thread mesh to fully reconstruct before testing the lock. Thread mesh rebuilding takes longer than WiFi reconnection because each border router must rediscover its neighboring devices and rebuild routing tables. Attempting to command the lock before rebuild completes produces the same not responding error.

5

Re-Commission the Lock If Hub Fabric Keys Were Lost

After a hub replacement, factory reset, or certain firmware updates, the Matter controller may regenerate its fabric credentials. Devices commissioned to the old fabric become permanently unreachable and show as not responding with no path to recovery other than re-commissioning. Factory reset the lock using the procedure in your lock manual — typically a button sequence while powered. After the reset, re-add the lock to your controller app by scanning its Matter QR code. Restore any access codes and automations after re-commissioning is confirmed.

Quick Solutions

Still having issues? This is usually the deeper cause below.