ESP32 Forum

Hi,
I have tried the switch example on ESP-32 few days back and it was working perfectly. now again I am trying the same switch example but now wifi provisioning through QR code is not working.

I already tried to reset the wifi and reset the board but still, the issue is not resolved.
i am using app version -2.2.4 and latest idf code.

Log:

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4
load:0x3fff0034,len:7116
load:0x40078000,len:13212
ho 0 tail 12 room 4
load:0x40080400,len:4568
entry 0x400806f4
I (30) boot: ESP-IDF v4.2.1 2nd stage bootloader
I (30) boot: compile time 18:06:59
I (30) boot: chip revision: 1
I (33) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (40) boot.esp32: SPI Speed : 40MHz
I (45) boot.esp32: SPI Mode : DIO
I (49) boot.esp32: SPI Flash Size : 4MB
I (54) boot: Enabling RNG early entropy source...
I (59) boot: Partition Table:
I (63) boot: ## Label Usage Type ST Offset Length
I (70) boot: 0 sec_cert unknown 3f 00 0000d000 00003000
I (78) boot: 1 nvs WiFi data 01 02 00010000 00006000
I (85) boot: 2 otadata OTA data 01 00 00016000 00002000
I (93) boot: 3 phy_init RF data 01 01 00018000 00001000
I (100) boot: 4 ota_0 OTA app 00 10 00020000 00190000
I (108) boot: 5 ota_1 OTA app 00 11 001b0000 00190000
I (115) boot: 6 fctry WiFi data 01 02 00340000 00006000
I (123) boot: End of partition table
I (127) boot_comm: chip revision: 1, min. application chip revision: 0
I (134) esp_image: segment 0: paddr=0x00020020 vaddr=0x3f400020 size=0x35a9c (219804) map
I (227) esp_image: segment 1: paddr=0x00055ac4 vaddr=0x3ffbdb60 size=0x0424c ( 16972) load
I (234) esp_image: segment 2: paddr=0x00059d18 vaddr=0x40080000 size=0x00404 ( 1028) load
I (235) esp_image: segment 3: paddr=0x0005a124 vaddr=0x40080404 size=0x05ef4 ( 24308) load
I (253) esp_image: segment 4: paddr=0x00060020 vaddr=0x400d0020 size=0xd81a4 (885156) map
I (590) esp_image: segment 5: paddr=0x001381cc vaddr=0x400862f8 size=0x18d40 (101696) load
I (652) boot: Loaded app from partition at offset 0x20000
I (652) boot: Disabling RNG early entropy source...
I (652) cpu_start: Pro cpu up.
I (656) cpu_start: Application information:
I (661) cpu_start: Project name: switch
I (666) cpu_start: App version: 1.0
I (670) cpu_start: Compile time: May 28 2021 18:06:44
I (676) cpu_start: ELF file SHA256: e2b94aac47c04c6f...
I (682) cpu_start: ESP-IDF: v4.2.1
I (687) cpu_start: Starting app cpu, entry point is 0x400819f4
I (0) cpu_start: App cpu up.
I (698) heap_init: Initializing. RAM available for dynamic allocation:
I (705) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (711) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (717) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (723) heap_init: At 3FFC8AE0 len 00017520 (93 KiB): DRAM
I (729) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (735) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (742) heap_init: At 4009F038 len 00000FC8 (3 KiB): IRAM
I (748) cpu_start: Pro cpu start user code
I (766) spi_flash: detected chip: generic
I (767) spi_flash: flash io: dio
I (767) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (775) esp_rmaker_commands: Registering command: up-time
I (0) esp_rmaker_console: Initialising UART on port 0
I (785) uart: queue free spaces: 8
I (795) esp_rmaker_commands: Registering command: mem-dump
I (795) esp_rmaker_commands: Registering command: task-dump
I (805) esp_rmaker_commands: Registering command: cpu-dump
I (805) esp_rmaker_commands: Registering command: sock-dump
I (815) esp_rmaker_commands: Registering command: heap-trace
I (825) esp_rmaker_commands: Registering command: reset-to-factory
I (825) esp_rmaker_commands: Registering command: add-user
I (835) esp_rmaker_commands: Registering command: get-node-id
I (845) esp_rmaker_commands: Registering command: wifi-prov
I (845) esp_rmaker_commands: Registering command: local-time
I (855) esp_rmaker_commands: Registering command: tz-set
I (865) gpio: GPIO[0]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3
I (865) gpio: GPIO[19]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
W (875) ws2812_led: WS2812 LED is disabled
I (915) wifi:wifi driver task: 3ffcf1bc, prio:23, stack:6656, core=0
I (915) system_api: Base MAC address is not set
I (915) system_api: read default base MAC address from EFUSE
I (925) wifi:wifi firmware version: c44a5e7
I (925) wifi:wifi certification version: v7.0
I (925) wifi:config NVS flash: enabled
I (925) wifi:config nano formating: disabled
I (935) wifi:Init data frame dynamic rx buffer num: 32
I (935) wifi:Init management frame dynamic rx buffer num: 32
I (945) wifi:Init management short buffer num: 32
I (945) wifi:Init dynamic tx buffer num: 32
I (955) wifi:Init static rx buffer size: 1600
I (955) wifi:Init static rx buffer num: 10
I (955) wifi:Init dynamic rx buffer num: 32
I (965) wifi_init: rx ba win: 6
I (965) wifi_init: tcpip mbox: 32
I (975) wifi_init: udp mbox: 6
I (975) wifi_init: tcp mbox: 6
I (975) wifi_init: tcp tx win: 5744
I (985) wifi_init: tcp rx win: 5744
I (985) wifi_init: tcp mss: 1440
I (995) wifi_init: WiFi IRAM OP enabled
I (995) wifi_init: WiFi RX IRAM OP enabled
I (1015) esp_rmaker_work_queue: Work Queue created.
I (1035) esp_mqtt_glue: Initialising MQTT
I (1035) app_main: RainMaker Initialised.
I (1035) esp_rmaker_node: Node ID ----- nQ7UKXVcUkAF2eKkW38Vvf
I (1035) esp_rmaker_ota: OTA state = 2
I (1045) esp_rmaker_ota_using_params: OTA enabled with Params
I (1045) esp_rmaker_time: Initializing SNTP. Using the SNTP server: pool.ntp.org
I (1055) esp_rmaker_core: Starting RainMaker Work Queue task
I (1065) esp_rmaker_work_queue: RainMaker Work Queue task started.
I (1065) wifi_prov_scheme_ble: BT memory released
I (1075) app_wifi: Starting provisioning
I (1085) phy_init: phy_version 4660,0162888,Dec 23 2020
I (1185) wifi:mode : sta (fc:f5:c4:2f:12:b0)
I (1185) BTDM_INIT: BT controller compile version [a4c513b]
I (1195) phy_init: phy_version 4660,0162888,Dec 23 2020
I (1445) protocomm_nimble: BLE Host Task Started
I (1455) wifi_prov_mgr: Provisioning started with service name : PROV_83cc77
I (1455) app_wifi: Provisioning started
I (1455) app_wifi: Scan this QR code from the ESP RainMaker phone app for Provisioning.
GAP procedure initiated: advertise; disc_mode=2 adv_channel_map=0 own_addr_type=0 adv_filter_policy=0 adv_itvl_min=256 adv_itvl_max=256

