mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 00:55:52 +03:00
[GH-ISSUE #1018] WM fails to reconnect to known AP after wake up from sleep #866
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#866
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 @MauiKano on GitHub (Mar 7, 2020).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1018
I use the latest development branch, cloned it on March 7th 2020 with
git clone -b development https://github.com/tzapu/WiFiManager.git
HW is a LiLygo Wristband (https://github.com/Xinyuan-LilyGO/LilyGO-T-Wristband)
WM configuring works but when I send my HW to sleep and rewake it WM has issues with reconnecting to the know AP. It remembers credentials correctly however but fails back to the setup procedure with the access point in the ESP for initial configuration.
This is what I see of DEBUG messages:
@tablatronix commented on GitHub (Mar 7, 2020):
This looks like wifi is not initializing or has not had time to.
Do you get similar issues with plain sketch and starting wifi ?
E (26425) wifi: esp_wifi_disconnect 1153 wifi not start
*WM: [1] Connecting to SAVED AP: xxxxx
*WM: [3] Using Password: xxxxxxxxxx
*WM: [3] WiFi station enable
E (26506) wifi: esp_wifi_connect 1145 wifi not startp
@MauiKano commented on GitHub (Mar 8, 2020):
Shame on me: It actually happens only when I set
#define FACTORY_HW_TEST //! Test RTC and WiFi scan when enabled
Without that setting WiFi works as expected. I have not yet diged in to understand the difference. However. I have a work-around so this can be closed.