Can the Puck recieve an Eddystone-URL broadcast?

You are reading a single comment by @Gordon and its replies. Click here to read the full conversation.

•

Gordon

I could be wrong here, but I think FEAA corresponds to the 170, 254 section of the advertising data, and is Google's Bluetooth UUID. So filtering on that will filter out everything except eddystone beacons, which could be what you want?

Filtering specifically on Puck.js devices could be more painful. I'd suggest maybe making your own URL shortener service - for instance if you shortened all your URLs using something like foob.ar/ee54ce5 then you could detect foob.ar and know that the beacon was one of yours.

•

intern in reply to @Gordon
Yea, I am trying to filter out all the other Puck devices transmitting using Eddystone format.

But now I am facing an issue of getting the data out, as the data is stored in the devices[i].data object. Now I am using a for loop to get each item in the devices[i].data object, then store it in another array. As I am not familiar with the js ArrayBuffer object.
```
new ArrayBuffer([3, 3, 170, 254, 26, 22, 170, 254, 16, 248, 3, 49, 50, 51, 52, 53, 54, 55, 56, 57, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75])
```

About

Avatar for Gordon @Gordon started