mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 00:55:52 +03:00
[GH-ISSUE #455] setTimeout not working #386
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#386
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 @thubaggins on GitHub (Nov 14, 2017).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/455
Hi,
I'm using ESP-12E with wifimanager 0.12
I try to config portal timeout to 60 seconds but it doesn't work.
When timeout reach wifimanager still in portal, please check this!
@tablatronix commented on GitHub (Nov 14, 2017):
Are any clients connecting to the AP ?
@thubaggins commented on GitHub (Nov 14, 2017):
No matter clients connected to the AP or not portal still doesn't restart to enter station mode.
I just wonder why ESP-32 fork for ESP-32 work fine!
@tablatronix commented on GitHub (Nov 14, 2017):
esp32 branch is just a clone of master , nothing has been committed to it.
@tablatronix commented on GitHub (Nov 14, 2017):
I noticed sometimes if a client connects, the esp8266 does not update clientlist if they leave. I think this is fixed in the latest SDK and core. rc2, have not tested it though.
@thubaggins commented on GitHub (Nov 14, 2017):
No I used this fork: https://github.com/zhouhan0126/WIFIMANAGER-ESP32
Not sure what happened but maybe sdk or esp8266 hardware cause issues?
@tablatronix commented on GitHub (Nov 14, 2017):
I doubt it, this probably introduced a bug #308
Your esp thinks a client is connected to the ap , and will not timeout.
Would be my guess
@thubaggins commented on GitHub (Nov 15, 2017):
But I have no client connected to the AP for sure!
I don't know why esp8266 just stuck in AP mode when esp32 work fine.
--edit: esp after timeout has run into my code, but still have AP mode but not accessible. I think esp stuck in AP+STA mode instead of STA mode only.
@tablatronix commented on GitHub (Nov 15, 2017):
Yeah thats a known bug, ap persists you will have to workaround it by setting mode in your code after wifimanager is used.
@thubaggins commented on GitHub (Nov 15, 2017):
I’ll try it, but wonder why esp32 work when esp8266 is not!
@tablatronix commented on GitHub (Nov 15, 2017):
because that code was removed
@tablatronix commented on GitHub (Nov 15, 2017):
If i had to guess, something is wrong with
wifi_softap_get_station_num()and it is not returning 0 when no clients.@tablatronix commented on GitHub (Nov 15, 2017):
I have not seen that issue, but I did have problems with it not dropping to 0 after a client disconnected.
But you say a client is not connecting, it it possible a client is autoconnecting with saved credentials ? Try changing ap name or something. I am curious. I WIll have to fix this since its buggy
@thubaggins commented on GitHub (Nov 15, 2017):
I’m using only one laptop connect to the AP. I’m sure my laptop doesn’t connect to the AP cause I tured off automatically connect in windows 10!
Any chance to improve wifi_softap_get_station_num() Function?
@tablatronix commented on GitHub (Nov 15, 2017):
I added debugging to my dev PR, so it will output some debugging. I do not see any problem yet.
Feel free to test
@thubaggins commented on GitHub (Nov 16, 2017):
Where is your PR :)
@tablatronix commented on GitHub (Nov 16, 2017):
Oh i thought i pasted it lol
https://github.com/tzapu/WiFiManager/pull/313
@thubaggins commented on GitHub (Nov 17, 2017):
As I said before, startConfigPortal() set WiFi mode to STA+AP cause root problem esp won't reset after timeout reach. I try to change WiFi mode in startConfigPortal() to AP only then everything working property.
Your PR it's work, because function startAP() set WiFi mode to AP!
Also I've add some debug message:
@tablatronix commented on GitHub (Nov 17, 2017):
Cant reproduce,
When you say it stays on , is it actually on, or is this a dup or #457
Where AP is persistent after config, but configportal is not actually running ?
Does autoconnect ever return or exit ?
How are you testing this?
use the autoconnect example, it clearly outputs
@thubaggins commented on GitHub (Nov 18, 2017):
Yes, I think this is a duplicate of #457
AP won't shutdown and configportal actually not running. Change WiFi mode to AP and problem solved!
WiFi.mode(WIFI_AP);@tablatronix commented on GitHub (Nov 18, 2017):
Thats kind of strange I wonder what the actual issue is though. Seems like it is working around one of the many bugs. The main problem i had was persistent toggling so ap mode didnt get stored in memory, softapdisconnect bugs.
@tablatronix commented on GitHub (Nov 18, 2017):
Also my pr only disables sta if its not connected so not sure if this is still an issue
@SadafShafi commented on GitHub (Jan 14, 2019):
ehy...i tried using
if (!wifiManager.autoConnect()) {
Serial.println("failed to connect and hit timeout");
but it when kept watch on serial monitor, the loop never ends.......therefore never prints failed to connect.......what should i do now...???
@tablatronix commented on GitHub (Jan 14, 2019):
This issue is closed and old