Crash on D1 mini and NodeMCU during WiFi initial provisioning

Lol that’s awesome, don’t want to upset to pooch :slight_smile:

To get the esp32 more sensitive we can disable active scanning and adjust the scan window and interval to be equal. That might help catch the adverts more frequently.

do you mean to have an ESP32 environment that support ethernet ?

Ok, do they come up as decoded in the OMG MQTT messages, or just a raw manufacturerdata/servicedata?

Depending on the above I would also suggest to fork the Decoder and remove as many decoder included as not necessary to not wast any processing time going through all the possible, but not really possible in your case, decoders. That together with a white-list of of the MAC address(es) of the beacons, disabling the active scanning, as @h2zero mentioned above, and it should probably also make the esp32 ble continuous scanning version a lot more responsive for your use case. If not, it would still also be advantageous for the ESP8266 version, as the reduced decoder should free up enough memory to run smoothly.