Procedures for integrating nRF Cloud into a Bluetooth Mesh Project

RE: Procedures for integrating nRF Cloud into a Bluetooth Mesh Project

a.da — Tue, 17 Feb 2026 02:05:19 GMT

Hi Edvin, thank you for your thorough investigation.

[quote userid="26071" url="~/f/nordic-q-a/126869/procedures-for-integrating-nrf-cloud-into-a-bluetooth-mesh-project/561237"]

I did find out that if I set:
CONFIG_MEMFAULT_METRICS_BLUETOOTH=n

it builds without the same error.

[/quote]

I have confirmed that setting 'CONFIG_MEMFAULT_METRICS_BLUETOOTH=n' allows the build to complete successfully without any errors in both the sample project and my project.

I understand that this is a temporary workaround.
However, I was unable to find any information in the Nordic or Memfault documentation regarding which specific metrics are affected by disabling this configuration.
If you have any insights on this, please let me know.

I look forward to an official fix for the Memfault libraries.

Best regards,

a.da

RE: Procedures for integrating nRF Cloud into a Bluetooth Mesh Project

Edvin — Mon, 16 Feb 2026 13:13:30 GMT

Hello, and thank you!

I looked at your project, and you are right. I see the same error that you see.

I am still not sure why it occurs only in this mesh project, and not if I try to enable it in e.g. a normal BLE project.

I did find out that if I set:
CONFIG_MEMFAULT_METRICS_BLUETOOTH=n

it builds without the same error.

There is a bug in the memfault libraries somewhere, and it is related to line 17 on v3.2.1\modules\lib\memfault-firmware-sdk\ports\zephyr\common\metrics\memfault_platform_bluetooth_metrics.c:

#include "controller/ll_sw/lll.h"

The Kconfig from the build log, CONFIG_BT_CTLR_SCAN_AUX_SET, and this line both refer to the Zephyr bluetooth controller, this name is not used in the Softdevice controller. But I am not sure why it is not triggered in a normal BLE project, but it is in the Bluetooth Mesh project. I have reached out to our Memfault team, but I have not heard back from them yet.

You can continue to dig and see if you figure out why it fails in this Mesh project, and not e.g. in the v3.2.1\nrf\samples\bluetooth\peripheral_uart project. I will get back to you when I hear from the Memfault team.

Best regards,

Edvin

RE: Procedures for integrating nRF Cloud into a Bluetooth Mesh Project

a.da — Thu, 12 Feb 2026 03:37:19 GMT

Hi Edvin,

[quote userid="26071" url="~/f/nordic-q-a/126869/procedures-for-integrating-nrf-cloud-into-a-bluetooth-mesh-project/560770"]

Unfortunately, we don't provide the Memfault service over Bluetooth Mesh at this point in time.

