How to Set Up MOKO Beacons for iBeacon and Eddystone Protocols

We get asked a lot how to properly set up the iBeacon, Eddystone configuration for MOKO beacons. Many customers want to know the proper configuration steps and parameter settings for their specific deployment needs. There are a few configuration requirements that must be followed correctly and some settings that can cause detection issues if not properly configured, but these are manageable with the right guidance.

In this guide, you’ll get a hands-on breakdown of how to configure MOKO beacons for both iBeacon and Eddystone. These are essential steps to understand when working with BLE beacon deployments, especially if you want a reliable setup and smooth ongoing operations.

What are iBeacon and Eddystone protocols?

A couple of very popular terms that you’ve probably heard of, beacons, iBeacon, and Eddystone. Before we dive deeper into the configuration details, I’ll give you a simple explanation.

Beacons are small radio devices that broadcast Bluetooth Low Energy (BLE) signals regularly. iBeacon and Eddystone are two different communication formats (or protocols) that define what’s inside that signal. They’re not the actual hardware, and they’re the format of the data the beacon sends out.

	iBeacon (Apple)	Eddystone (Google)
Main Fields	UUID, Major, Minor	UID, URL, TLM, EID
Platform Support	iOS (best), Android	iOS and Android
Use Case	App-based experiences	Web links, telemetry, flexible use cases
Signal Payload	Fixed	Multiple frame types

iBeacon (by Apple)

The iBeacon broadcasts a UUID, along with a Major and a Minor value. The Beacon doesn’t do the tracking; it just broadcasts. An app picks up the signal and acts on it. iBeacon is compatible with iOS and Android, but it works better with iOS since native to iOS.

Eddystone (by Google)

Eddystone has 3 different frame types: Eddystone-UID, Eddystone-URL, or Eddystone-TLM. Eddystone-EID is an encrypted version of UID for added privacy. Eddystone works well with both iOS and Android.

To simply sum up, iBeacon is simple to deploy, offers more documentation, but provides fewer features. Eddystone sends more types of data and delivers more features than iBeacon, but it is more complicated to integrate.

Tools you need to configure MOKO beacons

The entire MOKO beacon deployment requires proper preparation of hardware and installation tools. In order to quickly complete the deployment, the equipment and installation tools to be used are mainly as below:

• MOKO beacons (includes beacon device, mounting accessories, screws, and others).
• Testing devices – iOS or Android smartphones or tablets for configuration and testing.
• Install beacon configuration app, Download MOKOSmart’s specific apps like BeaconX Pro and MK Button, or use the nRF Connect app.

You have to make sure that your phone has Bluetooth, Location, and Storage permissions enabled for the app. Since Android 6.0, Location permission is required to scan BLE devices. That’s not a bug — it’s by design because beacons can be used for proximity/location services.

Note: MOKO mainly uses two different chipsets for our beacon products (Nordic and Telink). After installing BeaconX Pro, you’ll need to select the right sub-app version for your specific beacon model. If you pick the wrong one, you’ll see a prompt when you try to connect that says the firmware version doesn’t match.

Setting up a MOKO Beacon for iBeacon

Configuring your MOKO beacon for the iBeacon protocol mainly involves connecting to the beacon and configuring the key parameters. Here’s how to do it with the BeaconX Pro APP.

Step 1: Connect to the beacon

• Open the BeaconX Pro app, and wait for the scan preview. It’ll show all nearby MOKO-based devices, including your beacon.
• Find your beacon and tap the “CONNECT” button next to it, and the device LED will blink 4 times quickly
• Now enter the default connection password “Moko4321” and press “OK“. The device LED will blink 4 times rapidly again to confirm the connection.

Step 2: Configure iBeacon settings

Once connected, you’ll see the main screen with three parts: SLOT, SETTING, and DEVICE. To configure iBeacon, go to the SLOT tab. Each beacon has up to 6 advertising slots. Pick one and set the frame type to iBeacon. Now you can configure the following key parameters:

• UUID – This 16-byte value identifies your entire beacon network. You should use the same UUID across all your beacons (e.g. 000102030405060708090A0B0C0D0E0F, without dashes).
• Major – A 2-byte field that can range from 0– Use this to group beacons (like all beacons on a specific floor).
• Minor – Also 2-byte field from 0– Used to identify and distinguish individual beacons within a Major group.
• RSSI\@1m – Calibrated signal strength measured at 1 meter. Helps apps estimate distance. Range is from -100 dBm to 0 dBm.
• Advertising Interval – Time between broadcasts. Default of 350ms is a good balance between responsiveness and battery life.
• Tx Power – Adjusts signal range. Higher power = more range, but more battery drain.

