kopia lustrzana https://github.com/espressif/esp-idf
97f4130ad2
By default, disabled the BLE Encrpyption requirement for provisioning characteristic. With this flag enabled, when remote attempts to read and if the ACL link is not encrypted, ESP device will return Insufficient Authentication. It is remote device responsibility to go for link encryption which may result in pairing. Some devices do not proceed for any pairing and just show failure pop-up. Also, user needs to remove bonding on remote phone manually and then try again. This is causing bad user experience. End user can enable it as per their use case. |
||
|---|---|---|
| .. | ||
| wifi_prov_mgr | ||
| .build-test-rules.yml | ||
| README.md | ||
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.