Repository navigation
[0.2.0] - 2026-11-20
Bluetooth Mesh, the second milestone's first part, and the first release on
crates.io.
Added
bluetooth-numbers: Mesh model opcodes and model identifiers.bluetooth-mesh-stack, new (named for crates.io, wherebluetooth-meshis taken):- The security toolbox (s1, k1 to k4) and network PDU encryption and
obfuscation, checked against the specification's sample data. - Lower and upper transport: segmentation and reassembly, block
acknowledgments, application and device key encryption. - Provisioning on both sides (ECDH P-256, every authentication method)
over PB-ADV, and the advertising bearer's beacons. - The access layer: Composition Data, the Configuration models a
provisioner needs, Generic OnOff and Level. - A runtime that provisions, configures and controls nodes, and runs as
a node, on any bearer: the advertising bearer throughbluetooth-host,
or GATT through the Mesh Proxy service (ProxyBeareras the client,
ProxyServeron a node, with proxy filters). - End to end in CI on two Bumble controllers: provisioning, configuration
and control over advertising, and control through a proxy.
- The security toolbox (s1, k1 to k4) and network PDU encryption and
bluetooth-bridge:[mesh] enabledmakes the bridge a mesh's provisioner
on its own controller; requestsmesh/network,mesh/unprovisioned,
mesh/provision,mesh/configureandmesh/onoff, and events on
<base>/mesh/event.bluetooth-host:ScanConfig::always_report, AD types reported every time
whatever the duplicate filter says (Mesh's retransmissions are identical).
Fixed
- Home Assistant: each bridge on a broker is its own device, named for its
base topic (bluetooth_bridge_<base>); the defaultbluetoothkeeps the
bluetooth_bridgeid, so an existing installation keeps its device. Two
bridges used to share one.