BLE Provisioning failure with NimBLE stack only
Posted: Tue Nov 26, 2019 9:45 pm
Hey all,
I've implemented WiFi provisioning using the WiFi Provisioning Manager component. I've tested out the SoftAP transport and am working on trying the BLE transport as well so I can compare the two experiences.
Some background:
NimBLE also outputs a bunch of debug information, presumably using printfs instead of builtin logging functions. If this info is useful I can paste the complete output using dummy credentials.
If I use the older Bluedroid stack instead of NimBLE, provisioning goes smoothly and works pretty consistently, just like with SoftAP transport. I'd like to switch to NimBLE since it's lighter-weight and I only plan on using BLE anyways.
I've implemented WiFi provisioning using the WiFi Provisioning Manager component. I've tested out the SoftAP transport and am working on trying the BLE transport as well so I can compare the two experiences.
Some background:
- I'm using the Security0 option for provisioning but may move to Security1 later.
- Using ESP-IDF v4.0-beta2
- I have not changed any of the bluetooth-related options in sdkconfig except for the Bluetooth stack
Code: Select all
E (198740) WiFiProvConfig: Unable to unpack config data
E (198741) protocomm_nimble: Invalid content received, killing connection
E (198831) wifi_prov_handlers: Wi-Fi config not set
If I use the older Bluedroid stack instead of NimBLE, provisioning goes smoothly and works pretty consistently, just like with SoftAP transport. I'd like to switch to NimBLE since it's lighter-weight and I only plan on using BLE anyways.