# \[APP\]\[Pro\] Beacon - Detect your presence with BLE beacons

**URL:** <https://community.homey.app/t/app-pro-beacon-detect-your-presence-with-ble-beacons/3550>\
**Category:** Apps\
**Tags:** app, tools, homey-pro\
**Created:** [November 1, 2018, 5:45pm UTC](https://community.homey.app/t/app-pro-beacon-detect-your-presence-with-ble-beacons/3550 "2018-11-01T17:45:20Z")\
**Posts on this page:** 1\
**Showing post:** 877

<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:** [March 28, 2024, 12:47am UTC](https://community.homey.app/t/app-pro-beacon-detect-your-presence-with-ble-beacons/3550/877 "2024-03-28T00:47:16Z")

</div>

I guess it’s not allowed to actually _set_ the value of a beacon, you’d want to _get_ the value.  
But why, als long if it’s state is not undetected, it’s state is detected? Thats how most things work with Homey.

But maybe I get you wrong.  
You can consider to send a local webhook from the rpi to Homey;  
and update the yes/no field of an advanced virtual device with that

> [@\[APP\]\[Pro\] Advanced Virtual Device (Device Capabilities App) with Unique Text Status Indicator](https://community.homey.app/t/app-pro-advanced-virtual-device-device-capabilities-app-with-unique-text-status-indicator/68198/1):
>
> `let dcApp = await Homey.apps.getApp({id:'nl.qluster-it.DeviceCapabilities'});`
> 
> # Added an API call to set the **value** of AVD fields:
> 
> `await dcApp.apiPost('setvalue', {device:'Day-Amount', field:'number1', value:21});`
> 
> `await dcApp.apiPost('setvalue', {device:'Day-Amount', field:'measure_devicecapabilities_number-custom_1.number1', value:22});`
> 
> `await dcApp.apiPost('setvalue', {device:'c34dc5b4-3c30-48a9-8a4e-014aea93d00d', field:'measure_power', value:501});`

---

_[View the full topic](https://community.homey.app/t/app-pro-beacon-detect-your-presence-with-ble-beacons/3550)._