Handle network_driver: Unhandled wifi event: 21. #1100
Comments
|
This could also be due to the beacon interval used by the router, if it is set for a longer than normal time, or itself is suffering degraded performance due to congestion, may exaggerate this problem. And as you point out, it could be poor RSSI, which, compounded with a longer beacon interval could trigger this callback if just a single beacon ping is missed. |
|
I looked closer at |
|
cc @arpunk - whom I believe reported it on telegram.. |
|
@UncleGrumpy @petermm this only happened to me during that session and haven't seen that log warning again, but I agree that instead of |
|
The |
|
My mistake... I was accidentally looking error codes and not event codes 🤦🏾♂️. The unhandled wifi event 21 is indeed |
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
|
PR #1137 adds a handler and a configurable (optional) STA mode callback for the |
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Adds an event handler for `event 21` the `WIFI_EVENT_STA_BEACON_TIMEOUT` event
and an option to add an Erlang callback handler for the event. The event will
be logged with an info level message that includes a suggestion about the two
most likely causes, poor rssi and network congestion. A callback config option
`{beacon_timeout, fun()}` may be added to the `sta` config.
Closes atomvm#1100
Signed-off-by: Winford <winford@object.stream>
Address several ESP32 network driver issues These changes close the following issues for the ESP32 network driver: * [#643] When network:stop/0 is used the driver is now completely stopped and all resources are freed. * [#1100] Adds a configurable event handler for STA beacon timeouts (Event: 21). * Fixes several possible cases of double free() when using network:start/1. These changes are made under both the "Apache 2.0" and the "GNU Lesser General Public License 2.1 or later" license terms (dual license). SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later
repeatedly.. on a C3card - most likely poor Rssi..
Solution:
Silently handle it - as there already is the
wifi:bcn_timeout,ap_probe_send_startlogor
gracefully log "bcn_timeout: Potentially weak wifi signal", or better wording.
The text was updated successfully, but these errors were encountered: