Skip to main content

Module mesh

Module mesh 

Source
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>:

opbodyanswer
networkthe bridge’s address, IV index, and the nodes
unprovisionedthe devices whose beacons were heard, newest first
provisionuuid (hex), optional static_oob (hex)the node: address, elements
configureaddressits Composition Data, after the AppKey and bindings
onoffaddress, onthe Generic OnOff state it reports

Events on <base>/mesh/event: unprovisioned (a new beacon) and message (an access message to the bridge).

Structs§

BridgeMesh
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).