If your Lockin smart lock works sometimes and fails at other times, send Support a focused fault report rather than a general description. Include the exact lock model, app and firmware versions, power state, the access path that works and the one that fails, timestamps, what changed, and a redacted network sketch. That gives Lockin a reproducible support handoff without exposing your PIN, biometric data, account token, or Wi-Fi password.
This workflow is especially useful for a Lockin Veno Pro installation. The Veno Pro combines palm-vein, fingerprint, PIN, mechanical-key, app, and voice access with a camera, alerts, and Matter-based smart-home connections. A fault in one path does not automatically mean the lock hardware is failing.
Start with the exact lock and the symptom pattern
Write down the name printed on the product page, box, or device screen. Do not report a Veno Pro issue simply as “my Veno” if you have a Veno Plus, Veno, Veno Go, Veno Solar Palm, or another model. The supported access methods, camera behavior, power system, and setup conditions can differ.
Describe the fault in one sentence using this format:
On [date/time and time zone], [access method or feature] failed [number] times, while [known-working method] still worked; the lock/app showed [exact message or light/sound pattern].
Then record:
- Model and hardware: exact model, bundle or accessory involved, and whether the exterior or interior assembly is affected.
-
Software: Lockin Smart App version, lock firmware version, and phone operating-system version. The FAQ places firmware updates in
Devices → Live screen setting → Device information → Firmware Version Upgrade; check the current version without guessing. - Power: approximate battery level, whether a charge or battery change preceded the issue, and whether the lock works from a temporary emergency power source or mechanical key. Do not keep testing if the door cannot be secured safely.
- Location and conditions: indoor or outdoor side of the door, rain or condensation, unusual temperature, direct sun, recent installation work, or a door that has become harder to close.
Separate the working path from the failing path
Intermittent smart-lock troubleshooting becomes much clearer when each access path is tested and recorded separately. For a Veno Pro, make a small matrix like this:
| Path or feature | Result | Attempts | Time of last test | Exact response |
|---|---|---|---|---|
| Palm-vein recognition | Works / fails | |||
| Fingerprint | Works / fails | |||
| PIN | Works / fails | |||
| Mechanical key | Works / fails | |||
| Lockin Smart App nearby | Works / fails | |||
| Remote app control | Works / fails | |||
| Camera or live view | Works / fails | |||
| Activity log or alert | Works / fails |
Use a small, repeatable test: keep the door open while checking whether the latch moves smoothly, then test the same path with the door closed if it is safe to do so. Note whether the problem follows the user, the phone, the access method, the door position, or the time of day. Do not factory-reset the lock before Support has reviewed the evidence; a reset can remove useful context and access setup.
Check the physical and power context
Tell Support whether the latch extends and retracts smoothly by hand and with the interior thumbturn. Note rubbing, wobble, a loose mounting plate, a misaligned strike plate, or a door that must be pushed or pulled for the deadbolt to move. Lockin’s FAQ says correct Veno-series installation includes a smooth latch, rigid hardware, working palm-vein, fingerprint and password functions, stable Wi-Fi, remote lock/unlock, and camera activity where applicable.
If auto-lock is the problem, report whether the door-status cable was pinched during installation and whether the strike-plate sensor aligns with the deadbolt sensor. Those are specific installation conditions Lockin identifies as causes of abnormal automatic locking.
For power-related failures, report the battery percentage shown in the app, the date of the last full charge, the cable/charger change if any, and whether low-battery alerts arrived. The Veno Pro page describes a removable rechargeable battery, low-battery alerts, and backup entry using a key or power bank. Treat “works after charging” as evidence about the power path, not proof that every intermittent fault is a bad battery.
Record the app, Wi-Fi, and smart-home boundary
Draw a simple, redacted map:
Phone ── Lockin Smart App ── home router ── internet
└──── Matter controller / Thread border router (if used)
Lockin Veno Pro ── local Bluetooth / Wi-Fi / Matter path as applicable
Mark what changed: router, SSID, password, mesh node, VLAN or guest network, Matter controller, phone, app, or firmware. Write “2.4 GHz” or “5 GHz” only if you have verified the band. Lockin’s FAQ says Veno Pro does not support 5 GHz networks and identifies 2.4 GHz setup conditions; do not infer that a remote-app problem and a palm-recognition problem have the same cause.
If Matter is involved, say which controller and whether the Lockin Smart App, native entry, or another smart-home control still works. The Veno Pro product page describes Matter connections to Apple Home, Amazon Alexa, Google Home, and Samsung SmartThings. The FAQ separately says Veno Pro does not support native HomeKit, while Veno-series products can integrate with Apple Home through Matter. That distinction helps Support isolate an app, controller, network, or lock issue.
Include useful evidence, but redact secrets
Attach only evidence that answers a diagnostic question:
- a short video showing the failed action and the exact light, sound, or on-screen message;
- a screenshot of the device model, firmware/app version, battery state, or relevant log entry;
- timestamps with the time zone and the number of successful versus failed attempts;
- order number or proof of purchase if Support asks for warranty help;
- a redacted network sketch showing device roles, not credentials.
Never place any of these in a public worksheet or ordinary email attachment: a live PIN, administrator password, fingerprint or palm-vein file, account token, Wi-Fi password, recovery code, or an unredacted QR code. If Support needs a sensitive item, first confirm the private channel and the exact purpose. A screenshot can reveal more than the field you intended to share.
Use a compact support handoff
Copy this template into a private Support request:
Subject: Intermittent [model] fault — [feature] fails while [feature] works
Model / bundle:
Country or region:
Installation date (approximate):
Lockin Smart App version:
Lock firmware version:
Phone model and OS:
Battery level and last charge:
First noticed (date, time, time zone):
Frequency and reproduction steps:
Working paths:
Failing paths:
Exact message / light / sound:
Door and latch observations:
Recent changes (router, phone, app, firmware, battery, installation, weather):
Matter/controller details, if relevant:
Attachments included:
Sensitive information removed: yes
Requested next step:
Ask for the next diagnostic step, not an immediate replacement or a promise that one component is at fault. If the lock is unsafe to operate, cannot secure the door, or shows signs of heat or battery damage, stop using it and state that clearly in the request.
Where to send the report
Start with the Lockin FAQ for the model-specific troubleshooting documents and setup checks. The Veno Pro product page identifies the model’s supported paths and emergency power options, and the Lockin user-manual library links to the Veno Pro manual. For direct help, use Lockin Contact Us and verify the current private support channel before sending attachments. The US contact page currently lists support@lockin.com and a customer-service hotline.
If you are deciding whether a Veno Pro fits your door, resolve that separately with the product page and installation guidance. A diagnostic report can explain an intermittent fault; it cannot confirm compatibility with every door, storm-door arrangement, latch, network, or regional configuration.
The short answer
The most valuable information for Lockin Support is a dated, reproducible comparison: exact model; app and firmware; power state; working versus failing access path; door, weather, and installation context; recent network or hardware changes; exact messages; and redacted evidence. That is enough to begin a useful manufacturer support handoff while keeping your credentials and biometric information private.
















