If your Lockin Veno Solar Palm appears paired in a Matter controller but will not lock, unlock, or show a current state, check the controller’s local network path before changing Wi‑Fi bands or resetting the lock. Matter control depends on local IPv6 and multicast/mDNS traffic. A device can finish pairing and still become unreachable when the controller and lock are separated by a VLAN, guest network, multicast filter, or broken IPv6 path.
This guide is for a Veno Solar Palm that already appears in a Matter ecosystem. It helps you separate three different conditions: the lock itself still works locally, the Lockin Smart App can reach it, or the Matter controller cannot reach it. That distinction keeps troubleshooting focused and preserves your existing access methods.
What “paired but not responding” usually means
Matter pairing, sometimes called commissioning, is the process of adding a device to a controller. It is not the same as proving that the controller can continue to communicate with the lock. During commissioning, Bluetooth may help transfer network credentials; afterward, the device communicates through its native transport. Home Assistant’s Matter documentation describes this separation and identifies local IPv6 and mDNS/multicast as required parts of normal Matter communication.
For the Veno Solar Palm, Lockin documents Matter compatibility alongside built-in Wi‑Fi, app control, palm-vein entry, PIN, key, and voice-control options. The Lockin FAQ also says the Veno Solar Palm/Face family uses Matter over Thread for smart-home integration and that the Lockin Smart App remains the route for full functionality, troubleshooting, updates, and device management. Treat the controller path as one access layer—not as a replacement for native entry or the Lockin app.
First, identify which layer is failing
Use this short test matrix before changing router settings:
| Test | Result | What it tells you |
|---|---|---|
| Try palm, PIN, or the mechanical key at the door | Works | The lock and at least one local access path are functioning; the Matter controller path is the likely problem. |
| Open the lock in the Lockin Smart App while nearby | Works | The lock is responding through the Lockin path; investigate Matter controller reachability and network segmentation. |
| Lockin app also cannot reach the lock | Fails | Check the lock’s power, Wi‑Fi setup, signal, app state, and the exact Veno Solar troubleshooting guide before blaming Matter. |
| Matter controller shows the lock but commands time out | Fails | Pairing records exist, but local transport or controller state may be stale or blocked. |
Do not factory-reset a lock merely because the Matter tile is unavailable. A reset can erase device data and force you to rebuild access. Keep at least one working local method available while you diagnose.
Check the local IPv6 and multicast path
The most useful check for a Matter smart lock paired but not responding is whether local IPv6 and multicast traffic can travel between the Matter controller, its border router when applicable, and the lock’s network.
- Confirm the controller and lock are on the intended home network. Avoid testing from a guest SSID. If your router uses VLANs or separate IoT and main networks, verify that the controller and the Veno Solar Palm are allowed to exchange local Matter traffic. Home Assistant recommends keeping Matter devices and the controller on the same VLAN when troubleshooting.
- Enable IPv6 on the local network path. This does not mean you need an IPv6-enabled internet connection or a DHCPv6 server. The Home Assistant guidance specifically says IPv6 must be enabled on the Home Assistant host and that IPv6 multicast traffic must travel freely to it. Other controllers expose different settings, so use the controller maker’s current network documentation for its exact menu names.
- Review multicast and mDNS handling. Disable or revisit router and access-point features that filter, optimize, proxy, or suppress multicast traffic. Home Assistant notes that multicast filtering and malfunctioning IGMP snooping can interfere with Matter discovery and control. If you do not know which feature is responsible, test with the simplest flat home topology your equipment supports, then reintroduce segmentation one change at a time.
- Check the Thread border-router path if your setup uses Thread. Lockin’s Veno Solar Palm/Face FAQ describes Matter over Thread and lists ecosystem-specific border-router requirements. A Thread device needs a border router that connects the Thread network to the local IP network. If the border router is offline, isolated, or attached to a different network segment, the controller may retain a paired device record while commands fail.
- Restart only the network components that are safe to restart. Restart the controller or border router and, if needed, the access point/router according to their normal procedures. Then wait for the local network and Thread fabric to settle before testing a command. Do not delete the Matter fabric or reset the lock until the basic path checks are complete.
Why changing from 5 GHz to 2.4 GHz may not fix Matter
The Veno Solar Palm/Face troubleshooting PDF says the lock’s Wi‑Fi setup uses a visible 2.4 GHz SSID with WPA or WPA2 security. That matters when the Lockin Smart App is adding the lock to Wi‑Fi. It does not prove that a paired Matter controller can reach the lock.
So use the right test for the right layer:
| Symptom | Relevant next check |
|---|---|
| The Lockin app cannot complete Wi‑Fi setup | Confirm the visible 2.4 GHz SSID, WPA/WPA2 security, signal, power, and the Lockin troubleshooting steps. |
| The lock is already paired in Matter but controller commands fail | Check local IPv6, mDNS/multicast, VLAN/guest isolation, and the Thread border-router path. |
| Native palm/PIN/key entry works but the Matter tile is unavailable | Keep using native entry while repairing the controller transport; do not assume the lock hardware is dead. |
Re-test in a controlled order
After each network change, run the same small test rather than changing several variables together:
- Check whether the Veno Solar Palm responds to a native method at the door.
- Check whether the Lockin Smart App shows a current state or accepts a supported command.
- Check the Matter controller’s lock state, then send one lock or unlock command while you are present.
- Confirm the physical door and deadbolt moved as expected. A stale tile is not proof that the bolt changed.
- Record which change restored or failed control so you can reverse it safely.
If Matter works on a flat network but fails after you restore VLANs, guest isolation, multicast optimization, or firewall rules, the network policy is the leading suspect. Ask the router or controller manufacturer for the supported local Matter and IPv6/mDNS configuration rather than opening broad inbound internet access. Matter troubleshooting here is about local reachability; it is not a recommendation to expose the lock to the public internet.
When to use Lockin support or reset the integration
Use the Lockin FAQ and the Lockin user-manual page for the exact Veno Solar Palm/Face instructions, firmware path, and current platform conditions. The Veno Solar FAQ says a reset erases data, so treat reset as a last resort after you have recorded your current access methods and are prepared to pair and configure again.
Contact Lockin support when the lock cannot be reached in the Lockin Smart App after the documented power, signal, Wi‑Fi, cable, and pairing checks; when the lock behaves abnormally through native access; or when the exact model/firmware condition is unclear. For a Matter-only failure with native and app control working, also provide your controller platform, border-router model if used, whether the networks are segmented, and what changed immediately before the failure.
The practical answer
A Matter smart lock paired but not responding is often a controller-transport problem, not a failed pairing record and not automatically a 5 GHz problem. For a Lockin Veno Solar Palm, first prove that native entry and the Lockin Smart App still work. Then inspect local IPv6, mDNS/multicast, VLAN or guest isolation, and the Thread border-router path. Keep a local backup method available, make one network change at a time, and reset only when the documented Lockin process is the remaining supported route.
For the model’s current features and conditions, see the Lockin Veno Solar Palm product page. Use the product page, FAQ, and manual together: the controller can add convenient ecosystem control, while the Lockin Smart App and local access methods remain important for complete setup and dependable entry.
Sources and scope note
- Lockin Veno Solar Palm product page, checked September 14, 2026.
- Lockin FAQ, including Veno Solar Palm/Face Matter and troubleshooting links, checked September 14, 2026.
- Lockin User Manual page, checked September 14, 2026.
- Veno Solar Palm/Face FAQ & Troubleshoot PDF, version dated May 27, 2026, accessed September 14, 2026.
- Home Assistant Matter integration documentation, accessed September 14, 2026. This is protocol/network guidance, not proof of a Lockin-specific Home Assistant certification or integration.