-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Checklist
- Checked the issue tracker for similar issues to ensure this is not a duplicate
- Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
- Tested with the latest version to ensure the issue hasn't been fixed
How often does this bug occurs?
always
Expected behavior
I'm honestly not sure if this is the right place to start, but it is something that is different...
Once connected, I expect to see *_WIFI_STA_GOT_IP followed by *_CONNECTED
Instead I receive WL_IDLE_STATUS
I'm utilizing the Arduino-Core framework (3.1.1 atm) and WiFiClientEvents.ino example (with additional WiFi.status in main loop()):
Actual behavior (suspected bug)
With an ESP32-S3, the Wifi will transition through the following states:
Output via
Wait for WiFi...
[WiFi-event] event: 112
Connected to access point
[WiFi-event] event: 115
Obtained IP address: 192.168.1.100
WiFi connected
IP address:
192.168.1.100
(now in in loop())
[INFO] WiFi Status: WL_CONNECTED
[INFO] WiFi Status: WL_CONNECTED
...
Same code with an ESP32-P4:
Wait for WiFi...
[INFO] WiFi Status: WL_DISCONNECTED
[WiFi-event] event: 112
Connected to access point
(now in in loop())
[INFO] WiFi Status: WL_IDLE_STATUS
[INFO] WiFi Status: WL_IDLE_STATUS
...
Error logs or terminal output
Steps to reproduce the behavior
WiFiClientEvents.ino example
Project release version
Hard to tell what's packaged in Arduino Core...
System architecture
Intel/AMD 64-bit (modern PC, older Mac)
Operating system
Windows
Operating system version
Win 11
Shell
ZSH
Additional context
No response
Metadata
Metadata
Assignees
Labels
No labels