However, it seems that 1) always enables the duplicates filter, so only one advertisement for a given device is ever reported; meanwhile 2) can (after my recent patch) report all the advertisements, but disables device filtering - so userspace receives reports from all devices, not just those I care about, which seems inefficient. My question then is this - should my use case be implemented by a) extending HCI_AUTO_CONN_REPORT processing code to allow disabling the duplicates filter on request; b) extending the advertisement monitor interface to allow monitoring only specific devices; c) something else? Cheers, -- Anton Khirnov