█▀▀▀▀▀█ ▀▀▀█▄█ ▄▄██▀ █▀▀▀▀▀█
█ ███ █ ▀▄█ █▄ ▀▄▄█ █ ▀▀ █ ███ █
█ ▀▀▀ █ ▄▀█▀▄▀ ▀█ ▀▀█▄▄█ █ ▀▀▀ █
▀▀▀▀▀▀▀ █▄▀ █▄█▄█ ▀ ▀ █ █ ▀▀▀▀▀▀▀
██▄█▀ ▀▄ ▀▄ ▀▄ ▄▀▀▀██ ▀█▄ ▀▄▄ ▄▄▀
█ ▄█▀ ▀▀ ▀▀▀▀▄▄▀ ▀▀ █ ▄█▄█▀
▀▄█▀▀ ▀█▀██ ▄▄██▄ ▀▀▄ █ ▄▀█ ▀▄▄▀
█▀█▄▀▀▀ ▄█▀ ▄ ▄█▄▀▄█▄ ▄▀▄▄█ ▄
▀▀▀ █▀▄ ▄▀█▀▀ █▀▄▀▄▀ ▄█ ███▄ ██
▄ ▀ ▀▀▀▄██▄▀▄███ ▄▀█ ▀█ █▀▀ ▀▄▄▀
▄▄▀▀▀▄▀ ▀▀▀▄▄█▄▀▀█▄█▄█▀▀█ ▀▄ ▄▀
█ ▄▀██▀ █ ▄█▄ ▀█▄█▄▀▀█▀█ ▄█ ▀▄▄█
▀▀ ▀ ▀▀▀▄ ▄▀▀▄▄██▄█▀█ ▀██▀▀▀█▄▄▀
█▀▀▀▀▀█ ██▀▀▀██ ▄▀▄ █▄█ ▀ █ ▄ ▄
█ ███ █ █▄ ▄█▀▀█▀▄█▄▄ ▀██▀▀▀▀▄▄▀▀
█ ▀▀▀ █ ▄█ ▀ ▄█▀█ █▀ ▀▀███▄▀█ █▄█
▀▀▀▀▀▀▀ ▀▀▀▀ ▀▀ ▀ ▀▀▀▀▀▀


I (1675) app_wifi: If QR code is not visible, copy paste the below URL in a browser.
https://rainmaker.espressif.com/qrcode. ... port":"ble"}
I (1695) app_wifi: Provisioning Started. Name : PROV_83cc77, POP : 16895366
GAP procedure initiated: advertise; disc_mode=2 adv_channel_map=0 own_addr_type=0 adv_filter_policy=0 adv_itvl_min=256 adv_itvl_max=256

Moderator note: moved topic from ESP-IDF to ESP RainMaker forum

I see that your esp idf version is v4.2.1 for which we have indeed faced BLE related issues. Can you check and disable this config option if you see it as enabled?

idf.py menuconfig -> Component config -> Bluetooth -> NimBLE Options -> Enable Host Flow control (disable this)

I tried the above steps you provide on IDF v4.2.1 and now I am able to connect with wifi using QR code and also using BLE provisioning.
Thanks for resolving this bug on IDF 4.2.1.

I tried the above step as you provide and it is working fine. now I am able to connect to wifi through wifi and ble provisioning.

I tried this on switch example:
I load the code into the ESP32 device after power off-on, the status of the gpio is not retained and always it is low.
can you please point to any doc related to this?

By default, the power parameter only has read and write properties as you can see here. If you want the state to persist, create your own power parameter and add the PROP_FLAG_PERSIST property as well.