@Peter_Kawa Without being fluent in Javascript, my understanding of it leads me to believe this code sets a counter to 0 for each Beacon. The app will increment this number for each scan where it does not see the beacon, and if it reaches your preconfigured number, the beacon is determined to not be in range anymore. By default, being in range for one scan will reset the counter back to 0, reporting it as present again.
There should be no reason why this call to reset the counter couldn’t be made through the API, as long as the app somehow allows it.
That said, one could also repeat the bluetooth signals in a way such as perhaps the one you’re mentioning. It seems a bit overengineered for the purpose, however, when the goal is just to reset a counter and trigger associated effects.
This, essentially, is the function I want to call on a given device:
Hey! I’ve just bought a Tile Pro 2022, but can’t find it in the Beacon app.
Since I live in an apartment, the beacon finds 20-40 devices where you can’t tell what it is based on the name. Any idea how to tell which device is my Tile, or should the name be easily identified if detected?
Downloaded the Tile app on my phone and activated the Tile.
Put the tile in “Hide” and closed the app.
Turned off Bluetooth on my phone.
Downloaded the Beacon app on Homey
Tried to find beacon, which doesn’t seem to be present. (Tile is sitting right next to Homey)
I’ve tried multiple combinations of uninstalling the Tile app from my phone, restart the beacon app in Homey, enable/disable bluetooth on my device, removing batteries from the tile and so on without any success…
Anyone with a Tile 2022 who can give me some help/tips?
Has anyone here figured out way to detect a beacon instantly? Reliably under 3 seconds after the beacon appears in the range of the signal.
Via this app or any other method.
Would the following use case work?
I.e. add stationary device that works as beacon rather than the HomeyPro?
What I intend to do;
Stationary Beacon (e.g. USB powered) installed in 2 different rooms of the house.
Beacons paired with my iPhone and added as two separate devices in Homey Pro.
HomeyPro Beacon app would trigger separate flow depending on which room I enter? (Assuming TX is lowered to few meters so not to trigger when in adjacent room)
Would that be supported, as long as iBeacon standard is supported by the beacons?
Though all the other issues/questions regarding this app, I would like to come back to the still existing and unsolved respectively problem with the instability of Homey’s bluetooth function/protocol - without overdoing so.
As mentioned several times before, it definitely seems to be a general issue affecting Homey’s core functionality, therefore I’m still in contact with Athom’s support team.
Although not 100% prooved (a finally answer/response is left), the following observations may exclude any app-related issues with bluetooth protocol and the failured detection of the beacon. (@Koktail: Thank you very much again for your invested time and efforts in this awesome, delightful app. And to not leave it by words, could you contact me with a pm to share your Paypal/Bank details (I’m not a Paypal user) for a donation? Thanks!)
In the last weeks and months I carried on trying to find any possible reason for the suddenly stopped discovery and recognition of the beacon. It was just strange, that the last actualization of beacon’s status was always some hours ago, as I checked it in the mornings, although the beacon was the whole night long at the same spot.
So, even not really relevant at my first sight, I tried the following: our WiFi router switch off the WiFi signal every night (0 until 6 o’clock) according to the configured timetable for several reasons, f.e. to reduce the radition exposure at night, when WiFi isn’t indeedly necessarily.
I deactivated the WiFi timer, so the WiFi signal is on aorund the clock…and after that, the bluetooth (not WiFi!!!) connection of Homey with my beacon kept on until the next morning, and isn’t disconnected anymore (see also attached screenshot). That means the beacon is detected as soon as it is in reach of Homey.
As summary: There must be an interference and dependence respectively between the WiFi and bluetooth protocol of Homey.
In the meantime, Athom confirmed me regarding this that Bluetooth and WiFi are incorporated into a single chip (at least due to HP 2019).
As told above, a final response, especially a appropriate firmware update, is still left.
If you’re interested, I’ll keep you up to date in this topic. And maybe you made similar experiences affecting the dependence of Homey’s WiFi and bluetooth.
Not sure if it’s mentioned already, but bluetooth, wifi 2.4 & zigbee use the same 2.4GHz band.
Changing the 2.4GHz wifi channel might improve ble signal quality.
When zigbee is also used, possibly it’s channel should be adjusted as well.
Thanks for your immediate feedback and the considerations about eventual correlationsand interferences among these wireless protocols, which weren’t mentioned in this topic as far as I know.
I’m aware at least about the same frequencies of bluetooth and WiFi, although not relevant for this issue: The WiFi-signal was switched off, and therefore didn’t cause any interferences.
Did you mean this?
I am using your application for some time now and I noticed that whenever I restart the beacon application or when the Homey restarts or when the Homey is updated, the following setting is reset to the default value.
Can you please make the setting “Delay between reading sensor values in seconds” to not been overeaten when the application is restart or the homey is restarted.
And to not leave it by words, could you contact me with a pm to share your Paypal/Bank details (I’m not a Paypal user) for a donation? Thanks!)
