Skip to content

Conversation

@earlephilhower
Copy link
Owner

There may be an issue in the CYW43 driver that causes a link to never be
reported as going down once it has connected, when it was disassociated or
when the wlan shuts off unexpectedly.

Work around it by clearing the internal link active in a TCP callback for
the CYW43 driver.

Reports disconnection properly now, as well as reconnection.

Fixes #762

There may be an issue in the CYW43 driver that causes a link to never be
reported as going down once it has connected, when it was disassociated or
when the wlan shuts off unexpectedly.

Work around it by clearing the internal link active in a TCP callback for
the CYW43 driver.

Reports disconnection properly now, as well as reconnection.

Fixes #762
@khoih-prog
Copy link
Contributor

@earlephilhower

I've tested and can confirm that WiFi.status() WL_CONNECTED is working OK now, with 5s delay from link drop / power off.
Auto-reconnect is working OK after powering on the AP.

@earlephilhower earlephilhower merged commit d019f31 into master Aug 20, 2022
@earlephilhower earlephilhower deleted the mandown branch August 20, 2022 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WiFi.status() wrongly reports WL_CONNECTED even when WiFi is lost and RSSI is always 0 dBm

3 participants