If a Lockin Matter entity disappears from a home app, first determine whether the lock itself is missing, the Matter device is offline, or only one entity or dashboard card is hidden. Check the Lockin Smart App, the exact lock model, the home app’s device and entity registry, and the Matter controller or Thread network—in that order. Do not factory-reset a lock that still works locally just because one app no longer shows it.

Start with the Lockin Smart App

Open the Lockin Smart App and confirm that the lock is still listed and responds to a safe test, such as locking while the door is closed. Keep a mechanical key, administrator credential, or another configured local method available before changing connected-home settings.

Use the result to separate the problem:

Lockin’s FAQ directs owners to the device list for setup and identifies the Lockin Smart App as the place for full setup, settings, and device management. A Matter app is an additional control surface; it is not a replacement for the Lockin app’s model-specific controls.

Confirm that the exact model supports the Matter path

Matter support is model- and platform-dependent. Current Lockin documentation describes Matter integration for the Veno series with platforms such as Apple Home, Amazon Alexa, Google Home, and Samsung SmartThings. The controller or hub requirement can vary by platform and model. Lockin also says that Veno Pro does not support native HomeKit, while selected Veno models can integrate with Apple Home through Matter. That is not the same as Apple Home Key support.

Before repairing a missing entity, write down:

• The exact model name and firmware version shown in the Lockin Smart App.
• The home platform where the entity disappeared.
• Whether the connection is Wi-Fi Matter or Matter over Thread, if the product documentation identifies it.
• Which controller, hub, or Thread border router the platform uses.
• Whether the Lockin app still shows current battery and connection information.

This prevents a common mistake: trying to restore an entity through a first-pairing flow when the real issue is a platform-specific controller or feature boundary.

Search the home app before removing anything

An entity can disappear from a dashboard without being removed from the underlying device. Search the home app’s full device list, then check the assigned home, room, favorites, filters, hidden devices, and disabled entities. Search by the model name as well as the custom name—for example, “Veno,” “front door,” or “Lockin.”

If the Matter device is still present but the lock control is missing, open the device details and inspect its entities. A renamed entity, disabled entity, or changed room is a presentation or registry problem, not proof that the Matter pairing is gone. Re-add the entity to the dashboard only after confirming the device record and the intended household account.

For Home Assistant, open Settings → Devices & services → Matter, select the device, and inspect its entities and diagnostics. Home Assistant’s Matter documentation also distinguishes adding a new device from adding a device that is already in use by another Matter controller. Use the latter flow when the lock is still paired elsewhere; do not scan the original commissioning code as though the lock were new.

Check power, Wi-Fi, Thread, and local-network discovery

If the Matter device record exists but shows unavailable, check the transport layer before deleting the device:

1. Check the lock’s battery and confirm that local entry still works. Recharge or replace power as the exact model requires.
2. If the model uses Wi-Fi for the relevant service, check the router, the 2.4 GHz network, the SSID, and signal at the door. Lockin’s current FAQ calls out 2.4 GHz conditions for the Veno video series and recommends adequate battery before troubleshooting app connectivity.
3. If the Matter path uses Thread, confirm that the intended Thread border router or Matter controller is powered, online, and associated with the same home. Do not assume that a controller in another household or account can serve this one.
4. Check that the home platform’s Matter integration is installed and current. Home Assistant’s official Matter documentation identifies IPv6 and mDNS or multicast traffic as important to local Matter discovery and communication; VLANs, multicast filtering, or IGMP problems can interrupt that path.
5. Restart the affected controller or Matter service once, then recheck the existing device record. A restart is a lower-risk test than removing the lock and commissioning it again.

The important distinction is between “the device is still known but unreachable” and “the device record is gone.” The recovery action is different for each.

If another app still sees the lock

When the Lockin Smart App or another Matter controller still sees and controls the lock, preserve that working connection. The missing home app may need a multi-admin or “already in use” handoff rather than a reset.

In the affected platform, look for labels such as Add already paired device, Previously paired, Share, or Add to another service. Home Assistant documents an already in use path for a Matter device connected to another controller. Use the current setup code or sharing flow supplied by the Lockin app or the existing Matter controller, and keep the original Lockin account in place.

After the handoff, test three things:

• The Lockin Smart App still displays the lock and can perform its supported control.
• The repaired home app shows the intended lock entity and performs the intended action.
• A native or physical backup entry method still works if the connected-home service is unavailable.

If the second app can display the lock but exposes fewer controls, treat that as a platform feature boundary until the exact model and current platform documentation say otherwise.

When re-pairing or resetting is justified

Re-pair only after you have confirmed that the device is gone from the intended controller, the model and controller requirements are correct, and the platform’s existing-pairing recovery path has failed. Save the current setup code and record which app still owns the lock before changing anything.

Factory reset is a last resort because it can remove the lock’s existing configuration and access credentials. Lockin’s FAQ describes different reset procedures for an unbound device and a bound Veno-series device; follow the current instructions for the exact model, not a generic Matter guide. Plan for local access and a complete Lockin Smart App setup before starting the reset.

If the lock does not appear in the Lockin Smart App, the home app, or the controller’s Matter device list after the documented recovery steps, stop repeated pairing attempts and contact Lockin support with the model, firmware, app versions, controller, error text, and diagnostics. Do not publish a new QR code or share a setup code publicly.

A safe recovery order

Use this order whenever a Lockin Matter entity disappears:

1. Keep a physical or native Lockin backup access method ready.
2. Check whether the Lockin Smart App can see and control the lock.
3. Search the home app’s device and entity registry, rooms, filters, and disabled items.
4. Verify the exact model, Matter support, controller, Thread border router, power, Wi-Fi, IPv6, and local discovery conditions.
5. Repair an existing Matter connection through the platform’s already-paired or sharing flow.
6. Restart the affected app, controller, or Matter service and collect diagnostics.
7. Re-pair or factory-reset only when the existing record is genuinely gone and the current Lockin instructions support that step.

For model-specific setup, use the Lockin FAQ, the Lockin user-manual library, and the Lockin app download page. For a broader connectivity checklist, see Lockin’s smart-lock 2.4 GHz Wi-Fi, remote-access, and Matter guide. Home Assistant users can compare the current Matter integration documentation before changing a working Lockin pairing.