-
-
Notifications
You must be signed in to change notification settings - Fork 95
[realtek-amb] Use Wi-Fi partial scan to fix delays, add watchdog resets #346
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
Conversation
|
before
Lot better now and no watchdog resets on the bad case |
|
just need to boot it off the wifi and make sure it can still scan |
|
all good, reconnects to a different bssid when I reboot the ap |
|
looks like we have a bug in ESPHome on scan after forced disconnect 🙈 |
|
reconnect scan bug in esphome fixed as well esphome/esphome#13514 |
|
The |
|
compiles ok with esphome:
name: wr2-test
friendly_name: WR2 Test
rtl87xx:
board: wr2
framework:
version: 1.10.0
source: /Users/bdraco/libretiny
logger:
level: VERBOSE
api:
ota:
- platform: esphome
debug:
update_interval: 5s
sensor:
- platform: debug
free:
name: "Free Heap"
min_free:
name: "Min Free Heap"
loop_time:
name: "Loop Time"
text_sensor:
- platform: debug
reset_reason:
name: "Reset Reason"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
ap:
But don't have the hardware to validate on |
Fix WiFi connection delays and watchdog resets on Realtek
Some users have been experiencing watchdog resets during WiFi connection. After investigating, found that
wifi_connect_bssid()was scanning all channels even when we already know the target channel from the prior scan.Changes
wifi_set_pscan_chan()to limit the SDK's internal scan to just the target channel when knownBefore/After
Connect time dropped from ~2.8s to ~1.5s, total blocking from ~4s to ~2s. The watchdog feeds ensure no single blocking period exceeds ~1.5s.