Why Did Your Smart-Lock Unlocked Reminder Disappear After Home Assistant Restarted?

If your smart lock reminder disappeared after Home Assistant restarted, the most likely reason is a duration-based trigger was still counting down when Home Assistant went offline. Home Assistant documents that a trigger using for: does not survive a restart or automation reload; the pending wait is reset. The lock may still be physically unlocked, but the reminder’s timer is gone.

That is the smart lock reminder Home Assistant restart problem in one sentence: the timer was temporary, while the lock state may still be real.

For a Lockin Veno Solar Palm that is already exposed to Home Assistant as a supported lock entity, rebuild the reminder around a saved deadline rather than an in-memory duration. Re-check the lock state after startup, and send a notification only when the entity is confirmed unlocked. Treat unknown and unavailable as “do not decide yet”—never as proof that the door is unlocked.

Why a smart lock reminder resets after a Home Assistant restart

Home Assistant’s lock integration keeps a state for each lock and makes that state available to automations. Its documented lock states include locked, unlocked, open, jammed, unavailable, and unknown.

A common reminder looks conceptually like this:

triggers:
  - trigger: state
    entity_id: lock.front_door
    to: "unlocked"
    for: "00:10:00"
actions:
  - action: notify.send_message
    data:
      message: "The front door is still unlocked."

The for value is a duration that Home Assistant is waiting to observe. It is not, by itself, a durable appointment stored for later. If Home Assistant restarts or automations are reloaded during those 10 minutes, the pending duration is reset. That is why a smart lock reminder can vanish even though the lock has not changed state.

This is different from the lock’s physical state. A restart can interrupt the automation’s timer without locking or unlocking the Veno Solar Palm. Confirm the actual entity state before taking any action.

The safer pattern: save a deadline, then check the lock

Home Assistant’s trigger documentation suggests using an input_datetime to store the desired time when a for wait must survive a restart. The pattern is:

1. When the lock becomes unlocked, calculate a reminder deadline.
2. Save that deadline in an input_datetime helper.
3. Use the helper as a time trigger.
4. At the deadline, check that the lock is still exactly unlocked.
5. Send a reminder only if the state check passes.
6. Clear or replace the deadline when the lock becomes locked.

The important detail is step four. A saved deadline tells Home Assistant when to evaluate the reminder; it does not prove what happened while Home Assistant was restarting. The final state check prevents a stale appointment from producing a misleading notification.

Example structure

The following is a pattern to adapt in your own installation. Replace the entity IDs and notification service with your actual helpers. The exact YAML syntax can vary with your Home Assistant version and whether you use the visual editor.

input_datetime:
  front_door_unlocked_reminder_at:
    name: Front door unlocked reminder at
    has_date: true
    has_time: true

automation:
  - alias: "Record a restart-safe unlocked reminder deadline"
    triggers:
      - trigger: state
        entity_id: lock.front_door
        to: "unlocked"
    actions:
      - action: input_datetime.set_datetime
        target:
          entity_id: input_datetime.front_door_unlocked_reminder_at
        data:
          # Set this to your chosen reminder time using a template or helper.
          datetime: "{{ (now() + timedelta(minutes=10)).strftime('%Y-%m-%d %H:%M:%S') }}"

  - alias: "Remind me if the front door is still unlocked"
    triggers:
      - trigger: time
        at: input_datetime.front_door_unlocked_reminder_at
    conditions:
      - condition: state
        entity_id: lock.front_door
        state: "unlocked"
    actions:
      - action: notify.mobile_app_your_phone
        data:
          message: "The front door is still unlocked. Check the lock before leaving it unattended."

  - alias: "Clear the unlocked reminder deadline when the door locks"
    triggers:
      - trigger: state
        entity_id: lock.front_door
        to: "locked"
    actions:
      - action: input_datetime.set_datetime
        target:
          entity_id: input_datetime.front_door_unlocked_reminder_at
        data:
          datetime: "1970-01-01 00:00:00"

Use the Home Assistant editor to validate the configuration, and test it with a short interval before relying on it overnight. If your chosen helper or version handles clearing a time helper differently, follow the current Home Assistant documentation for that helper.

What to check after Home Assistant restarts

When a smart lock reminder disappears after a restart, use this sequence:

1. Confirm the automation is enabled

Open Settings → Automations & scenes and check that the reminder automation is enabled. An automation reload can reset a pending for trigger in the same way as a full restart.

2. Check the actual lock entity

Look at the entity used by the automation, not just a dashboard card or an old notification. The state should be unlocked before a reminder is sent. unknown means Home Assistant does not yet know the state; unavailable means the entity is currently unavailable. Wait for the integration to recover or investigate connectivity before making a safety decision.

3. Confirm the deadline helper survived

Inspect the input_datetime value. If it is empty, invalid, in the past, or pointing to the wrong day, the deadline-based automation cannot behave as intended. Check the helper’s date and time settings and Home Assistant’s timezone.

4. Check the integration path

Home Assistant’s Matter integration controls Matter devices over a local Wi-Fi or Thread network through its Matter Server. Lockin lists Veno Solar Palm as Matter compatible and says it works with Apple Home, Alexa, Google Home, and SmartThings. That does not by itself prove that every Veno configuration exposes the same Home Assistant entity or attributes. Confirm the actual entity and its supported actions in your installation.

5. Test the reminder without controlling the lock

Use a short deadline and an ordinary notification. Verify the message arrives after the lock remains unlocked, then lock the door and confirm that no later reminder is sent. Do not include lock.unlock, lock.open, or another motor-control action in a reminder workflow.

Why the Veno Solar Palm model check matters

The Veno Solar Palm product page lists built-in Wi-Fi, remote lock and unlock management, Matter compatibility, and auto-lock. It also lists palm-vein, PIN, app, mechanical-key, and voice unlock methods. These features belong to the named model; do not extend them automatically to another Veno variant.

The product page also links the lock’s support resources and user manual. Use the current Veno Solar Palm product page, Lockin FAQ, and user manual library to confirm the current model, firmware, and setup conditions before troubleshooting an integration.

Reminder versus auto-lock: choose the outcome carefully

A reminder is a notification workflow. It asks a person to check the door. Auto-lock is a separate lock behavior that may move the bolt automatically after the configured condition. Home Assistant also documents lock actions such as locking and unlocking, but the existence of an action is not a reason to include it in a reminder.

Choose a reminder when you want a human to decide what to do, especially after a restart or when the state may be stale. Consider the Veno Solar Palm’s documented auto-lock settings separately in the Lockin app and manual if automatic relocking fits your door alignment, household routine, and model configuration. Test the physical door; software state alone cannot confirm that a bolt completed its movement without error.

The short answer

Your smart lock reminder disappeared because Home Assistant’s pending for duration was reset by the restart or automation reload. Store a restart-safe deadline in an input_datetime, then check that the Veno lock entity is currently unlocked before sending the notification. Do not interpret unknown or unavailable as unlocked, and do not turn a reminder into an automatic unlock or bypass of platform confirmation.

If the entity remains unavailable or the state does not match the lock, pause the automation and consult the current Lockin FAQ or user manual with the model and firmware details in hand.

Sources

• Home Assistant automation triggers — for waits reset on restart or automation reload; input_datetime is the documented persistence pattern.
• Home Assistant Lock integration — lock states, triggers, conditions, and reminder example.
• Home Assistant Matter integration — Matter controller and local Wi-Fi/Thread conditions.
• Lockin Veno Solar Palm — current model-level features and support links.