initiator.py receives ADV_EXT_IND and pauses itself, no connection made

[zh5j]

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):

TRANSITION: INITIATING from STATIC

Timestamp: 0.239126  Length:  9  RSSI: -74  Channel: 37  PHY: 1M  CRC: 0x870E87
Ad Type: ADV_EXT_IND
ChSel: 0 TxAdd: 1 RxAdd: 0 Ad Length: 7
AuxPtr Chan: 29 PHY: 1M Delay: 2760 us
AdvMode: Connectable
AdvDataInfo DID: 0x614 SID: 0x0
0x0000:  47 07 46 18 14 06 5d 5c  00                       G.F...]\.

TRANSITION: PAUSED from INITIATING

(stays here forever...)

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!

[sultanqasim]

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.

[XenoKovah]

@wuzhongjie1997 see ticket #103 for some code which may possibly work for attempting retries. LMK if it works for you, since currently it only works for me when running from macOS, not Linux.