I’m trying to provision a Bluetooth Mesh device using BlueZ’s mesh-cfgclient tool on a Raspberry Pi. When I use the nRF Mesh mobile app, I can choose between “no OOB” (no out-of-band authentication) and “static OOB” (fixed key). Provisioning succeeds with no OOB but fails with static OOB.
However, on the Raspberry Pi, mesh-cfgclient always attempts to use static OOB when provisioning this device. I don’t need or want static OOB—no OOB works fine on the mobile app, and the device doesn’t require a static OOB key. Unfortunately, there doesn’t seem to be a straightforward command-line option in mesh-cfgclient to disable OOB methods or choose “no OOB” explicitly.
Question: Does anyone know how to configure or modify mesh-cfgclient so that it uses no OOB only and avoids static OOB? Any workaround or guidance would be greatly appreciated.
Thank you in advance!
I’ve read through the BlueZ documentation and searched in the mesh-cfgclient source code for any command-line flags or options that would let me disable or override OOB methods. I also tried modifying the tool’s configuration files (for instance, by removing references to "static-oob" in the local JSON config), but mesh-cfgclient still prompts me to enter a static OOB key. In addition, I explored the code to see if there was a straightforward way to comment out or remove static OOB capabilities, but that doesn’t appear to be a simple change.
