The log on my v5-Shield is flooded with the following messages:
11:56:20 AM Warning
wifi:
11:56:20 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:20 AM
11:56:20 AM Warning
wifi:
11:56:20 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:20 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:21 AM Warning
wifi:
11:56:21 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:21 AM
11:56:22 AM Warning
wifi:
11:56:22 AM
[ADDBA]rx delba, code:37, delete tid:0
11:56:22 AM
11:56:22 AM Warning
wifi:
11:56:22 AM
[ADDBA]rx delba, code:37, delete tid:0
There does not seem to be any immediate impact, but I think it might cause issues with ebus-communication from time to time. This did not occur with a firmware nearly a year ago, but there was nothing specific in the changelog that caught my eye and I never opened a ticket here.
I'm using Huawei Enterprise-APs (specifically AirEngine 6761-21) and assume that they advertise certain IEs in their Beacon-Frames that the ESP doesn't like.
The log on my v5-Shield is flooded with the following messages:
There does not seem to be any immediate impact, but I think it might cause issues with ebus-communication from time to time. This did not occur with a firmware nearly a year ago, but there was nothing specific in the changelog that caught my eye and I never opened a ticket here.
Build: 20240330 Chip ID: dc5475bc3060, ESP32-C3, rev 4 Hostname: ebus-bc3060 PCB: 1.20.1 Build: 20240330 Flash: 4194304 IDF: v5.3-dev-2646-gb15cfab6f3-dirty Reset reason: 5 eBUS r/w: 8228348/297382 Host r/w: 653650/16098513 Up time: 352282 Free heap: 135840 / 275012 ebusd connected: yes (inactive) eBUS signal: acquired
I'm using Huawei Enterprise-APs (specifically AirEngine 6761-21) and assume that they advertise certain IEs in their Beacon-Frames that the ESP doesn't like.