I have a simple WiFi sketch that scans and displays networks and then connects to one of them.

I have an esp32-s3 dev board (no name clone) that I have been using as an ESP NOW receiver for another project. The WiFi sketch no longer connects to the WiFI when I re-flash the WiFi sketch (it worked ...

Thanks; my understanding is that the sender will automatically retry failures a couple of times; I don't see any duplicates on the receiver, so I assume he is smart enough to realize he has already seen that message and just drops it.

It's failing again...


10:59:48.402 -> Sent OK
10:59:48.402 -> Sent OK
10:59:48.434 -> Send status: failed
10:59:48.434 -> Send status: success


10:59:48.861 -> Incoming lat: x.xx long: -y.yy mph: 0 sats: 8
10:59:48.861 -> From: 94:a9:90:1b:90:14


10:59:48.019 -> Incoming lat: x.xx long: -y ...

It's very strange; when I plugged both in yesterday morning, without having made any changes, it worked fine for a while, but later reverted to the strange behavior (I may have reset one or both before it started to fail).

However, I then added a second S3 receiver, running the identical code and ...

Hi; I have a simple one-way peer-to-peer app between 2 ESP32-S3s. I am only sending a few bytes and everything is working fine.

The sender sends a message every 10 seconds and the receiver gets it within a few milliseconds.

However, the sender callback always reports ESP_NOW_SEND_FAIL in the ...