You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like Sniffle automatically paused itself after receiving an AUX_ADV_IND in initiator mode.
From my crude estimation, this happens around half of the time (occasionally initiator.py does emit LL data packets indicating successful connection).
I'm in an environment with lots of BLE devices, probably a lot of these are constantly emitting ADV_EXT_* packets, while my Flipper seems to broadcast once every ~2 seconds, so is this behavior expected?
Any help much appreciated!
The text was updated successfully, but these errors were encountered:
What's happening is that Sniffle sends a CONNECT_IND but the other side fails to receive it, so a connection doesn't start. The initiator script does not retry connecting if the first attempt fails.
I've stumbled upon a very similar issue to #87 except that, when trying to connect to a Flipper Zero, this is all I get (no LL traffic):
Looks like Sniffle automatically paused itself after receiving an AUX_ADV_IND in initiator mode.
From my crude estimation, this happens around half of the time (occasionally initiator.py does emit LL data packets indicating successful connection).
I'm in an environment with lots of BLE devices, probably a lot of these are constantly emitting ADV_EXT_* packets, while my Flipper seems to broadcast once every ~2 seconds, so is this behavior expected?
Any help much appreciated!
The text was updated successfully, but these errors were encountered: