![]() It is a bit complicated to explain this in detail (something something math), but suffice it to say, these weird intervals work better. The smart people at Apple recommend that you set your advertising interval to one of these odd-looking numbers: 152.5 ms, 211.25 ms, 318.75 ms, 417.5 ms, 546.25 ms, 760 ms, 852.5 ms, 1022.5 ms, or 1285 ms. In addition, you could also try inputting a more optimal broadcast interval into the beacon. This would use more beacon battery power. You could lower the broadcast interval of the beacon to 500ms or 300ms or even 100ms. This would use more battery power on your smartphone. (I think there are some issues created by the iPhone iOS also, such that the scan interval and window time is different when the app is in the foreground or background). The app maker could increase its scan window or decrease its scan interval. If the app’s scan interval is set to 1000ms and the scan window is 100ms long, that leaves 900ms of time when the beacon broadcast could be missed by the app. In order for this to be “seen” by the app, the app has to be scanning for beacons at that exact moment. So that means that the beacon will send out it’s broadcast every 1000ms (i.e. Let’s say you set it at the default 1000ms. The beacon broadcasts it’s little UUID message according to the beacon’s configured interval. The reason why you are getting alerts when you shouldn’t is because the app thinks the beacon is gone. They seem like smart people (or at least a lot smarter than me!) But I think they will eventually work it out. I also saw this same issue mentioned in Reddit. I think the Pushcut app is a bit underdeveloped in terms of beacon functionality at this point.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |