mirror of
https://github.com/tzapu/WiFiManager.git
synced 2026-04-27 09:05:56 +03:00
[GH-ISSUE #1438] AP loss causes WiFi scan sync to not start. #1228
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#1228
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 @OekoSolveMG on GitHub (Jun 22, 2022).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1438
Basic Infos
Hardware
WiFimanager Branch / Release: v2.0.11-beta
Esp8266 / Esp32: ESP32
Hardware: M5 Stack Core 1
Core Version: 2.4.0, staging
Description
When being connected to a WiFi and then loosing the access point. Then reopening the captive portal and connecting wifi causes only 2 textboxes to appear and the scan sync is not started and the other wifi signals we could connect to are not shown.
Would it be possible to show all the possible wifi signals in this case as well, or have it be an option that could be enabled via. a boolean flag and a set method.
@tablatronix commented on GitHub (Jun 22, 2022):
hmm are you using ondemand to start the ap or a reboot?
Got any serial logs by chance?
@OekoSolveMG commented on GitHub (Jun 22, 2022):
OnDemand and non blocking
There isn't any error so no not really.
I'm pretty sure this isn't a bug, because it seems like if you click the configure wifi button the wifi_no_scan callback is called. That's why I meant it more as a feature request.
Because in my opionion it would make more sense to also show all available networks even if you were already connected to one and are now disconnected from it or to make it settable via a boolean flag.
@tablatronix commented on GitHub (Jun 22, 2022):
Yeah sounds like a bug in non blocking, let me test it