search

google / eddystone

Specification for Eddystone, an open beacon format from Google
Apache License 2.0
3.07k stars 761 forks source link

Nearby Notifications not giving a standard result #243

Open akshay0297 opened 6 years ago

akshay0297 commented 6 years ago

I have been trying to use Google Beacon Platform's Nearby Notification using multiple web url's and multiple app intents. At first I used to receive the last modified or added notification but after few tries I am getting randomized notifications i.e. either web url's notification or app intent notification whenever I turn on the Bluetooth in my device. Is there a valid reason like, if is there fixed duration for a particular notification for this or is it the beacon's fault ?

Targeting rule is set to default for all entries.

Could anyone help me with this?

Thank You in advance :)

helenclarko commented 6 years ago

It is my understanding that the beacons only broadcast one attached message at a time, unless it is set up to broadcast multiple protocols (e.g. eddystone-URL and Eddystone-UID) in which case it is possible to have two things broadcast at once.

Some devices allow for multiple broadcast slots and can have eddystone-UID set up in multiple slots. You then register each slot to Google beacon platform as a separate device.

It sounds like you have eddystone-UID set up with multiple attachments (URL and intent), but because only one can be broadcast at a time it is randomly pulling an attachment each time.

Setting a target will allow you to set a time and date for broadcast, it may help.

akshay0297 commented 6 years ago

Setting a target should help.

Thank You @helenclarko