Ryan Powell

Hello, I can't think of any way to do this currently. It could be done with some significant changes to the code, I do not have time for doing that...

Interesting approach, glad to see you're making progress. Happy to review when you're ready.

It appears this may be a result of upstream changes in the way the data is stored in NVS, I haven't identified the changes yet but it may just have...

@KlausMu I have identified the cause of this issue and it was an intended change, that is also a good one. The commit [here](https://github.com/espressif/esp-nimble/commit/12df982603c69e0df85d2619f6ae2f248ae52a4c) changes the IRK when freshly flashed...

> Going from 1.4.2 to 2.0.0 ESP32 is freshly flashed and booted, IRK changes, already bonded devices do not work because of the changed IRK. Correct, this basically changes the...

@KlausMu I have created a way to detect the downgrade and only erase the NimBLE bond storage info instead of the entire NVS. ``` esp_err_t err = nvs_flash_init(); if (err...

Both of those keys are only present in version 2.x (nimble core 1.5), so in your app you can use the code I provided to detect if they exist and...

Yes, that would be correct as well.

@KlausMu You can check for `peer_sec_1` which will be there if at least 1 bond exists. >After erasing the nimble_bond namespace, NimBLEDevice::getNumBonds() still returns the bonded peers. I believe they...

Are you also storing the address type?