google-beacon-platform

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

I successfully registered a beacon using Google Proximity API but the response indicates a different UID Request URL https://proximitybeacon.googleapis.com/v1beta1/beacons:register Request { "advertisedId": { "type": "EDDYSTONE", "id": "0x2f234454f4911ba9ffb6" }, "status": "ACTIVE", "latLng": { "latitude": 51.4935657, "longitude": -0.1465538 } } Response { "beaconName": "beacons/3!d31d9fdb7e38e787f8f75d5b6bd7df6f", "advertisedId": { "type": "EDDYSTONE", "id": "0x2f234454f4911ba9ffbw==" }, "status": "ACTIVE", "latLng": { "latitude": 51.4935657, "longitude": -0.14655379999999998 } } If you

The Google's Proximity Beacon API documentation uses Eddystone as an example everywhere: https://developers.google.com/beacons/proximity/register However, documentation mentions two more types of beacons , AltBeacon and iBeacon. If I understand correctly, something like this should be used (adapted from Google's example): { "advertisedId": { "type":"IBEACON", "id":"base 64 of what???"}, "status":"ACTIVE", "latLng": { "latitude": 51.4935657, "longitude": -0.1465538 } } However, what is the acceptable binary format for iBeacon's UUID,Major,Minor (which should be base64'd)? The id of the