RE: autoconnect issue after power reset in RPA

Hung Bui — Mon, 27 Jul 2026 11:59:30 GMT

Hi Khodidas,

If it's Matter device then the behavior is expected. You are not supposed to have BLE bond retained with a central if you do Matter. It's because in Matter you only use the phone for provisioning and you shouldn't retain bond after that.
You can take a look at this ticket: BLE Bonding after power cycle

A solution was suggested in the ticket.

RE: autoconnect issue after power reset in RPA

Khodidas11 — Sat, 25 Jul 2026 05:17:43 GMT

Dear Hung Bui
yes i have used, it still facing issue. attached is prj.conf

#
# Copyright (c) 2022 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

# This sample uses Kconfig.defaults to set options common for all
# samples. This file should contain only options specific for this sample
# or overrides of default values.

# Enable CHIP
CONFIG_CHIP=y
CONFIG_CHIP_PROJECT_CONFIG="src/chip_project_config.h"
CONFIG_CHIP_DEVICE_PRODUCT_NAME="Matter Door Lock"

# Configure ZAP file name
CONFIG_NCS_SAMPLE_MATTER_ZAP_FILE_PATH="${APPLICATION_CONFIG_DIR}/src/default_zap/lock.zap"

# 32774 == 0x8006 (example lock-app)
CONFIG_CHIP_DEVICE_PRODUCT_ID=32774
CONFIG_STD_CPP17=y

# Enable Matter extended announcement and increase duration to 1 hour.
CONFIG_CHIP_BLE_EXT_ADVERTISING=y
CONFIG_CHIP_BLE_ADVERTISING_DURATION=60

# Add support for LEDs and buttons on Nordic development kits
CONFIG_DK_LIBRARY=y

# Bluetooth Low Energy configuration
CONFIG_BT_DEVICE_NAME="MatterLock"

# Suspend devices when the CPU goes into sleep
CONFIG_PM_DEVICE=y

# Other settings
CONFIG_THREAD_NAME=y
CONFIG_MPU_STACK_GUARD=y
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_CHIP_LIB_SHELL=y
CONFIG_NCS_SAMPLE_MATTER_TEST_SHELL=y

# Reduce application size
CONFIG_USE_SEGGER_RTT=n
CONFIG_MATTER_LOG_LEVEL_INF=y
CONFIG_CHIP_APP_LOG_LEVEL=3

# Enable Factory Data feature
CONFIG_CHIP_FACTORY_DATA=y
CONFIG_CHIP_FACTORY_DATA_BUILD=y


#=============================Mantra======================#
# Enable multi-advertising / multiple identities if using concurrently with Matter
CONFIG_BT_ID_MAX=2

# Enable standard BLE peripheral and GATT features
CONFIG_BT_PERIPHERAL=y
#CONFIG_BT_DEVICE_NAME="Smart_lock1.1"
CONFIG_BT_DEVICE_NAME="MySecureLock"

# Optional: If you want to use the Nordic UART Service (NUS) for custom phone-to-lock features
CONFIG_CHIP_NUS=y


#========for Fix Passkey======#
CONFIG_BT_SMP=y
CONFIG_BT_SIGNING=y
CONFIG_BT_BONDABLE=y
CONFIG_BT_FIXED_PASSKEY=y
CONFIG_BT_SETTINGS=y
CONFIG_BT_CTLR_PRIVACY=y
CONFIG_BT_CTLR_TX_PWR_MINUS_40=y
CONFIG_BT_FILTER_ACCEPT_LIST=y
# Allow overwriting/updating existing bond keys
CONFIG_BT_KEYS_OVERWRITE_OLDEST=y
CONFIG_BT_PRIVACY=y

# Enable multi-connection support
CONFIG_BT_MAX_CONN=3
CONFIG_BT_MAX_PAIRED=3
#CONFIG_BT_ID_MAX=3
CONFIG_TEST_RANDOM_GENERATOR=y

CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y

CONFIG_PM=y
#For Hw information like mac, uniq serialno. etc
CONFIG_HWINFO=y

CONFIG_BT_PRIVACY=n

RE: autoconnect issue after power reset in RPA

Hung Bui — Wed, 22 Jul 2026 14:44:24 GMT

Hi Khodidas,

Could you check if you have configured CONFIG_BT_BONDABLE=y ?
Without that the device will only pair and not bond. Meaning each time you connect it will require a new bond.

When you use advertising with RPA, and you bonded to the peer device, the peer device (phone) should be able to recognize the advertiser using the keys they exchanged when bond even the address changes.

I would suggest to go through our BLE course: https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-5-bluetooth-le-security-fundamentals/