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…
Keep a local BlueZ GATT application’s exported object tree alive for the entire registration lifetime, and treat every new D-Bus owner as a new registration. Reusing the same object-path strings after process restart does not restore the previous application automatically. Applicability: BlueZ 5.79 local GATT server APIs and the matching gatt-database.c implementation on the system…
Recover a reset controller by rebuilding a new controller generation from durable product intent. Do not keep issuing commands through host objects that describe connections, advertising sets or credits the controller has already lost. The first recovery milestone is a synchronized host/controller state, not a successful reconnect to one peer. Applicability: Bluetooth Core 6.1 HCI…
Count HCI ACL packets against the controller pool that actually owns them, then return capacity from per-handle completion deltas or disconnect reclamation exactly once. Do not count application messages, radio packets or L2CAP credits as though they were the same resource. Applicability: Bluetooth Core 6.1 packet-based host-to-controller ACL flow control, with Linux v6.12 implementation examples….
Keep command-send allowance separate from the lifecycle of the operation a command starts. Command Status can permit another HCI command while the first procedure remains pending. Conversely, a later procedure-completion event does not automatically grant command credit. Applicability: Bluetooth Core 6.1 HCI command flow control, with Linux v6.12 source used as an explicitly narrower implementation…