-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WifiProv BLE doesn't auto connect Wifi after initial provisioning #9943
Comments
@mhendriks - add this line at the end of |
void setup() {
Serial.begin(115200);
WiFi.onEvent(SysProvEvent);
Serial.println("Begin Provisioning using BLE");
WiFiProv.beginProvision(
WIFI_PROV_SCHEME_BLE, WIFI_PROV_SCHEME_HANDLER_FREE_BTDM, WIFI_PROV_SECURITY_1, pop, service_name, service_key, NULL, reset_provisioned
);
WiFi.begin();
} |
@SuGlider thanks for the hint.
BTW In 3.0.2 the WifiProv works even less well. |
I'm testing it here with 3.0.2. If there is no You say that it doesn't always work. |
thanks for the clarification. |
I also set the Arduino IDE option |
We are sharing the same thoughts ... use I did a couple of tests with the 3.0.2. The WiFi.begin() should be called before the WifiProv in order to work properly. With the 3.0.1 the WiFi.begin() could be after the WifiProv but with the 3.0.2 this should be before. Many thanks for the solution / hints and swift reply! |
see #9946 |
Board
ESP32-S3-DEV-Module
Device Description
Start at #8760 the WifiProv example doesn't work properly.
After the initial BLE provisioning the Wifi isn't setup and the proces stops.
Before this commit (BIG Network refactoring) it is working fine. The problem still exists in version 3.0.1
Hardware Configuration
Version
v3.0.0
IDE Name
Arduino IDE
Operating System
macos latest
Flash frequency
80MHz
PSRAM enabled
no
Upload speed
115200
Description
After successful provisioning the wifi connection isn't started.
Only a reboot is or disconnect+start will setup the Wifi connection.
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: