Unfortunately I’m restarting regularly but since 04/2021 I see the highest peak was 34MB - so still below 40MB - but it’s nice contrast with Flora app, where I have 6 Flora sensors and it’s still running on ~9MB, compared to Beacon app, where I have just two “dummy” sensors - kettle and boiler detection. While Flora app mem utilization remains almost stable, Beacon is going from very nice initial value of 7.4MB to ~34MB.
Hi Sharkys. Could not find anything strange in the logging.
The big difference between the beacon app and other BLE apps is that this app is using the discovery mechanism to detect BLE devices. So from a technical perspective the issue is pointing in that direction.
Because I didn’t find any other cause, and the BLE discovery is Homey core firmware I cannot do anything about it. And the stacked memory that is allocated is freed by the garbage collector anyway after some time. And the memory doesn’t exceed the prescribed maximum values.
I bought the Feasycom Beacon as @Piero_F wrote, it adds up as an iBeacon. I’m still playing with the settings now, as there were a few false alarms overnight. However the distance from Homey is not working at all. Settings so far are 15, 1, 20.
I have been using Feasycom FSC-BP108 for over a year and I very satisfied.
Since Feasycom is a beacon that can be used in many environments and systems, you need to set the most suitable parameters for Homey. You should install the Feasycom app in your smartphone in order to set the interval of transmitted signal to 760 ms and the signal strength (TxPower) to 2.5 dB (a complete guide for setting beacon parameters can be found here).
Thanks a lot!
I didn’t know about that, it still has to be set up sideways in the app. I’ll try to play around with it a bit and hopefully it will be better. I found out that one beacon has the option of two iBeacons in the settings. Each has a different UUID. I thought I had added both to Homey, but yet it was just one keychain with two UUIDs
Since my partner bought a new phone, we constantly had problems with his presence. I bought him a Tile Pro 2022 and installed this app. Works like a charm! A big thank you to the maker and to the posters of the various info in this topic, necessary to get things working.
I intend to switch from homee to homey in 2023.
Not everyone in the family has a cell phone in their pocket all the time, so the geofancing story doesn’t work for us.
I am successfully using three Gigaset G-Tags (version1) with a raspberry pi zero as a BLE scanner/server. The notification to homee takes place via webhook. homeean presence
The G-Tags have good reception in the home, the message comes as soon as I drive into the carport.
I hope this works with the homey-pro (2023) as well,
and without additional raspi?
because the presence function of Homey itself still doesn’t work properly, I decided to manage the presence/away status by a beacon. So at this point, I would like to thank @Koktail for this awesome and quite helpful app. I really appreciate your efforts and time you’ve invested in the developement and given support for it. (i will suit the action to the words when I’m familiar with the app functionality )
I don’t want to overdo this topic at all (it’s still long enough), but I want to share a simple as confusing experience with you:
as mentioned above, there’s no duty to register the beacons. This is why I didn’t installed the musegear-App on my smartphone. Instead of this, I tried to add the beacon directly to Homey. I knew, that it’s public discoverable, because my smartphone was able to detect it as a generic BLE device.
I tried several attempts to add it to Homey. But it didnt’t function.
Than, the only thing I did was to restart Homey (not the beacon-app itself) - and suddenly my beacon was founded. And never lost its connection until now for around 10 hours. So far, so good.
But know I’ve got an issue very similar to other user, especially to Peter_Kawa. This is the reason, why I wanted to reply to his post for asking for a solution, because I’ a little bit unsure about the right seetings (I didn’t changed the default ones).
As you can see on the screenshot, regularly after 20-25 seconds, the outside range status is changed in inside status. In the meantime, the beacon was moved only in direct range of Homey (not outside of our house).
Sorry…just one more question from me as a newbe:
What’s the difference between an Beacon and a iBeacon? I didn’t find any explanations on this question by searching the topic.
I’m asking this question myself, because I want to rule out of course, that I added the wrong type of beacon to Homey.
I just red something about random addresses as an advertising signal from some beacons. And I was wondering, if mine is such one (see screenshot as follows). Even because of its default name iTrack
finally, I found time to answer: thank you so much for your both quick and especially very kind response!
It’s really helpful while logical, although I didn’t tried out yet. But this is what I’ll do next, maybe in combination with a higher verification amount outside range. I figured out in the meantime, that 15 times seems to be the best - just at the moment.
Since I’ve been a (still proud ) owner of a Homey Pro (early 2019) I’m regularly excited about this huge community of Homey users. In my opinion, one of the strengths of Homey, among others.
But nevertheless: at this point, I can absolutely agree with @NoX comments about Homey’s usability und Athom’s policy: Beacon - An app for presence detection using BLE beacons - #608 by NoX
I invested 399 € as well in this futuristic “wonderball”, and for that, we can expect a stable system with it’s general functions. Herefore belongs e.g. the Bluetooth connectivity in general. (By the way, even my wife told me some days ago, I should not spend more time in configurating our smart home as it will save us in the end:grimacing:)
But I don’t want to start a new discussion about it though, that’s not the right place for it.
Just to clarify and intensify the awareness, I think about reporting one more issue for that to Athom.