mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #1222] Recover connectivity after disconnection #1043
Labels
No labels
📶 WiFi
🕸️ HTTP
Branch
DEV Help Wanted
Discussion
Documentation
ESP32
Example
Good First Issue
Hotfix
In Progress
Incomplete
Needs Feeback
Priority
QA
Question
Task
Upstream/Dependancy
bug
duplicate
enhancement
invalid
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/WiFiManager#1043
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rhalaly on GitHub (Mar 6, 2021).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1222
I'm using the basic example code. But I've noticed that when the WiFi disconnected (router restart, out of range, etc.) the device doesn't try to reconnect to the network. And in order to reconnect I need to reboot the device manually.
Is there any way to implement retry mechanism? That will reconnect to the WiFi after disconnection or open AP if it fails?
@invidia191 commented on GitHub (Mar 10, 2021):
I have tried in loop to add:
WiFiManager wifiManager;
wifiManager.autoConnect();
This connects as AP, how are the saved values stored ?
@tablatronix commented on GitHub (Mar 10, 2021):
esp32 ?
@rhalaly commented on GitHub (Mar 10, 2021):
My original question is about ESP8266. I'm not sure if
wifiManager.autoConnect();should be placed in theloop... I just want a retry mechanism if any disconnection occurred (without opening AP again)@tablatronix commented on GitHub (Mar 10, 2021):
esp8266 should auto reconnect by default, so that is strange
@rhalaly commented on GitHub (Mar 10, 2021):
The basic example does not reconnect after I shut down my router for couple of minutes... (With esp8266)
The device is not reachable / detectable after the disconnection and there is no AP. I have to reboot the device and then it connects again...
@tablatronix commented on GitHub (Mar 10, 2021):
hmm works for me, how do you know you are not connected?
are you checking status ?
@rhalaly commented on GitHub (Mar 10, 2021):
Actually, I already put the chip in a way that I don't have direct access to it. But I cannot see it on my router and also the AP is not working. I also added an http server and it also not reachable (static IP)
I don't have access to it, but I can control the power supply (😈). So after a reboot with power down / up, it works again.
The firmware is the basic example with http server. Nothing more (I don't have anything on the
loop)@invidia191 commented on GitHub (Mar 10, 2021):
In my case, I have a ubidots connection in loop. I can not use the reconnection function from ubidots library because I need the saved wifi values.
@askarkurymbayev commented on GitHub (Mar 11, 2021):
good day! I also ran into this problem, after turning off / turning on the electricity, the ESP8266 starts first, and the router after a couple of minutes after charging, in this regard, the esp8266 does not find the network and goes into AP mode, you can delay the search for your network in a couple of minutes so that the router has time turns on and esp8266 is connected?
@tablatronix commented on GitHub (Mar 11, 2021):
well the ap only starts when you call it, you dont want it starting all the time, it wont start automatically
Add a delay in your loop and see if it changes, perhaps wifi needs some time to run
I can turn my router on and off indefinetly and my esp8266 reconnects everytime, If its not you need to have debugging and see what the failure modes are, perhaps your router is not allowing reconnect or something is wrong with your esp lib version
@askarkurymbayev
That is a totally different issue than that being discussed here
@tarontop commented on GitHub (Mar 16, 2021):
The problem I encountered is the same as you. I used non-blocking. How can I reconnect to Wi-Fi without restarting ESP8266?
@chrisncc1701 commented on GitHub (Mar 16, 2021):
my problem is my router port keeps closing after hours or days making the esp8266 unavailable externally, but i can log on locally port 80 and this reopens the router port, otherwise i have to reboot the esp, is this the same issue
@tablatronix commented on GitHub (Mar 16, 2021):
hmm sounds like something else is not restarting, sounds like a different issue or a routing issue.
@tarontop commented on GitHub (Mar 17, 2021):
After the power is off (the ESP8266 and the router are both powered off), the router takes about 2 minutes to start up. The ESP8266 is first started and the router has not been started. The ESP8266 judges that there is no Wi-Fi available and automatically enters the AP mode. I have to restart the ESP8266 Will connect to the router. How can I connect to the router without restarting the ESP8266?
@tarontop commented on GitHub (Mar 17, 2021):
I added wifiManager.setConnectTimeout(120); it seems to have no effect, in fact it is only about 54 seconds, how can I make him wait for 120 seconds
@tablatronix commented on GitHub (Mar 17, 2021):
Let me check
@tablatronix commented on GitHub (Mar 17, 2021):
Fixed in master, sorry about that func was passing as uint16!