How can i register EID-frame beacon with beacon tools app? or something else? - eddystone

I have two beacons which support eddystone. One of them broadcasts only EID-frame, and another beacon broadcasts only UID-frame.
I see only UID-frame beacon on beacon tools app and i can register uid-frame to google proximity api via beacon tools app.
But i can't register eid-frame beacon.
Because Even if i see the eid-frame beacon by other apps or altbeacon library, beacon tools app doesn't show eid-frame beacon.
I want to register eid-frame beacon to google proximity api.
How can i register EID-frame beacon with beacon tools app? or something else?

To be able to see and register your Eddystone EID beacon in Beacon Tools app, you need to have the same service ECDH key (you can find more details here).
But if you want just scan for the nearby Eddystone EID beacons, you can use some SDKs that has EID support, like this.
Hope, it helps. Please let me know if you have any further questions!

In addition, if you want to scan for nearby Eddystone EID beacons, you can also use a 3-rd party app like this one.

Related

Using Beacon as a locating device in retail

how to detect beacon signal and do we need to make any app to manage it or any predefined app or site is available?
I want to know how Beacon works and which Beacon is suitable for retail.
You need a mobile phone with Bluetooth 4.0 to detect beacons. They emit a BLE signal which is a little different from the normal Bluetooth signal. There are many generic apps in the play store and maybe in the app store to detect them.
But if you are looking for real functionality related to that, then you'll be needing the retail store-specific mobile app so that it can show you relevant updates in the app.

Can I detect proximity between two beacons?

I'm currently study BLE Beacon. I know that with Google Beacon API and its app, it is possible to know when the beacon communicates with my mobile phone, so I can design different notifications based on the proximity. But in my case, I need to know the proximity between a wearable beacon to a stable beacon. Is that possible at all?
Two challenges to doing this:
Google Beacon APIs do not provide proximity information beyond a beacon being visible at all (regardless of distance) to a mobile phone.
Beacons are generally speaking one way transmitters. You cannot use a beacon to listen for another beacon.
To make something like this work you need one of the two devices (either fixed or mobile) to be a beacon scanner, not a beacon. You could make a beacon scanner out of a fixed Raspberry Pi 3 which would detect the beacon wearables and calculate the distance to them. This is an approach I have helped multiple clients implement.

cant register beacon on beacon tools

Every time I try to register the beacon on the google beacon tools app on andriod I add the location but it does not seem to let me register it, The register beacon text is greyed out. Is there any way to register the beacon?
I suspect that you are trying to register an Eddystone-URL (or maybe Eddystone-EID) beacon. The Beacon Tools App will only let you register iBeacon or Eddystone-UID beacons. It will detect some other types of beacon broadcasts, but only supports these two frame types. I have seen this in the Beacon Tools App, that when I detect an Eddystone-URL broadcast, I can touch on it, but "Register Beacon" is greyed out.
Here you can see that Google says to use Eddystone-UID (or EID, but that setup is more complicated). And here they say that iBeacon is also supported for Nearby Notifications.
It may be you have already register that beacon to other project.
If not, then create one project on Google API Console.
And select your project on Beacon Tools App and then proceed.
Your beacon must be configured as Eddystone. otherwise Beacon Tools App will not detect.
try it
As #David said, if you used Eddystone URL, the register option on beacon tools would be greyed out.
But only enabling Eddystone UID would not work for me either, because beacon tools would not recognize my beacon at all. What I did to make this work was to enable both iBeacon and Eddystone UID during configuration.
After you register your beacon on beacon tools, you need to refresh the "registered" list to see it appears there. Or go to the Google developer dashboard of your project.

Unable to register locked Google Beacon on Beacon Tools Android application

I was trying to register a Google Beacon using the Beacon Tools Android app. However, on tapping "Register as Ephemeral ID", I get the following message:
I'm wondering if there is a way to get the password. As far as I know, this beacon was never used or registered.
Any help would be appreciated.
Thanks!
what kind of Beacons are you using? Depending on the manufactor they may have a special function to become unlocked. I'm using Beacons from Beaconinside and they have a small button on the circuit board that I have to press when I want to configure them. To register such a Beacon with EID I need to press the button and afterwards I have to enter 32 '0' into the "Unlock Beacon" dialog.
You should ask the manufactor of your Beacons for more details.

Can I make iPhone/iPad broadcast as Eddystone Beacon?

We can make iOS devices act as a iBeacon transmitter and We can locate nearby iBeacons if we know their Proximity UUID.
With Google's Proximity Beacon API, It's possible to configure and register real Beacon hardware, and we can locate them with Nearby Messaging API.
But is it possible to make iOS devices to broadcast as Eddystone Beacons ? And it needs to be discoverable by apps that scan Eddystone beacons.
Thanks in advance.
Unfortunately, this is not possible. While iOS devices can advertise Bluetooth LE service advertisements(which are the advertisement type used by Eddystone) using CoreBluetooth APIs, you cannot attach the necessary data. This is because the CBAdvertisementDataServiceDataKey that associates service data to an advertisement is read-only on iOS. You can't set the data.
So while you want to make the iOS device advertise something like this to transmit Eddystone-UID:
0201060303aafe1516aafe00e72f234454f4911ba9ffa6000000000001
You end up advertising something like this:
0201060303aafe0316aafe
This leaves off the Eddystone-UID type code (00), the calibrated power (e7), the namespace identifier (2f234454f4911ba9ffa6) and the instance identifier (000000000001). As a result, it won't be recognized as an Eddystone-UID frame.