You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On ESP-A, when using the latest code in main based on ESP32 board library 3.0.5, channels 12 & 13 are taking around 300ms to scan each (around 3x longer than configured) whereas other channels complete in around 110ms which matches the configured scan time.
I dropped back to 2.0.16 with the same code to see how it performed, and noticed that channel 12 & 13 scans complete in an average of 15ms, indicating it likely didn't scan at all.
Confirmed the behavior on 2 different devices. Verbose logging on both 3.0.5 & 2.0.16 show no issues with the scans.
Configured scanning of channel 14 which also took ~300ms per scan.
When limiting the scanning to only channels 1-11, all scans took the expected amount of time indicating this is a channel-specific issue.
The text was updated successfully, but these errors were encountered:
On ESP-A, when using the latest code in
main
based on ESP32 board library 3.0.5, channels 12 & 13 are taking around 300ms to scan each (around 3x longer than configured) whereas other channels complete in around 110ms which matches the configured scan time.I dropped back to 2.0.16 with the same code to see how it performed, and noticed that channel 12 & 13 scans complete in an average of 15ms, indicating it likely didn't scan at all.
Confirmed the behavior on 2 different devices. Verbose logging on both 3.0.5 & 2.0.16 show no issues with the scans.
Configured scanning of channel 14 which also took ~300ms per scan.
When limiting the scanning to only channels 1-11, all scans took the expected amount of time indicating this is a channel-specific issue.
The text was updated successfully, but these errors were encountered: