Hacker News new | past | comments | ask | show | jobs | submit login

Except that EVERYTHING interferes with a low powered btle signal. Hold your phone with an unobstructed view of an ibeacon, then put almost anything between you and it, your rssi will drop like a stone. Especially bad when it's your body between the antenna and receiver.

'iBeacon' is great for very general and very localized location finding, but you're going to have a very hard time triangulating your location very precisely in say a department store.




You are quite correct, however Apple have very sensibly been very conservative in what accuracy of distance estimation they provide to apps. The only distance values provided are: CLProximityUnknown, CLProximityImmediate, CLProximityNear, CLProximityFar. These correlate reasonably well with the type of information that can be usefully derived from RSSI (i.e., you're next to the cash register, you're in/next to the shop, you're close to the shop).


Sure but those are also highly variable. I built a test installation in a retail environment using about 15 beacons setting up four different types of zones. One of which was an attempt to do a 'tap your phone here interaction' (CLProximityImmediate trigger). The Beacon for that interaction was behind a piece of foamcore.

Now I'm not a radio engineer, it may be that it was too many beacons for the area or the general wireless soup was high but it could sometimes take 20-30 seconds to see that beacon as immediate with your phone sitting smack dab on it. Sometimes 1sec. (iOS7.0 on both ipod touch 5thgen and iphone 5 devices) . Perhaps the filtering they use just needs to be tweaked a bit.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: