-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v5.3 of ESP-IDF reports notably lower RSSI than v5.1 (IDFGH-13966) #14797
Comments
@mbratch |
@zhangyanjiaoesp Did you try it? This seems something you can easily verify. |
@mbratch |
@zhangyanjiaoesp thank you very much for the prompt reply and the information regarding internal testing. I did not perform a deep sleep, and my test process was not very formal but just observational looking at an RSSI indicator that I defined and my units under test (I have four of them) are stationary in a test setup. Of course, with wifi, there are natural fluctuations, and I tried to take that into account. But based upon your comments, I suspect perhaps I didn't capture enough data over a period of time to firmly determine what is going on. I will run more tests when I have the opportunity. |
Answers checklist.
IDF version.
v5.3.1
Espressif SoC revision.
Chip is ESP32-PICO-V3 (revision v3.0)
Operating System used.
Windows
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
PowerShell
Development Kit.
ESP32 Dev Kit 1
Power Supply used.
USB
What is the expected behavior?
After upgrading my ESP-IDF to v5.3.1 (from v5.1), I would expect to see no significant change in RSSI readings if the wifi environment hasn't changed.
What is the actual behavior?
After upgrading my ESP-IDF to v5.3.1 (from v5.1), what I see is that the RSSI reported by ESP-IDF using the
esp_wifi_sta_get_ap_info
function is significantly lower after the upgrade. Specifically, the RSSI with v5.1 was between -70 and -60. After the upgrade to v5.3.1 it dropped to between -127 and -80.Steps to reproduce.
Debug Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: