Beacon Launcher

[Gordon Meyer]

Sounds like good sleuthing. I have had to contend with a similar iBeacon problem, which is logically dealing with multiple events of the same type. Since the iBeacon is pinging at a regular interval the logic to make sure that “here” and “still here” are correctly handled was one of my earliest frustrations. (A later frustration was, and is, needing multiple beacons in the home and making sure they all agree before taking any action. Two might think I’m gone, but until they all think I’m gone, noting happens.)  —Gordon 


> On Jun 19, 2015, at 3:22 PM, Thomas Arman <tarman at me.com> wrote:
> 
> Thanks Gordon,
> 
> But the Estimote is settable for 100ms -> 2 sec announcement interval, but the app seems to be insensitive to changing that.
> 
> Two other apps on the Mac seem to see it “come and go” also, so I don’t think it is that app itself.  More likely it is something in OS X (maybe?).
> 
> I have three Estimote iBeacons and they all “come and go” to the Mac.
> 
> Digging deeper into the “Core Bluetooth Programming Guide” from Apple, I see that "All Bluetooth-related events that occur while a foreground-only app is in the suspended state are queued by the system and delivered to the app only when it resumes to the foreground.”
> That said, Core Bluetooth provides a way to alert the user when certain central role events occur.  
> 
> I suspect these apps are foreground only and wake up every ten seconds????
> 
> Tom
> 
>> On Jun 19, 2015, at 12:14 PM, Gordon Meyer <bb at g2meyer.com> wrote:
>> 
>> My guess is that the Estimote isn’t pinging frequently enough, so that app is assuming it has exited.  I don’t have that particular brand, but if it lets you set the rate, maybe drop it down from 10 seconds.  —Gordon
>> 
>> 
> 
> _______________________________________________
> XTensionList mailing list
> XTensionList at shed.com
> http://shed.com/mailman/listinfo/xtensionlist