# Preventing BLE beacon from entering low-power mode

**URL:** <https://community.homey.app/t/preventing-ble-beacon-from-entering-low-power-mode/144376>\
**Category:** Questions & Help\
**Created:** [October 21, 2025, 5:59pm UTC](https://community.homey.app/t/preventing-ble-beacon-from-entering-low-power-mode/144376 "2025-10-21T17:59:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![galbin1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/galbin1/32/121041_2.png) [@galbin1](https://community.homey.app/u/galbin1)\
**Post date:** [October 21, 2025, 5:59pm UTC](https://community.homey.app/t/preventing-ble-beacon-from-entering-low-power-mode/144376/1 "2025-10-21T17:59:24Z")

</div>

Hello

I just bought two BLE beacons from Feasycom as I read they are stable when integrated in Homey.

However, at the moment I am unable to create flows based on beacon presence, whether it is inside or outside the range. This is due to what I assume is the beacon entering low-power mode, so the beacon is constantly switching between inside and outside of range every few minutes.

Any idea how I can change this setting in Homey? It would be good if the beacon was detected as inside range as long as the device is at home. I understand this will affect battery life, but that’s a sacrifice I’m willing to make.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [October 21, 2025, 10:30pm UTC](https://community.homey.app/t/preventing-ble-beacon-from-entering-low-power-mode/144376/2 "2025-10-21T22:30:39Z")

</div>

Welcome!

If you use the Beacon app, please use the Beacon app topic for your questions.  
You’ll find links to these app topics on the app page at the app store.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 22, 2025, 6:02am UTC](https://community.homey.app/t/preventing-ble-beacon-from-entering-low-power-mode/144376/3 "2025-10-22T06:02:00Z")

</div>

The issue is more likely Homey’s ~~crappy~~ suboptimal BLE implementation.

Apps can only discover BLE devices _that are currently being seen_, and since beacons are not visible (not broadcasting their advertisements) most of the time, it’s going to be a hit or miss if Homey will be able to see the beacon.

That could be improved _somewhat_ by increasing how often the beacon emits its advertisements (if that were even possible, and I’ve never seen a beacon that makes this configurable), but it will still be very easy to miss.

What the Homey SDK (and therefore its apps) lacks is a way to send a notification to an app as soon as a device is being seen. That way, the app doesn’t have to poll periodically, with a high chance of missing devices.