Setting up a MOKO Beacon for Eddystone

The steps for Eddystone are very similar to iBeacon, but the frame types and parameters are different. Again, start by connecting to your beacon as described above. Then, go to the SLOT tab and configure:

Eddystone-UID (similar to that of iBeacon)

Choose a slot and set the frame type to Eddystone-UID, and you’ll need to configure the ADV content and other Parameters:

• Namespace ID – 10-byte string shared by all your beacons
• Instance ID – 6-byte value for uniquely identifying each beacon, think of a combination of Major and Minor from iBeacon into a single field.
• RSSI\@0m – Tx power in dBm emitted by the beacon at 0 meter, ranging from -100dBm to 0dBm.

Eddystone-URL

Select an available slot and set the frame type to Eddystone-URL, then enter a valid URL (1–17 characters in US-ASCII). The beacon automatically handles the URL compression and prefix encoding to fit more within the limited advertisement packet.

Eddystone-TLM

As others, choose a slot and select Eddystone-TLM. There are no other advertisement configurations except basic ADV Interval and Tx Power. The TLM frame type will broadcast information like battery voltage, chip temperature, ADV count, and uptime. This is useful for monitoring the health and status of your beacons remotely.

Running multiple protocols simultaneously

One of the great advantages of MOKO beacons is that you can run multiple protocols at the same time using different advertisement slots. This means you can configure your beacon to broadcast both iBeacon and Eddystone simultaneously, or use different Eddystone frame types together.

Each beacon has six advertising slots, and each can be set up with a different frame type. You could do something like:

Slot 1: iBeacon

Slot 2: Eddystone-UID

Slot 3: Eddystone-TLM

Slot 4: Eddystone-URL

This is really useful when you want to support both iOS and Android users or when you want to broadcast both app-specific data and general-purpose links.

Just keep in mind that more active slots = more power usage. Shorter intervals and higher Tx power also reduce battery life. So depending on your use case, you’ll want to find the right balance.

Real-world use cases for configured beacons

After you get your beacons configured properly, there are quite a few deployment scenarios where these configurations really shine. We’ve seen customers use iBeacon setups in retail stores to push personalized offers when shoppers get near specific product displays. The Major and Minor values work really well for organizing beacons by store section and individual product categories.

For Eddystone deployments, museums love using the URL frame type because visitors can just tap the notification to get more information about exhibits without needing to download a specific app. And with Eddystone-TLM running simultaneously, facility managers can monitor beacon health remotely and know when batteries need replacing before they actually die.

Many interesting setup we helped with involved warehouse operations that used Eddystone-UID for asset tracking combined with iBeacon for worker safety notifications. The multi-protocol capability really makes a difference when you need to serve different purposes with the same hardware.

Why choose MOKOSmart beacons

MOKO Beacons are cost-effective, robust, reliable, and low-powered wireless BLE transmitters. They support both iBeacon and Eddystone protocols, and we offer a wide range of beacon models depending on what you need, from asset tags to personnel safety tags, from sensor beacons to long-life location anchors. Many of our BLE beacons can operate in harsh industrial environments and have long battery life up to 10 years.

Beyond basic proximity broadcasting, you can get MOKO beacons equipped with 3-axis accelerometers, temperature and humidity sensors, and ambient light sensors. All backed by MOKO’s solid documentation and technical support.

FAQs about Beacon configuration

Q: Can I change the password of my MOKO beacon?

Yes. After you connect using the app, go to SETTING > Change Password. You can set a new one up to 16 characters long.

Q: Why is my beacon not showing up in the BeaconX Pro app?

Check three things: make sure Location, Bluetooth, and Storage permissions are granted; verify you selected the correct app version (Nordic or Telink) for your beacon; and ensure no other device is already connected to it.

Q: What happens if I configure two slots with the same frame type?

You can definitely do that, for example, having two iBeacon slots with different UUIDs. But keep in mind that each active slot adds load to the beacon and increases battery drain. Make sure there’s a reason to do it.

Q: How many devices can detect the same beacon at once?

As many as are in range. Beacons broadcast passively; they don’t create connections, so multiple phones or tablets can pick up the signal at the same time without any conflict.

READ MORE

• 5 Most Common MOKO Beacon Questions Answered
• Eddystone vs iBeacon -Which one should you choose?