Internet of Things: This Week’s Top Posts

Getting Geeky with Bluetooth LE
Getting Geeky with Bluetooth LE

There’s something new on the Internet of Things every week – from Bluetooth LE wrist bands for kids, to shareable bike locks that you run on your phone, to sprinklers that know the weather.

But the news of the week was Android. And with Radius Networks seemingly leading the charge, we’re seeing strong evidence that the world’s largest phone OS won’t be left behind by Apple in embracing iBeacon and Bluetooth LE technology.

Privacy and security concerns are being addressed on both sides of the ‘pond’ and in the meantime I’m proposing we think of a Bill of Rights for Toasters.

But Whose Beacons Can We See?
But most of the week seemed like it was spent trying to figure out: who can see my beacons? And while I started off assuming that there must be a simple hack to let iOS apps see beacons that aren’t your own, it doesn’t look like that’s possible (while Android has no such problem).

But while Android can “see” beacons that aren’t its own, there still seems to be something misleading in the claim: because if a beacon is set to ‘private’ and require pairing, I’m not sure in that case what seeing really means (and assume it will be device-dependent). Android might be able to see the random Proximity UUID but if it’s random, does it matter? The discussion continues.

Here’s this week’s top posts:

iBeacons, Apple and Android: Is Google Hijacking Your Bluetooth LE?
iBeacons: Can My iOS App Find Beacons That Aren’t Mine?
Virtual Worlds and the Internet of Things
Estimote: Stumbling or Thriving with Success?
iBeacon for Android: Radius App Helps You Discover and Test Beacons

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>