Ryan Powell
Ryan Powell
Please see #777 The answer is in the comment from you code: > NimBLEAddress MAC_LiPo4(MAC_lithium, 0); // 0=Public, 1= Random --- BLE_ADDR_PUBLIC (0) BLE_ADDR_RANDOM (1) That should be: `NimBLEAddress MAC_LiPo4(MAC_lithium,...
Not much you can do really. If the devices are known then you can save their addresses and try directly connecting without scanning but that won't save much.
Any chance you can decode that backtrace?
Honestly, your code to deinit isn't required as the call to `NimBLEDevice::deinit();` will do the same thing anyway. Try that and let me know what happens.
Okay, I'll look into it, thanks!
This appears to be an issue upstream, the backtrace indicates that when `esp_bt_controller_deinit` is called is when the crash occurs, which is not a function in this library. I do...
I have confirmed the issue on an esp32c6 and also confirmed that the cause is an upstream bug as it also happens with the BLE library included in the Arduino...
The only workaround for now is to comment out the call to `esp_bt_controller_deinit`, the controller won't deinitailize so the resources will still be consumed but at least the rest of...
@keenravi-hub Unfortunately this is not fixable within this library as it is an upstream bug and will need to wait for the Arduino core to be updated.
Possibly related to https://github.com/h2zero/NimBLE-Arduino/issues/1041 Please try the fix suggested there and let me know.