Answers checklist.
General issue report
Hello everyone,
I am working through the RainMaker getting-started exercises and have encountered persistent issues with the provisioning process. I would appreciate any guidance or solutions.
Here is my detailed setup and the problems I'm facing:
My Environment:
OS: Windows 11
IDE/Platform: Visual Studio Code with the official ESP-IDF extension
ESP-IDF Version: v5.3.1
Target Device: ESP32-C3
Project Used: The official led_lightexample from the ESP RainMaker repository.
Provisioning Transport: Configured as BLE (CONFIG_APP_WIFI_PROV_TRANSPORT_BLE=y).
Flashing Process: I consistently perform a full flash erase using idf.py erase-flashbefore each new flash to rule out residual data issues.
The Problems:
QR Code Provisioning Failure:
When I attempt to provision the device using the QR code generated in the serial monitor, the RainMaker app fails with the error: "Failed to get Wi-Fi scan list".
The device itself seems to start the SoftAP for provisioning correctly, but the app cannot retrieve the list of available Wi-Fi networks from it.
BLE Provisioning Association Failure:
If I try to provision directly via BLE (without the QR code), the initial BLE connection and "Proof of Possession" (PoP) step appear successful.
However, the process consistently fails at the subsequent stage where the node association is finalized. The device logs indicate a successful BLE connection, but the app reports a failure in completing the node association.
Troubleshooting Attempted:
I have reviewed the official ESP RainMaker documentation but have not found a solution that resolves these specific errors.
Questions:
Has anyone encountered similar "Wi-Fi scan list" failures during QR code provisioning with ESP32-C3 and IDF v5.3.1?
Are there known issues with BLE node association in the current RainMaker SDK that require specific configuration changes?
Could this be related to the Wi-Fi or BLE driver configuration on the ESP32-C3? Any suggestions for further debugging would be greatly appreciated.
Thank you for your time and help


sdkconfig.txt
log.txt
Answers checklist.
General issue report
Hello everyone,
I am working through the RainMaker getting-started exercises and have encountered persistent issues with the provisioning process. I would appreciate any guidance or solutions.
Here is my detailed setup and the problems I'm facing:
My Environment:
OS: Windows 11
IDE/Platform: Visual Studio Code with the official ESP-IDF extension
ESP-IDF Version: v5.3.1
Target Device: ESP32-C3
Project Used: The official led_lightexample from the ESP RainMaker repository.
Provisioning Transport: Configured as BLE (CONFIG_APP_WIFI_PROV_TRANSPORT_BLE=y).
Flashing Process: I consistently perform a full flash erase using idf.py erase-flashbefore each new flash to rule out residual data issues.
The Problems:
QR Code Provisioning Failure:
When I attempt to provision the device using the QR code generated in the serial monitor, the RainMaker app fails with the error: "Failed to get Wi-Fi scan list".
The device itself seems to start the SoftAP for provisioning correctly, but the app cannot retrieve the list of available Wi-Fi networks from it.
BLE Provisioning Association Failure:
If I try to provision directly via BLE (without the QR code), the initial BLE connection and "Proof of Possession" (PoP) step appear successful.
However, the process consistently fails at the subsequent stage where the node association is finalized. The device logs indicate a successful BLE connection, but the app reports a failure in completing the node association.
Troubleshooting Attempted:
I have reviewed the official ESP RainMaker documentation but have not found a solution that resolves these specific errors.
Questions:
Has anyone encountered similar "Wi-Fi scan list" failures during QR code provisioning with ESP32-C3 and IDF v5.3.1?
Are there known issues with BLE node association in the current RainMaker SDK that require specific configuration changes?
Could this be related to the Wi-Fi or BLE driver configuration on the ESP32-C3? Any suggestions for further debugging would be greatly appreciated.
Thank you for your time and help
sdkconfig.txt
log.txt