Classic Bluetooth SPP, BLE GATT services and clients, notifications and reconnection. Radio roles and GATT client/server roles are separate design choices; define the application data contract explicitly.
Budget a large Mesh Access message in segments, retransmission opportunities and retained buffers before increasing the payload limit. One missing segment can keep a transaction alive while other traffic competes for the same transport resources. Applicability: historical Bluetooth Mesh Protocol 1.1 lower-transport segmentation and Zephyr 4.2.0 transport/Kconfig sources. The worked case is an Access message…
A GATT connection to a Mesh Proxy Server is only the bearer. The server’s proxy filter can still exclude the destination addresses your management client needs. Diagnose that per-connection filter separately from GATT notification readiness and the client’s application-model subscriptions. Applicability: historical Bluetooth Mesh Protocol 1.1 ordinary proxy filtering, with Zephyr 4.2.0 proxy_srv.c behavior explicitly…
Start a Mesh product’s address plan with independently addressable behavior. Then map each physical function to an element, each element to its model instances, and each instance to the required keys and communication settings. A node address alone cannot identify every controllable output inside the enclosure. Applicability: historical Bluetooth Mesh Protocol 1.1 elements, Composition Data…
Remote provisioning adds a reachable Mesh server between the commissioner and the unprovisioned device. Qualify both paths and track the provisioning transaction across them. A scan report from that server proves neither that a provisioning bearer can open nor that the new node has joined successfully. Applicability: historical Bluetooth Mesh Protocol 1.1 PB-Remote for installing…
Plan Mesh Key Refresh around a per-node evidence ledger, not a single network-wide progress percentage. A node that missed new-key distribution is fundamentally different from one that has both keys but missed a phase signal. Advancing to revocation without distinguishing them can remove a device that was meant to remain. Applicability: historical Bluetooth Mesh Protocol…
A returning Mesh node must recover an authenticated network epoch without reusing unsafe sequence state or treating previously accepted traffic as new. Do not repair a long-offline failure by zeroing counters, clearing replay records or copying an IV Index from an unauthenticated advertisement. Applicability: the historical Bluetooth Mesh Protocol 1.1 document, especially sections 3.9.8, 3.11.5…
A low-power node can keep a valid friendship while losing queued application messages. PollTimeout limits friendship inactivity; it does not promise that every message will remain buffered until the next poll. Design polling around both the Friend Queue and the application’s freshness requirement. Applicability: Bluetooth Mesh Protocol 1.1 friendship, with Zephyr 4.2.0 source as an…
Add a Bluetooth Mesh relay only when a controlled comparison shows that it improves the required receivers’ delivery or resilience within the traffic budget. Enabling every capable node can create more repeated traffic without fixing the actual weak path. Applicability: Bluetooth Mesh Protocol 1.1 managed flooding over the advertising bearer. Zephyr 4.2.0 configuration-client declarations illustrate…
A BlueZ discovery filter expresses one client’s interest in a shared adapter. It does not create a private stream containing only that client’s devices. Make the application repeat its own eligibility checks, then investigate which active clients broaden the shared discovery work. Applicability: BlueZ 5.79 Adapter1 and its tagged adapter.c implementation. The proposed experiment uses…
Treat an acquired GATT descriptor as a connection-scoped resource with one owner, a negotiated size context and an explicit close path. On HUP, retire that acquisition; after reconnect, obtain a new descriptor and MTU rather than reviving the old integer. Applicability: BlueZ 5.79 remote/client GattCharacteristic1 AcquireWrite and AcquireNotify, with the matching gatt-client.c implementation. Local/server implementations…