You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
When debugging my Bluetooth scanning code I found out that there is a mixup in the UUID for EddyStone frames in the documentation. In this paragraph is written:
The Complete List of 16-bit Service UUIDs as defined in The Bluetooth Core Specification Supplement (CSS) v5, Part A, § 1.1. The Complete List of 16-bit Service UUIDs must contain the Eddystone Service UUID of 0xFEAA. This is included to allow background scanning on iOS devices.
While in the table it is in the other order: AAFE:
Byte offset
Value
Description
Data Type
...
...
...
5
0xAA
16-bit Eddystone UUID
6
0xFE
...
...
...
...
9
0xAA
16-bit Eddystone UUID
10
0xFE
...
...
...
...
I assume the correct value is the one from the quoted text FEAA. In that case please correct the AAFE in the table. Or am I misunderstanding something fundamental here!?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When debugging my Bluetooth scanning code I found out that there is a mixup in the UUID for EddyStone frames in the documentation. In this paragraph is written:
While in the table it is in the other order: AAFE:
0xAA
0xFE
0xAA
0xFE
I assume the correct value is the one from the quoted text
FEAA
. In that case please correct theAAFE
in the table. Or am I misunderstanding something fundamental here!?The text was updated successfully, but these errors were encountered: