ESP32 Forum

Hi -

I have projects with ESP32-WROOM-S3 and an ESP32-C3 Super Mini and neither are reliably connecting to my network. Like 1 out of 50 times they will connect. I have google fiber and I have 2 access points. I have both a 2.4GHz and a 5GHz network. The 2.5 and 5GHz networks have different SSIDs so I know I'm trying to connect to my 2.4GHz network. I have the security protocol set to WPA2. I am certain I am using the correct SSID and password. It works sometimes. I know my code is finding my network as I list it on the screen with its RSSI, Channel, and BSSID.

It "seems" to work better with one of the access points turned off, but even then, it is not very reliable. I have strong signal (25dBm) with my closest AP is on and 60dBm when its off. I've written code to try to force the higher signal strength ( WiFi.begin(ssid, password, ch, bssid, /*connect=*/true); ) . Nothing I'm doing is working.

What is odd is that this exact code "used" to work every time. I did switch to Google Fiber and it "may" be related to that, it's WiFi, or the multiple Access Points (I didn't used to have 2). I have always had 2.5GHz and 5GHz so I don't believe that is an issue.

I am now having the exact same issue with my ESP32-S3 and my ESP32-C3 where I didn't have these issues before. I've tried everything I can think of and that Co-Pilot can think of. Does anyone know of issues with Google Fiber WiFi or maybe their WPA2?

You say, "What is odd is that this exact code "used" to work every time"

Have you updated ESP or other supporting software in the mean time? If so, can you go back to the earlier software to see if anything has changed?

I had some network issues that were relieved by preventing the ESP WiFi software from sleeping.

Take a look at:
WiFi.setSleep(false);

Regards,

Andy

The ESP32 will show detailed connection information if you set core debugging to verbose. If you post that log, we may be able to help.

Interestingly enough, I'm having a similar issue with my WiFi connection for ESP32-S3. I'm switching WiFi networks too. Worked fine with the first one, not so great with the new one. Same code in both cases. Here's a link to my question (with code and logs): viewtopic.php?t=47692.

Communicated with ChatGPT: Found the reason:
- Serial Monitor. still open after the previous board test

What Is Happening
During upload:

IDE opens the COM port
Board resets
USB disconnects
Windows creates a new COM port
IDE still tries to use the old one


Closed Serial Monitor, and upload works!