mirror of
https://git.kernel.org/pub/scm/bluetooth/bluez.git
synced 2024-11-16 00:34:39 +08:00
64670a4a31
Instead of keeping track of unique 16bit node identifiers, reuse their UUIDs to create both storage directories and dbus objects. Because of that: - UUID is no longer stored in the JSON file, it's inferred from the directory name instead - Join(), CreateNetwork() and ImportLocalNode() APIs return an error if given UUID already registered within the daemon
50 lines
1.3 KiB
Plaintext
50 lines
1.3 KiB
Plaintext
Bluetooth Mesh Daemon
|
|
*********************
|
|
|
|
Copyright (C) 2019 Intel Corporation. All rights reserved.
|
|
|
|
Compilation and installation
|
|
============================
|
|
|
|
In addition to main BlueZ requirements, MeshCtl needs the following:
|
|
- json-c library
|
|
|
|
Configuration and options
|
|
=========================
|
|
|
|
--enable-mesh
|
|
|
|
Build mesh daemon and other Bluetooth Mesh based tools
|
|
|
|
Current implementation of the mesh daemon requires exclusive access to
|
|
a Bluetooth controller.
|
|
The AutoEnable option in the installed main.conf should be set to "false".
|
|
|
|
Storage
|
|
=======
|
|
|
|
Default storage directory is /var/lib/bluetooth/mesh.
|
|
|
|
The directory contains the provisioned nodes configurations.
|
|
Each node has its own subdirectory, named after node's Device UUID (32-digit
|
|
hexadecimal string) that is generated by the application that created a node.
|
|
|
|
Each subdirectory contains the following files:
|
|
- node.json:
|
|
node configuration and is populated by the
|
|
daemon based on the configuration commands from a
|
|
provisioner/configuration client
|
|
- node.json.bak:
|
|
a backup that the last known good node configuration.
|
|
|
|
The files are in JSON format.
|
|
|
|
Information
|
|
===========
|
|
|
|
Mailing lists:
|
|
linux-bluetooth@vger.kernel.org
|
|
|
|
For additional information about the project visit BlueZ web site:
|
|
http://www.bluez.org
|