# Bluetooth advertisements: different between BluetoothSensorTag and hcitool

**URL:** <https://mangoh.discourse.group/t/bluetooth-advertisements-different-between-bluetoothsensortag-and-hcitool/3182>\
**Category:** mangOH Yellow\
**Created:** [December 13, 2019, 10:33pm UTC](https://mangoh.discourse.group/t/bluetooth-advertisements-different-between-bluetoothsensortag-and-hcitool/3182 "2019-12-13T22:33:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gjames](https://avatars.discourse-cdn.com/v4/letter/g/7cd45c/32.png) [@gjames](https://mangoh.discourse.group/u/gjames)\
**Post date:** [December 13, 2019, 10:33pm UTC](https://mangoh.discourse.group/t/bluetooth-advertisements-different-between-bluetoothsensortag-and-hcitool/3182/1 "2019-12-13T22:33:38Z")

</div>

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?  
Thanks

---

<div class="post-metadata">

**Author:** ![dfrey](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/dfrey/32/303_2.png) [@dfrey](https://mangoh.discourse.group/u/dfrey)\
**Post date:** [December 16, 2019, 5:24pm UTC](https://mangoh.discourse.group/t/bluetooth-advertisements-different-between-bluetoothsensortag-and-hcitool/3182/2 "2019-12-16T17:24:40Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![gjames](https://avatars.discourse-cdn.com/v4/letter/g/7cd45c/32.png) [@gjames](https://mangoh.discourse.group/u/gjames)\
**Post date:** [December 16, 2019, 9:03pm UTC](https://mangoh.discourse.group/t/bluetooth-advertisements-different-between-bluetoothsensortag-and-hcitool/3182/3 "2019-12-16T21:03:11Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Jay](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jay/32/46_2.png) [@Jay](https://mangoh.discourse.group/u/Jay)\
**Post date:** [January 30, 2020, 3:53pm UTC](https://mangoh.discourse.group/t/bluetooth-advertisements-different-between-bluetoothsensortag-and-hcitool/3182/4 "2020-01-30T15:53:52Z")

</div>

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:

```auto
menu scan
transport auto
back
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()`?