# True support for non-connected BLE beacons

**URL:** <https://community.thunkable.com/t/true-support-for-non-connected-ble-beacons/1231898>\
**Category:** Feedback\
**Created:** [April 18, 2021, 10:48pm UTC](https://community.thunkable.com/t/true-support-for-non-connected-ble-beacons/1231898 "2021-04-18T22:48:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zimbu-bcb](https://avatars.discourse-cdn.com/v4/letter/z/6a8cbe/32.png) [@zimbu-bcb](https://community.thunkable.com/u/zimbu-bcb)\
**Post date:** [April 18, 2021, 10:48pm UTC](https://community.thunkable.com/t/true-support-for-non-connected-ble-beacons/1231898/1 "2021-04-18T22:48:06Z")

</div>

Hi Thunk,

Love the platform so far. But I really need it to support BLE **beacon** functionality. That means that it should be able to scan for beacons, and show their **advertised** info packet (UUID, Major, Minor, Name, MAC, measured RSSI, etc.). This must be achievable WITHOUT a connection to the beacon.

Beacons are supposed to be one way communication, like a lighthouse, not requiring a connection…hence the name “Beacon”. I know that many users are using BLE modules for two way communication of small data packets WITH a connection. That’s great, and it’s needed too, but it is not the same as **scanning and reading advertisement packets from beacons** (e.g. iBeacons).

Thanks,

Zimbu

---

<div class="post-metadata">

**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\
**Post date:** [November 8, 2024, 1:25pm UTC](https://community.thunkable.com/t/true-support-for-non-connected-ble-beacons/1231898/2 "2024-11-08T13:25:07Z")

</div>


