BLE Mesh Wildcard / Catch all Opcode handler callback

RE: BLE Mesh Wildcard / Catch all Opcode handler callback

Hieu — Fri, 13 Jun 2025 07:16:57 GMT

Hi jm_solar,

I have an update. A colleague introduced me to this feature, which let the application receive messages from the access layer directly, so you can extract the model and opcode and handle it on your own. See: sdk-zephyr/subsys/bluetooth/mesh/Kconfig at v4.0.99-ncs1 · nrfconnect/sdk-zephyr.

Note that this comes with the RPL/Flash weakness as detailed in that Kconfig description. The application will also get a callback for messages of all other models, even the ones that are setup in the "normal" way as well, so you will need to implement your own filtering.

RE: BLE Mesh Wildcard / Catch all Opcode handler callback

Hieu — Thu, 12 Jun 2025 20:11:13 GMT

Hi jm_solar,

If you want to set it up in a way that it can handle all op codes, then perhaps the only way is to setup all op codes...

May I ask why you need this pass-through functionality? The relay nodes practically play the role of such pass-through devices already.

RE: BLE Mesh Wildcard / Catch all Opcode handler callback

jm_solar — Wed, 11 Jun 2025 15:27:55 GMT

Hi Hiue, yes that is surely a solution if the list is known.

But as mentioned in our use case the list changes over time and this device should not require a firmware update when the list changes. The handling on this device has no dependency on the opcode so we want to keep the current situation where this device does not need an update in order for the new opcodes sent by other devices to be supported.

RE: BLE Mesh Wildcard / Catch all Opcode handler callback

Hieu — Wed, 11 Jun 2025 10:25:05 GMT

Hello jm_solar,

Have you tried providing the same handler to all the op codes that need to be handled similarly?

Hieu