Ryan Powell

Hi @mitchjs, I haven't yet reached the point where I'll be implementing extra support for bond maintenance etc. I hope to get there soon though. If you need this functionality...

You'll need to change: ``` NimBLECharacteristic *MyLEDStatusCharacteristic = pService->createCharacteristic(CHARACTERISTIC_UUID_LED_STATUS, NIMBLE_PROPERTY::READ_ENC | NIMBLE_PROPERTY::NOTIFY); ``` to: ``` NimBLECharacteristic *MyLEDStatusCharacteristic = pService->createCharacteristic(CHARACTERISTIC_UUID_LED_STATUS, NIMBLE_PROPERTY::READ | NIMBLE_PROPERTY::READ_ENC | NIMBLE_PROPERTY::NOTIFY); ``` For some reason this is...

> (mostly in nRF Connect, god i hate this program... lightblue better, what else is there?) ble scanner is pretty good. > i didnt create the 2902, its done by...

If you bond, the keys are persisted in the phone and on the esp32, if you delete the bond on one of them they both need to be deleted (library...

> failed to configure restored IRK That's the nimble stack letting us know what the issue is, I'm not sure why it would have this problem I would need to...

Actually I think I know why, you are using IDF v4.0 correct? If so can you tell me the commit you're on. I made a PR on the esp-nimble repo...

Yeah, that’s because it has stored bonds that it’s trying to load and cannot for some reason. If you checkout my esp-nimble-component library and put that in your projects/components folder...

Just so you know why this is happening here is the PR that fixes it. https://github.com/espressif/esp-nimble/pull/7

This is odd, I don’t see any issues here on master branch, I’ll look into this more. I’ll get back to you after I do some testing.

After you switched branches did you `erase_flash`? You’ll need to start out clean once you have the updated nimble, also delete esp32 bonds from your phone.