Some more information for better understanding of my problem. My goal is to change as little as possible in the existing esp-matter implementation. To achieve this, I wanted to start Nimble BLE with my BLE profile as soon as the esp-matter SDK tells me that BLE is no longer needed for Matter/CHIP. A...

Hello everyone, I have a similar question. @trantrieuphi: Have you found a solution? As a workaround, I have added an abort service to the Matter BLE profile to abort the commissioning process. As soon as I receive the ChipDeviceEvent "kCHIPoBLEConnectionClosed", I initialize the nimble stack and st...