FSC-BP103C iBeacon UUID

aschnetz

Hi,
It happens that the UUID gets 0s when I try to modify it. Typically I had 11111111-1111-1111-1111-111111111111 and I changed it to 11111111-1111-1111-1111-111111111112 but when I reconnect it was 00000000-0000-0000-000000000000 again as if it was reset or the new UUID rejected. Any explanation to this behavior ?
I did it via the App FeasyBeacon with IOS device. I had only an iBeacon slot enabled/active during this changes.
Thanks in advance.

FAE_Gavin

aschnetz Based on your description, after modifying the iBeacon UUID using the FeasyBeacon App on an iOS device, you found that the UUID became all zeros upon reconnecting. This typically indicates that the new UUID was not accepted or saved by the device.

The UUID you provided (11111111-1111-1111-1111-111111111112) is a valid 128‑bit UUID (32 hexadecimal characters + 4 hyphens) in terms of format. Therefore, the issue is likely related to the writing process or the device’s response.

To help us identify the root cause, could you please record a video (or provide detailed screenshots) of the following steps:

Open the FeasyBeacon App and connect to the device – show the initially displayed UUID.
Modify the UUID and tap the save/write button.
Show any prompt or message displayed by the app after saving.
Disconnect and then reconnect to the device – check whether the UUID has become all zeros.

Please send the video to: Support@feasycom.com

We look forward to your recording and will assist you as soon as possible.

aschnetz

Hi,

I just sent the video via mail. It does not only concern this UUID number. I noticed that it often happens when I try to change UUID.

I hope it helps.

Antoine

FAE_Gavin

aschnetz Dear Antoine,
Thank you for the video. We have confirmed the issue.

Cause: This is a bug in the current version of the FeasyBeacon App. The app fails to properly update the UUID when only a single character is changed. It requires the entire 32-character UUID string to be fully deleted and re-entered from scratch.

2.Solution:
To successfully change the UUID, please follow these steps:

In the FeasyBeacon App, delete the entire existing UUID (clear all 32 characters).
Type the new UUID completely (all 32 characters).
Save the configuration.
This will ensure the new UUID is correctly written to the beacon.

3.Next Steps:
Our development team has been notified of this bug and will work on a fix for a future version of the FeasyBeacon App. In the meantime, please use the workaround above.

Thank you for bringing this to our attention, and we apologize for any inconvenience caused. If you have further questions, feel free to ask.

aschnetz

Hi,

I tried the work around and it does not work. I tried different things as well but somehow something goes wrong since I get zeros when I read it back. I only got one time the entered UUID be correctly stored but it has randomly worked while I did not do something different. So it looks really random.

FAE_Gavin

aschnetz This issue is mainly caused by the APP. I have already reported it to the relevant engineers.
For now, we recommend resolving it with the temporary solution below:

In the FeasyBeacon App, delete the entire existing UUID (clear all 32 characters).
Type the new UUID completely (all 32 characters).
Save the configuration.
This will ensure the new UUID is correctly written to the beacon.