Lockin Home Assistant Unlock Confirmation: Add a Safer Button

If your Lockin Veno Pro is already paired with Home Assistant through Matter, a Lockin Home Assistant unlock confirmation can be added to the button card’s unlock action. Use a standard Button card, call lock.unlock, target the one exact Lockin lock entity, and add a confirmation object to the tap action.

This extra step helps prevent an accidental tap from sending the unlock command. It does not replace a Home Assistant login, a Lockin access code, or another authentication method.

Before you start

This walkthrough assumes that:

• Your Lockin Veno Pro is already operating as a responsive lock entity in Home Assistant.
• Home Assistant is already controlling the lock through a functioning Matter setup. Home Assistant documents itself as a Matter controller; this article does not claim that every Lockin model or firmware version has the same integration behavior.
• You have permission to edit the dashboard and test the lock.
• You know the actual entity ID for the door. Replace the example lock.lockin_front_door below with the entity ID shown in your own Home Assistant instance.

Lockin lists Veno Pro with Matter connectivity via Thread and identifies it as a video smart lock with palm-vein, fingerprint, PIN, key, and app access. The Home Assistant connection and the button behavior still depend on the model, firmware, controller, and configuration you are actually using.

The Button card YAML

In a manually managed dashboard, use a Button card like this:

type: button
name: Unlock front door
icon: mdi:lock-open-outline
entity: lock.lockin_front_door
show_state: true
tap_action:
  action: perform-action
  perform_action: lock.unlock
  target:
    entity_id: lock.lockin_front_door
  confirmation:
    title: Unlock front door?
    text: Confirm that you want to send the unlock command.
    confirm_text: Unlock
    dismiss_text: Cancel
hold_action:
  action: none
double_tap_action:
  action: none

The entity ID appears twice on purpose: once for the card’s displayed state and once as the action target. Keep the action target as one exact lock entity. Do not substitute an area, floor, label, or device unless you intentionally want Home Assistant to run the action against every matching lock in that target.

If your integration requires an unlock code, Home Assistant supports a code value in the action data. Do not paste a real code into a shared article, screenshot, or public dashboard configuration. Check the integration and your Lockin setup before deciding whether a code is required.

Add it from the dashboard editor

If you prefer the visual editor:

1. Open the dashboard you manage and choose Edit dashboard.
2. Add a standard Button card, or edit the existing Lockin lock button.
3. Select the actual Lockin lock entity. Confirm that the displayed state belongs to the intended door.
4. Set the tap action to Perform action.
5. Choose lock.unlock as the action and select the same, exact entity under Target.
6. Turn on the action’s Confirmation option.
7. Give the dialog a specific title such as Unlock front door? and use a clear confirmation button such as Unlock.
8. Set hold and double-tap actions to None if you do not want another gesture to operate the lock.
9. Save the card and test it while you are physically able to secure the door again.

The confirmation belongs to this card action. It is not a lock PIN, a server-side access rule, or a control that automatically protects unlock commands in other dashboards, automations, scripts, native apps, or voice assistants.

Test cancel and confirm separately

Test both paths instead of assuming that the dialog is enough:

1. Start with the door in a known, safe state and keep your physical key or the supported emergency method available.
2. Tap the button once. Check that the dialog names the intended door.
3. Choose Cancel or dismiss the dialog. Confirm that the lock did not change state.
4. Repeat the test and choose Unlock deliberately.
5. Read the lock state back in Home Assistant and, when safe, verify the physical door behavior.
6. Re-lock the door using the method you intend to rely on, then confirm the locked state.
7. Test that an accidental hold or double tap does not trigger an unplanned action if you set those gestures to none.

Do not describe the setup as hardware-tested unless you have completed an authorized test on that installation. A configuration example can show the intended Home Assistant behavior; it cannot prove that a particular reader’s Matter fabric, entity, firmware, or door alignment will behave identically.

Common mistakes to avoid

Using a broad target

lock.unlock accepts an entity, device, area, floor, or label target. A broad target can match multiple lock entities. For a confirmation prompt on one door, use one exact entity_id and name the door in the dialog.

Treating the prompt as authentication

The prompt asks for a deliberate second choice in the dashboard. It does not verify who is holding the device or prevent another authorized control path from unlocking the Lockin lock. Keep Home Assistant accounts, dashboard access, Lockin credentials, and any required lock code protected separately.

Editing an automatically managed dashboard

Some dashboards or cards may be managed by an integration or another configuration source. Before taking control, understand what will stop being managed automatically. If you need to preserve that management, add the confirmation in the supported source rather than making an untracked manual edit.

Confusing unlock with open

lock.unlock is the action for unlocking the lock. Home Assistant documents open as a separate action for a supported lock that can release a latch. Do not change the action to open unless that is the behavior you actually want and your Lockin integration exposes it.

What to do next

Once the cancel and deliberate-confirm tests pass, keep the button limited to the one Lockin door and review it after any entity rename, Matter re-pairing, firmware change, or dashboard migration. For model-specific setup and door conditions, check the Lockin Veno Pro product page, the Lockin FAQ, and the Lockin user-manual library.

The goal is simple: make the final Lockin Home Assistant unlock confirmation deliberate while keeping the Lockin lock, its actual Home Assistant entity, and its other access controls understood separately.