Historia

harshal.patil 483b87750c docs(wifi_provisioning): Use heap to allocate memory for the response Added a note to specify that the memory for the response of a custom endpoint should be allocated using the heap, as this memory gets freed by the protocomm layer once it has been passed to the transport layer. Closes https://github.com/espressif/esp-idf/issues/13263		2024-03-04 16:34:27 +05:30
..
wifi_prov_mgr	docs(wifi_provisioning): Use heap to allocate memory for the response	2024-03-04 16:34:27 +05:30
.build-test-rules.yml	Add ESP32-C6 in supported targets for wifi_prov_mgr example	2023-04-28 10:57:32 +05:30
README.md	provisioning: Remove legacy examples section from README	2022-01-28 09:58:43 +05:30

README.md

Provisioning Application Examples

This primarily consists of a single unified example wifi_prov_mgr

wifi_prov_mgr Abstracts out most of the complexity of Wi-Fi provisioning and allows easy switching between the SoftAP (using HTTP) and BLE transports. It also demonstrates how applications can register and use additional custom data endpoints.

Provisioning applications are available for various platforms:

Android:
- BLE Provisioning app on Play Store.
- SoftAP Provisioning app on Play Store.
- Source code on GitHub: esp-idf-provisioning-android.
iOS:
- BLE Provisioning app on app store
- SoftAP Provisioning app on app Store
- Source code on GitHub: esp-idf-provisioning-ios
For all other platforms a python based command line tool is provided under "$IDF_PATH/tools/esp_prov"

The Android and iOS provisioning applications allow the user to configure the device manually or by scanning a QR code. QR codes can be generated by any online QR code generator. QR code payload is encoded with a JSON string containing the device name, proof-of-possession key (if used) and transport type (BLE or softAP), for example:

{"ver":"v1","name":"PROV_000318","pop":"a1000318","transport":"softap"}

The more details about QR code format, you can refer to QR Code Scan.