Expand description
Bluetooth Mesh in the bridge: the bridge as a mesh’s provisioner, on the advertising bearer of the controller it already scans with.
The network (keys, the nodes it provisioned) lives in <data>/mesh, and is
created on the first start with [mesh] enabled = true. Requests on
<base>/bridge/request/mesh/<op>, answered on <base>/bridge/response/mesh/<op>:
| op | body | answer |
|---|---|---|
network | the bridge’s address, IV index, and the nodes | |
unprovisioned | the devices whose beacons were heard, newest first | |
provision | uuid (hex), optional static_oob (hex) | the node: address, elements |
configure | address | its Composition Data, after the AppKey and bindings |
onoff | address, on | the Generic OnOff state it reports |
Events on <base>/mesh/event: unprovisioned (a new beacon) and
message (an access message to the bridge).
Structs§
- Bridge
Mesh - The bridge’s mesh.
Constants§
- AD_
TYPES - The AD types Mesh is carried in, reported by the scanner every time.
Functions§
- only_
mesh - Whether an advertisement is only Mesh (not worth publishing as a report).