基于esp32的mqtt通信平台设计.zip （毕设/课设/竞赛/实训/项目开发）

# Wi-Fi Provisioning Manager Example (See the README.md file in the upper level 'examples' directory for more information about examples.) `wifi_prov_mgr` example demonstrates the usage of `wifi_provisioning` manager component for building a provisioning application. For this example BLE is chosen as the mode of transport, over which the provisioning related communication is to take place, between the device (to be provisioned) and the client (owner of the device). In the provisioning process the device is configured as a Wi-Fi station with specified credentials. Once configured, the device will retain the Wi-Fi configuration, until a flash erase is performed. Right after provisioning is complete, BLE is turned off and disabled to free the memory used by the BLE stack. Though, that is specific to this example, and the user can choose to keep BLE stack intact in their own application. `wifi_prov_mgr` uses the following components : * `wifi_provisioning` : provides manager, data structures and protocomm endpoint handlers for Wi-Fi configuration * `protocomm` : for protocol based communication and secure session establishment * `protobuf` : Google's protocol buffer library for serialization of protocomm data structures * `bt` : ESP32 BLE stack for transport of protobuf packets This example can be used, as it is, for adding a provisioning service to any application intended for IoT. ## How to use example ### Hardware Required Example should be able to run on any commonly available ESP32 development board. ### Application Required Provisioning applications are available for various platforms. See below #### Platform : Android For Android, a provisioning application along with source code is available on GitHub : [esp-idf-provisioning-android](https://github.com/espressif/esp-idf-provisioning-android) #### Platform : iOS For iOS, a provisioning application along with source code is available on GitHub : [esp-idf-provisioning-ios](https://github.com/espressif/esp-idf-provisioning-ios) #### Platform : Linux / Windows / macOS To provision the device running this example, the `esp_prov.py` script needs to be run (found under `$IDF_PATH/tools/esp_prov`). Make sure to satisfy all the dependencies prior to running the script. Presently, `esp_prov` supports BLE transport only for Linux platform. For Windows/macOS it falls back to console mode and requires another application (for BLE) through which the communication can take place. There are various applications, specific to Windows and macOS platform which can be used. The `esp_prov` console will guide you through the provisioning process of locating the correct BLE GATT services and characteristics, the values to write, and input read values. ### Configure the project ``` make menuconfig ``` * Set serial port under Serial Flasher Options. ### Build and Flash Build the project and flash it to the board, then run monitor tool to view serial output: ``` make -j4 flash monitor ``` (To exit the serial monitor, type ``Ctrl-]``.) See the Getting Started Guide for full steps to configure and use ESP-IDF to build projects. ## Example Output ``` I (445) app: Starting provisioning I (1035) app: Provisioning started I (1045) wifi_prov_mgr: Provisioning started with service name : PROV_261FCC ``` Make sure to note down the BLE device name (starting with `PROV_`) displayed in the serial monitor log (eg. PROV_261FCC). This will depend on the MAC ID and will be unique for every device. In a separate terminal run the `esp_prov.py` script under `$IDP_PATH/tools/esp_prov` directory (make sure to replace `myssid` and `mypassword` with the credentials of the AP to which the device is supposed to connect to after provisioning). Assuming default example configuration, which uses protocomm security scheme 1 and proof of possession PoP based authentication : ``` python esp_prov.py --transport ble --service_name PROV_261FCC --sec_ver 1 --pop abcd1234 --ssid myssid --passphrase mypassword ``` Above command will perform the provisioning steps, and the monitor log should display something like this : ``` I (39725) app: Received Wi-Fi credentials SSID : myssid Password : mypassword . . . I (45335) tcpip_adapter: sta ip: 192.168.43.243, mask: 255.255.255.0, gw: 192.168.43.1 I (45345) app: Provisioning successful I (45345) app: Connected with IP Address:192.168.43.243 I (46355) app: Hello World! I (47355) app: Hello World! I (48355) app: Hello World! I (49355) app: Hello World! . . . I (52315) wifi_prov_mgr: Provisioning stopped . . . I (52355) app: Hello World! I (53355) app: Hello World! I (54355) app: Hello World! I (55355) app: Hello World! ``` ### Wi-Fi Scanning Provisioning manager also supports providing real-time Wi-Fi scan results (performed on the device) during provisioning. This allows the client side applications to choose the AP for which the device Wi-Fi station is to be configured. Various information about the visible APs is available, like signal strength (RSSI) and security type, etc. Also, the manager now provides capabilities information which can be used by client applications to determine the security type and availability of specific features (like `wifi_scan`). When using the scan based provisioning, we don't need to specify the `--ssid` and `--passphrase` fields explicitly: ``` python esp_prov.py --transport ble --service_name PROV_261FCC --pop abcd1234 ``` See below the sample output from `esp_prov` tool on running above command: ``` Connecting... Connected Getting Services... Security scheme determined to be : 1 ==== Starting Session ==== ==== Session Established ==== ==== Scanning Wi-Fi APs ==== ++++ Scan process executed in 1.9967520237 sec ++++ Scan results : 5 ++++ Scan finished in 2.7374596596 sec ==== Wi-Fi Scan results ==== S.N. SSID BSSID CHN RSSI AUTH [ 1] MyHomeWiFiAP 788a20841996 1 -45 WPA2_PSK [ 2] MobileHotspot 7a8a20841996 11 -46 WPA2_PSK [ 3] MyHomeWiFiAP 788a208daa26 11 -54 WPA2_PSK [ 4] NeighborsWiFiAP 8a8a20841996 6 -61 WPA2_PSK [ 5] InsecureWiFiAP dca4caf1227c 7 -74 Open Select AP by number (0 to rescan) : 1 Enter passphrase for MyHomeWiFiAP : ==== Sending Wi-Fi credential to esp32 ==== ==== Wi-Fi Credentials sent successfully ==== ==== Applying config to esp32 ==== ==== Apply config sent successfully ==== ==== Wi-Fi connection state ==== ++++ WiFi state: connected ++++ ==== Provisioning was successful ==== ``` ## Troubleshooting ### Provisioning failed It is possible that the Wi-Fi credentials provided were incorrect, or the device was not able to establish connection to the network, in which the the `esp_prov` script will notify failure (with reason). Serial monitor log will display the failure along with disconnect reason : ``` E (367015) app: Provisioning failed! Reason : Wi-Fi AP password incorrect Please reset to factory and retry provisioning ``` Once credentials have been applied, even though wrong credentials were provided, the device will no longer go into provisioning mode on subsequent reboots until NVS is erased (see following section). ### Provisioning does not start If the serial monitor log shows the following : ``` I (465) app: Already provisioned, starting Wi-Fi STA ``` it means either the device has been provisioned earlier with or without success (e.g. scenario covered in above section), or that the Wi-Fi credentials were already set by some other application flashed previously onto your device. On setting the log level to DEBUG this is clearly evident : ``` D (455) wifi_prov_mgr: Found Wi-Fi SSID : myssid D (465) wifi_prov_mgr: Found Wi-Fi Password : m********d