Unique Identifier for Feasy Beacon in Flutter (Android vs iOS)

abenahmed

Hello everyone,

I’m building an attendance app using Feasy Beacon devices and Flutter, and I’m scanning BLE devices with the flutter_blue_plus plugin.

On Android, everything works as expected:

I can identify the beacon using the MAC address (remoteId)

The UUID matches the value configured on the beacon

On iOS, however, I’m facing a limitation:

remoteId is a random 128-bit UUID (e.g. e006b3a7-ef7b-4980-a668-1f8005f84383)

This UUID changes between installs and cannot be used as a stable identifier

iOS does not expose the MAC address

According to the plugin documentation:

/// iOS uses 128-bit uuids as the remoteId
/// Android uses 48-bit MAC addresses as the remoteId

My question:

What is the correct and reliable way to uniquely identify a Feasy Beacon across both Android and iOS?

Specifically:

Which BLE data should be used as a unique identifier (UUID / Major / Minor / Manufacturer Data)?

How can this identifier be extracted using flutter_blue_plus on iOS?

Is using iBeacon data (UUID + Major + Minor) the recommended approach for cross-platform identification?

FAE_Gavin

abenahmed I need to check some technical details internally first, and will get back to you as soon as possible.

abenahmed

waiting for you

FAE_Gavin

abenahmed To uniquely identify a Bluetooth device like the Feasy Beacon across both iOS and Android, you can use its MAC address, provided the beacon hardware supports broadcasting it. While a Bluetooth device itself is uniquely identified by its MAC address, an iBeacon is logically identified by its configurable UUID, Major, and Minor combination.

To extract the MAC address on iOS using flutter_blue_plus, you will need to parse it from the raw advertisement data . For implementation details, please consult the official flutter_blue_plus documentation.

Recommended Solution: FeasyBeacon App SDK. It provides a unified API that directly returns stable identifiers such as the device's MAC address and iBeacon data, abstracting away the platform-specific complexities.
FeasyBeacon App SDK
Additionally, the attached file is the beacon broadcasting protocol.

feasybeacon-advertising-protocol-v11.pdf

150kB

abenahmed

Thanks for the clarification.
Could you give me an example of code showing how to extract the mac address in ios using FeasyBeacon App SDK

FAE_Gavin

abenahmed The FeasyBeacon App SDK automatically handles the underlying data parsing. The "General Advertising Frame" broadcast by the device (detailed in FeasyBeacon Advertising Protocol)contains the real MAC address. This frame is identified by the Service UUID 0xFFF0.
Once you integrate and use the SDK for scanning, it performs the following steps automatically:

Identifies and captures advertisement packets containing the Service UUID 0xFFF0.
Parses the raw MAC address data from bytes 6 to 11 according to the frame structure defined in the protocol.
Converts this 6-byte address into a common string format (e.g., DC:0D:30:00:1F:A5).

Furthermore, for a practical reference, the SDK includes the complete source code for the FeasyBeacon App sample project. You can open this project in Xcode to directly see how device discovery and information display (including the MAC address) are implemented in the UI and corresponding code, which is the most intuitive guide for integration.