Fixing Yale YRD510 Matter Locks Constantly Asking for Codes in Home Assistant

Understanding the Yale YRD510 Matter Code Prompt Issue

The Yale YRD510 Smart Lock with Matter is a popular choice for smart homes, offering local control via the Matter protocol. However, users integrating this lock into Home Assistant (HA) often encounter a frustrating issue: the lock constantly prompts for a Master Passcode or asks to set up entry codes, even after initial setup.

Why Code Prompts Appear

This behavior stems from how Matter handles user code management, or rather, the current lack of comprehensive support for it within Home Assistant’’s Matter integration.

1. Matter Standard Limitation: While the Matter Door Lock cluster supports user codes, Home Assistant’’s Matter integration (as of late 2024/early 2025, based on community discussions) often lacks the necessary UI or service calls to fully manage user codes directly.

2. Lock Default Behavior: The Yale lock firmware is designed to prompt for code setup if it detects that user codes have not been configured via the primary connected app (in this case, Home Assistant). If HA doesn’’t fully provision codes or the lock state isn’’t correctly reported back, the lock assumes setup is incomplete.

3. Multiple App Conflict (Pitfall): A critical pitfall is setting up entry codes in multiple Matter-enabled apps (e.g., Google Home and Home Assistant). Yale explicitly warns against this, as it can lead to conflicts and require a factory reset to clear all codes. Entry codes should only be set up in one app.

Expected Behavior and Pairing Pitfalls

When pairing the Yale YRD510 via Matter to Home Assistant:

• Initial Setup: You must first create a Master Passcode directly on the lock keypad if it’’s a fresh install or factory reset. This is required before connecting it to any app.

• HA Control: Once paired, HA should be able to lock and unlock the device.

• Code Management Gap: If HA does not provide a UI for code management, the lock may continue to prompt for codes on the keypad, as it expects the primary controller to handle this.

If you are experiencing persistent prompts, ensure you have not configured codes using another app. If you have, you may need to factory reset the lock and re-pair it, ensuring HA is the sole manager of user codes (if HA supports it for your specific Matter implementation).

Adding User Codes in Home Assistant

While the Matter integration might lack a dedicated UI, Home Assistant typically exposes services for managing user codes on door locks, often through the lock domain. You can use these services in automations or scripts.

The service usually required is lock.set_usercode.

YAML Example 1: Setting a Permanent User Code

This automation sets a user code (e.g., 1234) for slot 1 and enables it.

alias: Set Permanent User Code (Slot 1)
description: Sets a user code for a family member.
trigger: []
condition: []
action:
  - service: lock.set_usercode
    target:
      entity_id: lock.yale_yrd510_matter_lock
    data:
      code_slot: 1
      usercode: "1234"
      enabled: true
mode: single

YAML Example 2: Setting a Temporary Guest Code

This script sets a temporary code (e.g., 9876) for slot 2, which can be enabled/disabled via other automations.

script:
  set_guest_code:
    alias: Set Guest Code
    sequence:
      - service: lock.set_usercode
        target:
          entity_id: lock.yale_yrd510_matter_lock
        data:
          code_slot: 2
          usercode: "9876"
          enabled: true
    mode: single

Note on Code Slots: Lock devices typically support a limited number of user codes (e.g., 25 for Yale locks). The code_slot parameter refers to the index (starting from 1) where the code is stored on the lock.