Hi!
You don't have to modify the library to get this working. The following works for me: You can declare a callback function for the web server, which is called when the portal is started. In this method, you can add (or change!) routes on the web server inside the WiFiManager library. If you change the base route (just "/") then you can deliver whatever HTML (even a file, if you use the SPIFFS or similar file system library) as a custom default landing page.
There is a quirk I've noticed on this, though. If you do "replace" the base route of the WiFiManager, then (for some reason) the corresponding handle method is repeatedly being invoked -- this can be seen if you Serial.println something. Not sure if this is a problem though.
Code: Select all
WiFiManager wifiManager;
void bindServerCallback(){
wifiManager.server->on("/", handleSetupRoute); // overwrite/replace existing/default route
wifiManager.server->on("/test", handleTestRoute); // add new route
}
void setup() {
wifiManager.setWebServerCallback(bindServerCallback);
}
void handleSetupRoute(){
String data = "<html><body><h1>Hello World!</h1></body></html>";
wifiManager.server->send(200, "text/html", data);
}
void handleTestRoute(){
String data = "<html><body><h1>Something else</h1></body></html>";
wifiManager.server->send(200, "text/html", data);
}
