Skip to content
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

Investigate WiFi Manager callbacks for webserver / mDNS autostart after captive portal success #1

Closed
mwood77 opened this issue Feb 2, 2023 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@mwood77
Copy link
Owner

mwood77 commented Feb 2, 2023

Winderoo must be physically reset after successfully connecting to a user's WiFi network; this is inconvenient.

Investigate whether a callback exists that can trigger the webserver & mDNS to start after successfully changing wifi networks.

@mwood77 mwood77 self-assigned this Feb 2, 2023
@mwood77 mwood77 added the bug Something isn't working label Feb 2, 2023
mwood77 added a commit that referenced this issue Feb 5, 2023
@mwood77
Copy link
Owner Author

mwood77 commented Feb 5, 2023

b583128

...
wm.setSaveConfigCallback(saveWifiCallback);

void saveWifiCallback() {
  // Slow blink to confirm success & restart
  for ( int i = 0; i < 6; i++ ) {
    digitalWrite(LED_BUILTIN, HIGH);
    delay(500);
    digitalWrite(LED_BUILTIN, LOW);
    delay(500);
  }
  ESP.restart();
}

@mwood77 mwood77 closed this as completed Feb 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant