Advertising Device not showing up in Wireshark nrFSniffer toolbar Device Drop down list

[jstafford]

I am using a raspberry pi that is running a NUS service. The PacketList in Wireshark shows the advertising packets from the device, but the device is not showing up in the Wireshark nRFSniffer toolbar Device drop down list.

The PDU type is ADV_IND which I though would flat the device to be in the drop down list. However, I did notice in the Advertising Data, there is no flag element (AD Type 0x01).

Is this element required in order for the nRF sniffer to monitor a connection? 

Packet Info in Packet List

No.	Time	Source	PHY	Protocol	Length	Delta time (us end to start)	RSSI (dBm)	Info
968	3.983	Raspberr_68:97:12	LE 1M	LE LL	9	939	-45	ADV_IND

The Packet Details are

Frame 967: 35 bytes on wire (280 bits), 35 bytes captured (280 bits) on interface 0
    Interface id: 0 (\\.\pipe\wireshark_extcap_COM4_20181107122233)
    Encapsulation type: Nordic BLE Sniffer (186)
    Arrival Time: Dec 31, 1969 16:00:04.579066000 Pacific Standard Time
    [Time shift for this packet: 0.000000000 seconds]
    Epoch Time: 4.579066000 seconds
    [Time delta from previous captured frame: 0.002663000 seconds]
    [Time delta from previous displayed frame: 0.002663000 seconds]
    [Time since reference or first frame: 3.981319000 seconds]
    Frame Number: 967
    Frame Length: 35 bytes (280 bits)
    Capture Length: 35 bytes (280 bits)
    [Frame is marked: False]
    [Frame is ignored: False]
    [Protocols in frame: nordic_ble:btle:btcommon]
	
Nordic BLE Sniffer
    Board: 4
    Header Version: 1, Packet counter: 2961
        Length of header: 6
        Length of payload: 28
        Protocol version: 1
        Packet counter: 2961
        Packet ID: 6
    Length of packet: 10
    Flags: 0x01
        .... ...1 = CRC: OK
        .... ..0. = Direction: Slave -> Master
        .... .0.. = Encrypted: No
        .... 0... = MIC: Only relevant when encrypted
        .000 .... = PHY: LE 1M (0)
        0... .... = RFU: 0
    Channel: 38
    RSSI (dBm): -49
    Event counter: 0
    Delta time (µs end to start): 3606
    [Delta time (µs start to start): 3982]
	
Bluetooth Low Energy Link Layer
    Access Address: 0x8e89bed6
    Packet Header: 0x0900 (PDU Type: ADV_IND, ChSel: #1, TxAdd: Public)
    Advertising Address: Raspberr_68:97:12 (b8:27:eb:68:97:12)
    Advertising Data
        Tx Power Level
            Length: 2
            Type: Tx Power Level (0x0a)
            Power Level (dBm): 12
    CRC: 0x61e561

[jstafford]

I have got nRFSniffer to show   the Raspberry P in the Device drop down list which allowed me to track the connection by removing the (packet.crcOK and not packet.direction) from the conditional statement used to add a device to Devices  in SnifferCollector.py.  

Note: used beta-2