23
My attempt at locating my iPhone from my Pebble Watch using Bluetooth Latency (It didn't work) (programming.dev)
submitted 7 months ago by to c/programming@programming.dev
8 comments fedilink hide all child comments
 

Just wanted to share an idea I had, in order to hope that another developer learns from my lessons, and hopefully either finds a work around or a better solution to this problem.

I wanted to find out if it was possible to locate your iPhone from your watch based on the latency of Bluetooth messages, since RSSI (signal strength) isn't available. I made a simple app, and started sending messages back and forth between my phone and app.

After much testing, the conclusion is no. Mostly because Bluetooth is amazing and the average latency for a message is 58-62ms. And because as Erik pointed out... apple just sucks.

I am hopeful PebbleOS can be updated to see RSSI or the app can expose the notification api to the PebbleKit JS.

If anyone want me to publish my code, let me know.

The raw data is here if you want to see it: https://docs.google.com/spreadsheets/d/1Yr5XX0CXh5TifsnW3yOp10ZoaA_xx0q189f_fG8rMTU/edit?usp=sharing

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 3 points 7 months ago

The issue is:

  1. PebbleKit JS - doesn't have access to the sound or vibration motor on iOS. Since Apple blocks that functionality unless it's directly interacted with via the user

  2. PebbleKit iOS - Might pull it off but you'll need a separate app on the App Store, however the Pebble watches are just Bluetooth so no guarantee that you'll get a reading.

  3. iOS Apps are $100/year to keep up, and for that functionality... not worth it.

There are already apps which do this on Android and works without issue.

  • permalink
  • fedilink
  • source
  • parent