Bluetooth LE SDK Host Stack Version 11.1.0 - Release Notes (Jun 23, 2026)#

Bluetooth LE Version 11.1.0

The Bluetooth Host Stack is a Bluetooth 6.1-compliant stack that provides the core functionality along with multiple API to simplify development. The core functionality offers both standalone mode, allowing a developer to create and run their application directly on the SoC, or NCP mode, allowing for the use of an external host MCU.

Click here for earlier releases.

Release Summary#

Key Features | API Changes | Bug Fixes | Chip Enablement

Key Features#

Periodic advertising ADI and data ID refresh support
Duplicate filtering for periodic advertisement reports
HCI and BGAPI connection handle conversion commands
Connection analyzer maintains synchronization through connection parameter and channel map updates
Configurable RPA randomization intervals for local privacy
RPA refresh notification events for scanner/initiator and advertisers
Read peer resolvable private address from Resolving List
Channel Sounding handover commands and events

API Changes#

New APIs for periodic advertising data management, duplicate filtering, connection handle conversion, connection analyzer LLCP processing, privacy RPA randomization, address refresh events, peer RPA reading, and CS handover

Bug Fixes#

Fixed Resolving List local IRK handling when local privacy is not active
Corrected documentation of sl_bt_cs_test_start() antenna_selection parameter

Chip Enablement#

None.

Key Features#

New Features | Enhancements | Removed Features | Deprecated Features

New Features#

New flag SL_BT_PERIODIC_ADVERTISER_INCLUDE_ADVERTISING_DATA_INFORMATION in sl_bt_periodic_advertiser_flags enables the inclusion of Advertising Data Information (ADI) in transmitted periodic advertising PDUs.
New command sl_bt_periodic_advertiser_refresh_data_id enables refreshing the Advertising Data ID (DID) without the need to provide the same data again.
New mode sl_bt_sync_report_non_duplicate in sl_bt_sync_reporting_mode_t enables filtering duplicate periodic advertisements.
The bluetooth_feature_linklayer_interface component provides new commands sl_bt_linklayer_get_hci_connection_handle and sl_bt_linklayer_get_bgapi_connection_handle for converting between link layer HCI connection handles and the BGAPI host stack connection handles. The application needs to convert between handle types when it uses the linklayer class to access low-level link layer functionality that uses connection handles.
The bluetooth_feature_connection_analyzer feature can now maintain synchronization to the analyzed connection even if connection parameters or channel map is updated. The LLCP events need to be passed from the Central device to the connection analyzer device by the application. Use the bluetooth_feature_connection_analyzer_llcp_report component and the sl_bt_linklayer_event_info_reporting_enable command to enable the LLCP reporting on the Central. Pass the corresponding LLCP events from sl_bt_evt_linklayer_event_info_report events to the connection analyzer device and use sl_bt_connection_analyzer_process_llcp_event to process the event.
New command sl_bt_gap_set_privacy_mode_with_rpa_randomization enables configuring local privacy with separate minimum and maximum RPA rotation intervals. When the interval bounds differ, advertiser and central-side RPAs are refreshed at randomized times within the configured range. Keeping the interval bounds equal preserves deterministic rotation behavior.
New events sl_bt_evt_gap_random_address_refresh and sl_bt_evt_advertiser_random_address_refresh notify the application when the scanner/initiator or a stack-managed advertiser starts using a new private address. The related privacy mode commands document these events.
New command sl_bt_resolving_list_read_peer_resolvable_address reads the current peer resolvable private address tracked by the controller for a device in the Resolving List.
The bluetooth_feature_cs component adds Channel Sounding (CS) handover commands and events to the cs BGAPI class. Use the bluetooth_feature_cs_handover_leader and bluetooth_feature_cs_handover_follower components to enable the corresponding controller-side handover roles. Retrieve CS procedure parameters from the CS Leader, pass them to the CS Follower, and use the handover commands and events to synchronize the Follower to the CS procedure and LE connection and to control scheduled CS procedure execution.

Removed Features#

None.

Deprecated Features#

None.

API Changes#

New APIs | Modified APIs | Removed APIs | Deprecated APIs

New APIs#


New API Signature	Deprecated API replaced by this
sl_bt_periodic_advertiser_refresh_data_id	N/A
sl_bt_sync_report_non_duplicate	N/A
sl_bt_linklayer_get_hci_connection_handle	N/A
sl_bt_linklayer_get_bgapi_connection_handle	N/A
sl_bt_connection_analyzer_process_llcp_event	N/A
sl_bt_gap_set_privacy_mode_with_rpa_randomization	N/A
sl_bt_evt_gap_random_address_refresh	N/A
sl_bt_evt_advertiser_random_address_refresh	N/A
sl_bt_resolving_list_read_peer_resolvable_address	N/A
sl_bt_cs_handover_get_procedure_parameters	N/A
sl_bt_cs_handover_set_procedure_parameters	N/A
sl_bt_cs_handover_create_sync	N/A
sl_bt_cs_handover_enable_procedure	N/A
sl_bt_cs_handover_remove_procedure	N/A
sl_bt_evt_cs_handover_sync_established	N/A
sl_bt_evt_cs_handover_complete	N/A
sl_bt_evt_cs_handover_result	N/A
sl_bt_evt_cs_handover_result_continue	N/A

Modified APIs#

None.

Removed APIs#

None.

Deprecated APIs#

None.

Bug Fixes#

ID	Issue Description	GitHub / Salesforce Reference (if any)	Affected SW or HW Variants, Modes
1382779	Fixed the Resolving List to use an all-zero local IRK when local privacy is not active. Previously, the real local IRK was always used when the local privacy component was present, which caused the controller to drop directed advertising packets addressed to the local device's identity address even when the application had not enabled local privacy.	None	Generic software issue
1529554	Fixed the GATT server to no longer raise an sl_bt_evt_gatt_server_characteristic_status event with a synthetic "notification and indication enabled" client config for characteristics whose CCCD is user-handled when a connection is opened or re-opened. User-handled CCCDs are owned by the application, so the stack has no client configuration state to report and now skips them in the per-connection client configuration reporting loop.	None	Generic software issue
1586657	Corrected the documentation of sl_bt_cs_test_start() parameter antenna_selection. The docs now state CS_SYNC usage (including mode-0 packets) and remove the 0xFE loop-mode note for this command. This is a documentation-only fix: runtime behavior is unchanged, and 0xFE was already unsupported for this command.	None	Generic software issue

Impact of Release Changes#

Impact Statements in 11.1.0#

Change	Migration Guide	Affected Software Variants if applicable	Affected Modes	Affected OPNs / Boards / OPN Combinations	Affected Host Interfaces
The Resolving List now sets the local IRK based on whether local privacy is currently active. When local privacy is not active, an all-zero local IRK is used so the controller uses the local device's identity address. Previously, the real local IRK was always used, preventing the local device from receiving directed advertising to its identity address.	Applications that add devices to the Resolving List should be aware that the local IRK is determined at the time the device is added. If the application changes the local privacy mode after adding devices to the Resolving List, it should remove all devices and re-add them to ensure the correct local IRK is used.	All	All	Hardware agnostic	N/A

Known Issues and Limitations#

ID	Issue or Limitation Description	GitHub / Salesforce Reference (if any)	Workaround (if any)	Affected Software Variants, Hardware, Modes, Host Interfaces
1417141	The OTA DFU fast mode in the Bootloader with Apploader is unreliable due to the chance of packet losses.	None	Use OTA DFU reliable mode.	All