[GH-ISSUE #1488] ESP32S3 wifi not broadcasting during AP mode #1272

Closed
opened 2026-02-28 01:29:21 +03:00 by kerem · 1 comment
Owner

Originally created by @shashi5841 on GitHub (Sep 10, 2022).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1488

Tested with esp32-s3 with the same issue.
ESP32-S3 with WiFiManager lib.

Can't find SSID AutoConnectAP, when the module is in AP mode.

Terminal output:

SPIFFS mounted
*wm:[1] AutoConnect
*wm:[2] ESP32 event handler enabled
*wm:[2] Connecting as wifi client...
*wm:[2] setSTAConfig static ip not set, skipping
*wm:[1] Connecting to SAVED AP: espressif
*wm:[1] connectTimeout not set, ESP waitForConnectResult...
*wm:[2] [EVENT] WIFI_REASON: 201
*wm:[2] [EVENT] WIFI_REASON: NO_AP_FOUND
*wm:[2] Connection result: WL_NO_SSID_AVAIL
*wm:[1] AutoConnect: FAILED
*wm:[2] Starting Config Portal
*wm:[2] Disabling STA
*wm:[2] Enabling AP
*wm:[1] StartAP with SSID: AutoConnectAP
*wm:[2] AP has anonymous access!
*wm:[1] AP IP address: 192.168.4.1
*wm:[1] Starting Web Portal
*wm:[2] HTTP server started
*wm:[2] Config Portal Running, blocking, waiting for clients...
*wm:[2] NUM CLIENTS: 0
*wm:[2] NUM CLIENTS: 0
*wm:[2] NUM CLIENTS: 0
*wm:[2] NUM CLIENTS: 0

I used 4 different mobile phones and different laptop PC to find esp32s3 in the WiFi list but the module was not broadcasting.

Used the latest library of WiFi manager v2.0.12-beta

Please advise what to do ??

Originally created by @shashi5841 on GitHub (Sep 10, 2022). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1488 Tested with esp32-s3 with the same issue. ESP32-S3 with WiFiManager lib. Can't find SSID AutoConnectAP, when the module is in AP mode. Terminal output: SPIFFS mounted *wm:[1] AutoConnect *wm:[2] ESP32 event handler enabled *wm:[2] Connecting as wifi client... *wm:[2] setSTAConfig static ip not set, skipping *wm:[1] Connecting to SAVED AP: espressif *wm:[1] connectTimeout not set, ESP waitForConnectResult... *wm:[2] [EVENT] WIFI_REASON: 201 *wm:[2] [EVENT] WIFI_REASON: NO_AP_FOUND *wm:[2] Connection result: WL_NO_SSID_AVAIL *wm:[1] AutoConnect: FAILED *wm:[2] Starting Config Portal *wm:[2] Disabling STA *wm:[2] Enabling AP *wm:[1] StartAP with SSID: AutoConnectAP *wm:[2] AP has anonymous access! *wm:[1] AP IP address: 192.168.4.1 *wm:[1] Starting Web Portal *wm:[2] HTTP server started *wm:[2] Config Portal Running, blocking, waiting for clients... *wm:[2] NUM CLIENTS: 0 *wm:[2] NUM CLIENTS: 0 *wm:[2] NUM CLIENTS: 0 *wm:[2] NUM CLIENTS: 0 I used 4 different mobile phones and different laptop PC to find esp32s3 in the WiFi list but the module was not broadcasting. Used the latest library of WiFi manager v2.0.12-beta Please advise what to do ??
kerem 2026-02-28 01:29:21 +03:00
  • closed this issue
  • added the
    duplicate
    label
Author
Owner

@tablatronix commented on GitHub (Sep 10, 2022):

#1482

<!-- gh-comment-id:1242751906 --> @tablatronix commented on GitHub (Sep 10, 2022): #1482
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/WiFiManager#1272
No description provided.