Synchronize multiple DF TX devices in the DF Connectionless RX Example "Periodic Advertising list"

[Faizan-Ellahi-DE]

I got an Unknown Command error while working with the periodic advertising list feature #29127

When I tried to add the device to the Periodic Advertising list or clear the Periodic Advertising list, error -5 shows over the terminal after deep looking at the source code found the reason for such error is that commands (BT_HCI_OP_LE_ADD_DEV_TO_PER_ADV_LIST, BT_HCI_OP_LE_REM_DEV_FROM_PER_ADV_LIST, BT_HCI_OP_LE_CLEAR_PER_ADV_LIST, BT_HCI_OP_LE_READ_PER_ADV_LIST_SIZE) are not defined/handled in the **static int controller_cmd_handle(uint16_t ocf, struct net_buf *cmd, struct net_buf **evt, void node_rx) function.

Is there any way to solve such a bug, kindly guide me?

[cvinayak]

Periodic Advertising List in the Controller is work in progress, please try this PR: #38338

[cvinayak]

@Thalley Does the host support synchronization from periodic advertising lists?

Shouldn't this check addresses in the list?

zephyr/subsys/bluetooth/host/scan.c

Lines 696 to 702 in f50574a

	if (!pending_per_adv_sync ||
	pending_per_adv_sync->sid != evt->sid ||
	bt_addr_le_cmp(&pending_per_adv_sync->addr, &evt->adv_addr)) {
	struct bt_le_per_adv_sync_term_info term_info;
	BT_ERR("Unexpected per adv sync established event");
	per_adv_sync_terminate(sys_le16_to_cpu(evt->handle));

[Thalley]

@Thalley Does the host support synchronization from periodic advertising lists?

Shouldn't this check addresses in the list?

zephyr/subsys/bluetooth/host/scan.c

Lines 696 to 702 in f50574a

	if (!pending_per_adv_sync ||
	pending_per_adv_sync->sid != evt->sid ||
	bt_addr_le_cmp(&pending_per_adv_sync->addr, &evt->adv_addr)) {
	struct bt_le_per_adv_sync_term_info term_info;
	BT_ERR("Unexpected per adv sync established event");
	per_adv_sync_terminate(sys_le16_to_cpu(evt->handle));

Yes, that is actually still missing. Basically we need to implement this paragraph:

If the Periodic Advertiser List is not used, the Advertising_SID, Advertiser Address_Type, and Advertiser Address parameters specify the periodic advertising device to listen to; otherwise they shall be ignored.

So if the option to use the list is set, then we shall ignore the address parameters and instead either just accept it, or store the list in the host and validate whether the address of the event is in the list. The former is the simpler solution, and I am not sure if we need to validate the address in the host.