Can the Puck recieve an Eddystone-URL broadcast? #2196
Replies: 7 comments
-
Posted at 2017-04-26 by @gfwilliams Yes, it should be! You'll just have to decode the data to get the URL (or maybe not? You could just forward the data as-is).
|
Beta Was this translation helpful? Give feedback.
-
Posted at 2017-04-27 by intern Hi Gordon, thanks for your reply. I am currently testing out the Eddystone broadcasting function using the The code that i used is:
Will result in:
Interestingly enough, I saw your answer on another iBeacon question which uses the code below and it works on the puck with a packet size of 30 bytes:
Now I am not sure if this is a Puck issue or a Eddystone issue. Hope you can help me out. Thanks in advance :) |
Beta Was this translation helpful? Give feedback.
-
Posted at 2017-04-27 by @gfwilliams First, I'd say it looks like you might have an out of date Puck.js firmware? It'd be worth updating to 1v92 But I don't think that is your problem. Error 9 is 'invalid length' (which is reported as text on 1v92 firmware). It's actually saying that the data you're trying to send has the length field set wrong. Try changing: to: It should be the number of bytes that are after that byte. Also, do you know that if you want to use eddystone, there's a library which will do it all for you? http://www.espruino.com/Puck.js+Eddystone |
Beta Was this translation helpful? Give feedback.
-
Posted at 2017-04-28 by intern Hi, you are correct that my Puck is now still on 1v88. I didn't update it because I have some other projects in progress and I don't want to potentially affect them through updating. I changed Working: (31 bytes total)
Any further extension will result in BLE Error Code 9 but that is to be expected, I think. I am aware that the Eddystone library exists, but I am using this manual way to verify if the message can be maximum 31 bytes long. Now I am able to use
Many thanks for you help. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2017-04-28 by @gfwilliams I could be wrong here, but I think FEAA corresponds to the 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 |
Beta Was this translation helpful? Give feedback.
-
Posted at 2017-04-28 by intern 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
|
Beta Was this translation helpful? Give feedback.
-
Posted at 2017-04-28 by @gfwilliams Well, Google is your friend here I think - but if a for loop works for you, I'd use that :) |
Beta Was this translation helpful? Give feedback.
-
Posted at 2017-04-26 by intern
Hi all,
Since the Puck is capable of broadcasting a URL using the
NRF.setAdvertising()
function I was wondering if the Puck can recieve/read an Eddystone-URL broadcast by another Puck. My objective is to extend the range of the Puck Bluetooth broadcast.
An example is one Puck broadcast a URL which is received by another Puck close by, the second Puck then broadcast the same URL. Only the first Puck knows the URL, the rest just "propagates" the Bluetooth broadcast (something like a very basic Bluetooth Mesh)
Is this possible with the Puck hardware?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions