esp32-h2 matter error; (CON-1892)

[Shawn-115200]

Describe the bug
A clear and concise description of what the bug is.

Environment

• ESP-Matter Commit Id: a4da466

• ESP-IDF Commit Id: 7452b1cb1d22cd1b439a6a922548efacea98ee72

• SoC (eg: ESP32 or ESP32-C3): esp32-h2

• Device Logs (Please attach the log file): see th end;

• Host Machine OS: ubuntu2404

• Host Machine Python version: python-3.12.3

• Commissioner app and versions if present:

• Home hub app and versions if present:

• Commissioner's logs if present:

Any additional details
log
`

Host Machine(x86 machine) + esp32-H2(ot_rcp); esp32-H2(light)

Host Machine run command;

sudo chip-tool pairing ble-thread 1001 hex:0e08000000000001000000030000194a0300000c35060004001fffe00208b96bc343db574ad30708fd7277dced3e72ed051012a871d89538c1c8e2bc04b0de7dea61030f4f70656e5468726561642d3065363401020e6404100ac2eea7baa12c2ec9bf9f46054029cb0c0402a0f7f8 20202021 3840

esp32/esp-matter/examples/light

matter ble adv start

Starting BLE advertising
Done

I (1333701) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (1333701) NimBLE: GAP procedure initiated: advertise;
I (1333701) NimBLE: disc_mode=2
I (1333701) NimBLE: adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (1333701) NimBLE:

I (1333701) chip[DL]: CHIPoBLE advertising started
I (1333821) chip[DL]: BLE GAP connection established (con 0)
I (1333821) chip[DL]: CHIPoBLE advertising stopped
I (1335761) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 0 16
I (1335761) chip[BLE]: local and remote recv window sizes = 5
I (1335761) chip[BLE]: selected BTP version 4
I (1335761) chip[BLE]: using BTP fragment sizes rx 244 / tx 244.
I (1335861) chip[DL]: Write request/command received for CHIPoBLE TX CCCD characteristic (con 0 ) indicate = 1
I (1335861) chip[DL]: CHIPoBLE subscribe received
I (1335861) NimBLE: GATT procedure initiated: indicate;
I (1335861) NimBLE: att_handle=18

I (1335961) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 0) status= 14
I (1335961) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 0 16
I (1335971) chip[EM]: >>> [E:27612r S:0 M:223160270] (U) Msg RX from 0:B4445AA23118C48E [0000] to 0000000000000000 --- Type 0000:20 (SecureChannel:PBKDFParamRequest) (B:98)
I (1338471) NimBLE: GATT procedure initiated: indicate;
I (1338471) NimBLE: att_handle=18

I (1338561) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 0) status= 14
I (1341061) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 0 16
I (1343561) NimBLE: GATT procedure initiated: indicate;
I (1343561) NimBLE: att_handle=18

I (1343661) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 0) status= 14
I (1346161) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 0 16
I (1348661) NimBLE: GATT procedure initiated: indicate;
I (1348661) NimBLE: att_handle=18

I (1348761) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 0) status= 14
I (1351261) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 0 16
I (1353761) NimBLE: GATT procedure initiated: indicate;
I (1353761) NimBLE: att_handle=18

I (1353911) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 0) status= 14
I (1356361) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 0 16
I (1358861) NimBLE: GATT procedure initiated: indicate;
I (1358861) NimBLE: att_handle=18

I (1358961) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 0) status= 14
I (1361461) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 0 16
I (1363971) NimBLE: GATT procedure initiated: indicate;
I (1363971) NimBLE: att_handle=18

I (1364061) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 0) status= 14
I (1366561) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 0 16
I (1367361) chip[DL]: Write request/command received for CHIPoBLE TX CCCD characteristic (con 0 ) indicate = 0
I (1367361) chip[DL]: CHIPoBLE unsubscribe received
I (1367371) chip[BLE]: Releasing end point's BLE connection back to application.
I (1367371) chip[DL]: Closing BLE GATT connection (con 0)
I (1367371) NimBLE: GAP procedure initiated: terminate connection; conn_handle=0 hci_reason=19

I (1367371) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (1367371) NimBLE: GAP procedure initiated: advertise;
I (1367371) NimBLE: disc_mode=2
I (1367371) NimBLE: adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (1367371) NimBLE:

I (1367371) chip[DL]: CHIPoBLE advertising started
I (1367461) chip[DL]: BLE GAP connection terminated (con 0 reason 0x216)
I (1367471) chip[DL]: Configuring CHIPoBLE advertising (interval 25 ms, connectable)
I (1367471) chip[DL]: Device already advertising, stop active advertisement and restart
I (1367471) NimBLE: GAP procedure initiated: stop advertising.

I (1367471) NimBLE: GAP procedure initiated: advertise;
I (1367471) NimBLE: disc_mode=2
I (1367471) NimBLE: adv_channel_map=0 own_addr_type=1 adv_filter_policy=0 adv_itvl_min=40 adv_itvl_max=40
I (1367471) NimBLE:

I (1367471) esp_matter_core: BLE Disconnected
`
...

[Jerry-ESP]

This does not appear to be a firmware issue. I tested using the same version of the firmware and did not encounter such a problem. And please share the chip-tool logs, maybe it's a commissioner side issue.

[dhrishi]

@Shawn-115200 Can you please share the chip-tool logs as requested? Please close the issue if it works now