Bluetooth advertisements: different between BluetoothSensorTag and hcitool

We’re scanning for BLE devices using a modified BluetoothSensorTag app and also using hcitool. The two give different results. We see all of the devices with hcitool. With our simplified BluetoothSensorTag app, we see some devices, but not all. (We are not trying to treat these as sensor tags or to pair to them yet. We are only trying to discover them from their advertising data). We haven’t been able to identify any settings or configuration in the BluetoothSensorTag example that would cause this difference.
Any ideas?

Have you tried running bluetoothctl and then typing power on and then scan on? How do those scan results compare?

bluetoothctl does not show them.
These are BLE devices.
hcitool lescan shows them
hcitool scan does not show them
Is is possible to get the ‘lescan’ behavior in the BluetoothSensorTag app?

I had similar issue:

  • I can see my BLE device using “hcitool lescan” command.
  • I cannot see this device when scanning using “scan on” command with bluetoothctl tool.

But I discovered that enabling transport filter in scan menu of bluetoothctl solves this issue:

menu scan
transport auto
scan on

So maybe it is possible to do the same thing within the BluetoothSensorTag app in BeginSensorTagSearch() function by calling bluez_adapter1_call_set_discovery_filter_sync() before bluez_adapter1_call_start_discovery_sync()?