It is probably still possible to add the memfault service as a BLE service (but you would need to connect to the device via Bluetooth (not mesh) to use it.

[/quote]

Yes, I understand.

[quote userid="26071" url="~/f/nordic-q-a/126869/procedures-for-integrating-nrf-cloud-into-a-bluetooth-mesh-project/560770"]I assume this is what you tried originally. Would it be possible to upload the project where you tried to add the memfault service? And what was it that you added that caused it to fail?[/quote]

Instead of my actual project, I am attaching a sample program that reproduces the exact same build error.
I would like to keep this ticket public so that it remains accessible to others, and the issue is easily reproducible using this sample.

devzone.nordicsemi.com/.../light_5F00_ctrl.zip

Specifically, I merged the 'prj.conf' from the MDS sample into the 'prj.conf' of the Lightness Controller sample.
Please note that I have omitted the Memfault Project Key.

Best regards,

a.da

RE: Procedures for integrating nRF Cloud into a Bluetooth Mesh Project

Edvin — Tue, 10 Feb 2026 09:59:37 GMT

Hello,

Unfortunately, we don't provide the Memfault service over Bluetooth Mesh at this point in time.

It is probably still possible to add the memfault service as a BLE service (but you would need to connect to the device via Bluetooth (not mesh) to use it.

I assume this is what you tried originally. Would it be possible to upload the project where you tried to add the memfault service? And what was it that you added that caused it to fail?

Best regards,

Edvin

RE: Procedures for integrating nRF Cloud into a Bluetooth Mesh Project

a.da — Sun, 08 Feb 2026 23:18:39 GMT

Hi Edvin,

Thank you for looking into this and for coordinating with the Memfault team.
I look forward to hearing more from you or the team.

a.da

RE: Procedures for integrating nRF Cloud into a Bluetooth Mesh Project

Edvin — Fri, 06 Feb 2026 13:35:39 GMT

I understand. You should not need to use CONFIG_BT_LL_SW_SPLIT=y for any of the Bluetooth Mesh features either.

Let me check with the Memfault team whether they already have anything for Bluetooth Mesh, or any thoughts on how we can attack that. Particularly around OTA, but also with regards to fault data reports.

Please excuse the delay, but I need to discuss this internally first. I will get back to you once I know more, or perhaps the Memfault team will handle this ticket directly.

Best regards,

Edvin

RE: Procedures for integrating nRF Cloud into a Bluetooth Mesh Project

a.da — Fri, 06 Feb 2026 06:00:03 GMT

Hi Edvin, thanks for your reply.

[quote userid="26071" url="~/f/nordic-q-a/126869/procedures-for-integrating-nrf-cloud-into-a-bluetooth-mesh-project/560461"]Did you use CONFIG_BT_LL_SW_SPLIT=y before you started adding the Memfault Service?[/quote]

No, I have never used 'CONFIG_BT_LL_SW_SPLIT=y'.
I am using the Nordic Semiconductor's Bluetooth Stack.

I apologize for the confusion.
My intention is not that I want to use the Zephyr Bluetooth controller; rather, I want to confirm if it is mandatory to enable it for this integration.
As I mentioned, enabling Mesh-related configs seems to force this dependency, and I am trying to find a way to avoid it.

[quote userid="26071" url="~/f/nordic-q-a/126869/procedures-for-integrating-nrf-cloud-into-a-bluetooth-mesh-project/560461"]Also, can you please describe a bit how you plan that this should work?[/quote]

To provide some context, I am relatively new to the Memfault Service and am currently in the exploration phase to see how it can be utilized within my Bluetooth Mesh project.
I understand that in order to register a device and upload reports to Memfault Service, a direct BLE connection to a mobile device is required.
Of course, it is not practical for a Provisioner or gateway to maintain a constant connection with every node in a Mesh network.

Therefore, I am still considering what kind of data to store and how to manage the reporting process, including how it would operate in a real-world market deployment.

At this stage, I anticipate that the OTA Releases feature, in particular, will be partially applicable to my needs.

a.da

RE: Procedures for integrating nRF Cloud into a Bluetooth Mesh Project

Edvin — Thu, 05 Feb 2026 14:45:24 GMT

Hello,

I think you sidetracked a bit. Did you use CONFIG_BT_LL_SW_SPLIT=y before you started adding the Memfault Service?

The CONFIG_BT_LL_SW_SPLIT=y basically says that you use the Zephyr Bluetooth Controller instead of Nordic Semiconductor's Bluetooth Stack (the SoftDevice Controller).

Also, can you please describe a bit how you plan that this should work? You have a Bluetooth Mesh network, and you want to add the Memfault Service. This will not automatically make every device report this to some gateway. It will add a Bluetooth Low Energy Service that stores the crash faults to some flash partition, but it is only useable for devices that are connected to a Mobile device via Bluetooth Low Energy (not through Bluetooth Mesh).

I am not sure, it might work the way that you have planned out, but can you please give some description on how you planned that this will work, and how it should behave? And what features you intend to use from the Memfault Service?

Best regards,

Edvin