[GH-ISSUE #1732] Question: Is there a way to detect if the WiFi connection is successful before the config portal closes? #1470

New issue

Open

opened 2026-02-28 01:30:12 +03:00 by kerem · 1 comment

kerem commented

2026-02-28 01:30:12 +03:00

Owner

Originally created by @ateker01 on GitHub (Apr 6, 2024).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1732

I have an app that tries to detect if the connection is successful after the password is saved. Basically,

ESP8266 starts the ondemand config portal
When user enters the password and hits the "save" button the URL changes to 192.168.4.1/wifisave
At that point my app understands that the password was entered

if the password is correct, the config portal closes
if the password is incorrect, the config portal restarts

is there way for the app to detect if 8266 was able to connect to the wifi before config portal closes? for example if the URL has changed to 192.168.4.1/wifisucess or wififailed, the app could detect it.

Originally created by @ateker01 on GitHub (Apr 6, 2024). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1732 I have an app that tries to detect if the connection is successful after the password is saved. Basically, ESP8266 starts the ondemand config portal When user enters the password and hits the "save" button the URL changes to 192.168.4.1/wifisave At that point my app understands that the password was entered if the password is correct, the config portal closes if the password is incorrect, the config portal restarts is there way for the app to detect if 8266 was able to connect to the wifi before config portal closes? for example if the URL has changed to 192.168.4.1/wifisucess or wififailed, the app could detect it.

kerem commented

2026-02-28 01:30:12 +03:00

Author

Owner

@real-bombinho commented on GitHub (Apr 28, 2024):

Did you find a solution?

If the portal closes successfully then ESP should have migrated to the new network and you are unlikely to get a response from 192.168.4.1 unless by accident this is the new IP too.

Your app would need to identify the new IP of the ESP. You might need to add a way to ping your app from the ESP after reconnection.

@real-bombinho commented on GitHub (Apr 28, 2024): Did you find a solution? If the portal closes successfully then ESP should have migrated to the new network and you are unlikely to get a response from 192.168.4.1 unless by accident this is the new IP too. Your app would need to identify the new IP of the ESP. You might need to add a way to ping your app from the ESP after reconnection.