Important announcement - Onyx Beacon hardware and services to be discontinued! More info...



Local notifications and coupons don’t arrive on device when app is in background?

Please check if you have the content already received before sending the app in background. If you have the content, swipe to left on the cell to delete it. If the content is delivered, then you’ll not receive any notifications.
If none of this helps, please send the logs from the Xcode console for the sample app and/or try to reproduce this behaviour using OnyxBeacon management app ( ). In the OnyxBeacon app you have to login so the app can load your account info. You have an option to send logs directly from the app.


How to activate the sound for the Enterprise Beacons?

In the current version, the API for enabling buzz on the beacon is not exposed yet. We’ll integrate this feature in one of the next releases of the SDK.

It is possible to enable buzz on the beacon by connecting to it through CoreBluetooth:

1. Scan for peripheral devices and read the scan response. Please take a look at the structure of the scan response (advertisementData paramter from centralManager:didDiscoverPeripheral:advertisementData:RSSI: delegate method). You can identify your beacon by using the major and minor values. The UUID field contains the first 4 bytes of the proximity UUID due to scan response size limitations.

2. After you have identified the peripheral you’re interested in, issue a connect and then scan for services. You should identify a service that has the UUID 2aaceb00-c5a5-44fd-2000-3fd42d703a4f.

3. After retrieving characteristics for that service, identify the characteristics that have the following UUIDs:

2aaceb00-c5a5-44fd-2002-3fd42d703a4f – buzz characteristic
2aaceb00-c5a5-44fd-2002-3fd42d703a4f – extended buzz characteristic

3.1 Buzz characteristic accepts one byte data with value 0x01. This will enable a buzz that will have 4 beeps at equal intervals of time during 4 seconds.
3.2 Extended buzz accepts 2 byte data, a bit field where each bit represents the state of buzz, total of 16 bits. There will be a short buzz, a preamble, after which the buzz pattern will be issued. The total length of preamble + 16 flag bits has 4s.


The action name for receiving beacons should be in the format of .content.ibeacons?

The beacon functionality works independently of the coupons. About the implementation, the action filter is right. Check to have mManager.setAPIContentEnabled(true); in the code that initializes the sdk.


Can I see if a coupon has been used through the SDK?

If you delete a coupon using the method deleteCoupon(long couponId), the coupon will be received again after an interval set in the beacon page (CMS) in Message frequency field.

If you don’t want to receive the coupon again than just delete it from UI. And when you want to be able to receive it again delete it from the SDK using the above method.


How does the configuration of the client take place? Is there a possibility of a central configuration option for all the deployed beacons or is it only possible through the app? What configurations can be made here?

iOS SDK has the support for unattended beacon configuration. The SDK that is integrated in the app that is running on client phone can detect if the beacons that are around need new configuration and will connect and attempt to send the configuration packet.


What type of SDK will I get? What is its purpose?

Our SDK is available for both iOS and Android. It helps you in developing iBeacon compatible mobile apps or to integrate it into existing mobile apps.