|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Flutter_blue||2,213||30||14||5 months ago||31||March 15, 2021||653||bsd-3-clause||Dart|
|Bluetooth plugin for Flutter|
|Btlejack||1,649||10 months ago||9||November 18, 2022||15||mit||Python|
|Bluetooth Low Energy Swiss-army knife|
|Corebluetoothperipheral||384||10 years ago||2||apache-2.0||Objective-C|
|Demonstration of using CoreBluetooth on Mac and iOS|
|Bluetoothchat||278||5 years ago||3||Java|
|基于Android Classic Bluetooth的蓝牙聊天软件，目前仅支持一对一实时通信、文件传输、好友添加、好友分组、好友在线状态更新等功能，其中消息发送支持文本、表情等方式。|
|An up-to-date listing of all the various Bluetooth Specification-related elements that are defined by our industry (Company IDs, Service UUIDs, Characteristic UUIDs and Descriptor UUIDs), that you can use instead of rolling your own.|
|Blue Falcon||251||3 months ago||25||September 30, 2020||8||gpl-3.0||Kotlin|
|A Bluetooth kotlin multiplatform "Cross-Platform" library for iOS and Android|
|Bluetooth Le||194||6||a month ago||44||January 02, 2023||21||mit||TypeScript|
|Capacitor plugin for Bluetooth Low Energy|
|H Ble||167||5 years ago||4||Java|
|Pytile||152||89||13 hours ago||32||February 03, 2022||3||mit||Python|
|📡 A simple Python API for Tile® Bluetooth trackers|
|Bluez Ibeacon||141||10 years ago||2||mit||Objective-C|
|Complete example of using Bluez as an iBeacon|
Welcome to the Bluetooth Numbers Database, an online repository containing metadata and definitions for a subset of Bluetooth Assigned Numbers. The goal of this project is to provide a shared open platform to access from a variety of platforms, such as web and mobile, with the intention of covering both GATT and industry specifications.
Bluetooth Numbers Database is maintained by Nordic Semiconductor ASA.
During the development of various Bluetooth tools at Nordic, many of the assigned numbers from the Bluetooth specifications have been taken into use in different areas, which has lead to duplication of effort between the different tools. Hence it has been seen as beneficial to unify the work efforts by using a single, cohesive project representing a Single Source of Truth.
In addition to looking up officially defined numbers, it is common to extend the SIG-defined numbers with proprietary definitions that do not overlap with the standard. Such extension is permitted, but unless there is a place to check against whether your proposed UUID is used by others, we run the risk of having multiple uses for the same identifier.
Bluetooth Numbers Database aims to solve this problem by providing a centralized database for querying UUIDs and Company identifiers. It is also open to anyone who would like to contribute.
The #1 question most Bluetooth developers will ask themselves when seeing this repo is a variation along the lines of
Don't need another library - I can write this in 5 minutes. And whilst true, this does not cover the entire picture, because it's everyone writing the same piece of code 5 minutes, and then having to keep it up to date. That's the weight we're removing from you by using this community project. You don't need to worry about staying up to date regarding new Company IDs or GATT Attributes - just write code that pulls information from this repo every once in a while, and your apps will permanently be kept up to date. No need for reinventing the wheel.
If you're involved with any software wherein Bluetooth UUIDs (GATT Attributes) or Manufacturer IDs need to be shown to the user in readable form, such as displaying their associated names or descriptions, this project is just for you. Pull the information you need directly from our
/v1/ endpoint folder, and you're good to go. Schema Definitions are just below, and you can be sure that the integrity of said files and schemas will be maintained through our automated tests.
For the 'v1' release of the database, two types of data structures are used: UUIDs and Company Identifiers. Both of them defined as JSON Schemas.
UUID definitions specified in this project use the following data structure:
||Unique Number identifying the specific GATT Attribute. The number can be 16 or 128 bits UUID, and must comply with the format as defined in the Bluetooth Core specification. Examples: "2902" for Client Characteristic Configuration Descriptor, "EF680100-9B35-4933-9B10-52FFA9740042" for Thingy Configuration Service.||Yes|
||The GATT Attribute's name.||Yes|
Uniform Type Identifier, a reverse-dot notation String used to set the context of the attribute. Apply the following naming convention to the identifier: (reverse domain URL).(attribute type).(generic use case).(specific use case). Example:
||The source of the UUID's definition. For example: all GATT Services, Characteristics and Descriptors have a
We have based the data structure above on the official listing of GATT Specifications as much as possible. You can check this listing of GATT Characteristics for reference. And as above, you can check our JSON Schema here.
||Decimal value representing a Company as defined in the official list of assigned Company Identifiers of the Bluetooth Specification.||Yes|
||Name of the Company||Yes|
This structure is a mirror of the official Bluetooth Specification. It is added as a convenience so that each application does not need to download and transfrom the online listings at the Bluetooth official website. Note that registration of new Company Identifiers must go through official channels at Bluetooth SIG. The full JSON Schema for the Company ID Data Structure can be found here.
Furthermore, please feel free to raise issues or pull requests with your own suggestions about how this project can or should improve. We at Nordic do not view Bluetooth Numbers Database as our property, but as a shared endeavour with the rest of the developer and Bluetooth communities.