Bluetooth Mesh Light CTL (color tuned light) sample

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Fri, 21 Nov 2025 10:07:02 GMT

Sounds good! Feel free to open more cases here as well if anything pops-up.

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Thu, 20 Nov 2025 18:38:14 GMT

Ok, so that mystery is solved thank you!. I'm still doing some testing, will let you know when I close it out.

Jack

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Thu, 20 Nov 2025 14:41:39 GMT

[quote user="ji_584"]I had originally been using no subscription address for the servers and 0xFFFF (all nodes) publish address for the clients. Recently, I switched from the Android app to iOS, which is much easier to configure, and I used a group for both publish and subscribe. It seems that CTL started to work when configured this way.
[/quote]

That does make some sense; the address of the node is its primary/first element address. So I wonder if the 0xFFFF address wouldn't target secondary elements. I typically use group addresses for quick tests like these.

For this reason 0xFFFF is eg. not recommended for a DFU. I've handled a case where that was a problem before.

[quote user="ji_584"]

Would you expect all of the servers to work when an appropriate client message is sent to 0xFFFF even if no subscribe address is set on the server?

[/quote]

Yeah, I believe that is generally true: the node doesn't need to subscribe to anything to receive a message to 0xFFFF, though once again: that might just be the primary element.

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Mon, 17 Nov 2025 23:51:24 GMT

Funny you should post this, last night it started working and I was puzzled as to why.

I had originally been using no subscription address for the servers and 0xFFFF (all nodes) publish address for the clients. Recently, I switched from the Android app to iOS, which is much easier to configure, and I used a group for both publish and subscribe. It seems that CTL started to work when configured this way.

So my conclusion is that something in the CTL server and client doesn't work with 0xFFFF addresses. I don't know if the issue is that the CTL client won't send to all nodes, or if the CTL server doesn't respond to those messages.

Would you expect all of the servers to work when an appropriate client message is sent to 0xFFFF even if no subscribe address is set on the server?

This is great progress.

Thanks,

Jack

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Mon, 17 Nov 2025 15:23:57 GMT

Hi again, and thanks for the patience on this one.

I bet the issue is related to how you are addressing the light fixture, and the fact that Light CTL happens to be on another element than the ones related to lightness on the light fixture node. I haven't gotten around to get properly tested yet, but I figured it was better to get to you on this sooner rather than even later. Your code looks ok.

I realize it's been a while since you asked. Any update on this one from your side? How are you configuring the addressing?

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Wed, 29 Oct 2025 14:00:17 GMT

Hi Jack,

That's okay, we can keep it here.

I'll look into it, but I might have to get back to you on this next week.

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Mon, 27 Oct 2025 20:28:07 GMT

Hi,
It's been a while for this ticket, let me know if I need to open a new one.

I have recently renewed effort in this area, and I have been unable to get a client to actually set the temperature. I used the example ctl srv app posted above:
https://github.com/omkar3141/sdk-nrf/blob/5c2911b2970616609d03437c1992d311f3f302e7/samples/bluetooth/mesh/light_ctrl/src/model_handler.c

and the dimmer example app modified to include a ctl client.

I provisioned with the Android nRF Mesh, setting the app key for the relevant models on both server and client, and publish address of 0xFFFF on the client side models. No error messages are observed, the client appears to be responding to the button press with calls to bt_mesh_light_ctl_set_unack(), the lightness level changes on the server, but there is no indication that the temp level changes. I had to fix a few config file errors due to changing API requirements. Hardware is two nrf54l15dk.

Any advice on getting this working?

Thanks,
Jack

Here is the model_handler.c I tested, derived from the sample dimmer app:

/*
* Copyright (c) 2023 Nordic Semiconductor ASA
*
* SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
*/

/**
* @file
* @brief Model handler for the Light Dimmer Controller.
*
*/
#include <zephyr/bluetooth/bluetooth.h>
#include <zephyr/bluetooth/mesh/proxy.h>
#include <bluetooth/mesh/models.h>
#include <bluetooth/mesh/light_ctl_cli.h>
#include <dk_buttons_and_leds.h>
#include "model_handler.h"
#include <time.h>

#include <zephyr/logging/log.h>
LOG_MODULE_REGISTER(dimmer_sample, LOG_LEVEL_INF);

#define SHORT_PRESS_THRESHOLD_MS 300
#define LONG_PRESS_TIMEOUT_SEC K_SECONDS(20)
#define DELTA_MOVE_STEP 1000
#define SCENE_COUNT 4

/* Color temperature mapping constants */
#define CTL_TEMP_MIN 2700 /* Warm white at low lightness */
#define CTL_TEMP_MAX 6500 /* Cool white at high lightness */
#define CTL_DELTA_UV 0 /* No delta UV adjustment */

enum dim_direction { DIM_DOWN, DIM_UP };

/* Forward declarations */
static void ctl_status_handler(struct bt_mesh_light_ctl_cli *cli,
struct bt_mesh_msg_ctx *ctx,
const struct bt_mesh_light_ctl_status *status);
static void temp_status_handler(struct bt_mesh_light_ctl_cli *cli,
struct bt_mesh_msg_ctx *ctx,
const struct bt_mesh_light_temp_status *status);

/* CTL client handlers */
static const struct bt_mesh_light_ctl_cli_handlers ctl_handlers = {
.ctl_status = ctl_status_handler,
.temp_status = temp_status_handler,
};

/** Context for a single Light Dimmer instance. */
struct dimmer_ctx {
/** Generic OnOff client instance for this switch */
struct bt_mesh_onoff_cli onoff_client;
/** Generic Level client instance for this switch */
struct bt_mesh_lvl_cli lvl_client;
/** Light CTL client instance for this switch */
struct bt_mesh_light_ctl_cli ctl_client;
/* Relative start time of the latest press of the button */
int64_t press_start_time;
/* Dimmer direction */
enum dim_direction direction;
/* Long press work (Dimmer mode) */
struct k_work_delayable long_press_start_work;
struct k_work_delayable long_press_stop_work;
/* Current lightness level for temperature mapping */
uint16_t current_lightness;
};

/** Context for a single scene button instance */
struct scene_btn_ctx {
/** Scene client instance for this button */
struct bt_mesh_scene_cli client;
/** The currently recalled scene*/
uint16_t current_scene;
/** Time when button was pressed */
int64_t press_start_time;
};

#if IS_ENABLED(CONFIG_BT_MESH_NLC_PERF_CONF)
static const uint8_t cmp2_elem_offset[1] = { 0 };

static const struct bt_mesh_comp2_record comp_rec[2] = {
{/* Basic Scene Selector NLC Profile 1.0.1*/
.id = BT_MESH_NLC_PROFILE_ID_BASIC_SCENE_SELECTOR,
.version.x = 1,
.version.y = 0,
.version.z = 1,
.elem_offset_cnt = 1,
.elem_offset = cmp2_elem_offset,
.data_len = 0
},
{/* Dimming Control NLC Profile 1.0.1 */
.id = BT_MESH_NLC_PROFILE_ID_DIMMING_CONTROL,
.version.x = 1,
.version.y = 0,
.version.z = 1,
.elem_offset_cnt = 1,
.elem_offset = cmp2_elem_offset,
.data_len = 0
}
};

static const struct bt_mesh_comp2 comp_p2 = {
.record_cnt = 2,
.record = comp_rec
};
#endif

static void dimmer_start(struct k_work *work)
{
struct dimmer_ctx *ctx = CONTAINER_OF(k_work_delayable_from_work(work), struct dimmer_ctx,
long_press_start_work);

struct bt_mesh_lvl_move_set move_set = {
.delta = (ctx->direction == DIM_UP) ? DELTA_MOVE_STEP :
(int16_t)(-1 * DELTA_MOVE_STEP),
.transition = &(struct bt_mesh_model_transition){ .time = 500 },
};

LOG_INF("Start dimming %s...", (ctx->direction == DIM_UP ? "UP" : "DOWN"));

/* Use traditional level control for continuous dimming - CTL will be set on release */
if (bt_mesh_model_pub_is_unicast(ctx->lvl_client.model)) {
bt_mesh_lvl_cli_move_set(&ctx->lvl_client, NULL, &move_set, NULL);
} else {
bt_mesh_lvl_cli_move_set_unack(&ctx->lvl_client, NULL, &move_set);
}

k_work_reschedule(&ctx->long_press_stop_work, LONG_PRESS_TIMEOUT_SEC);
}

static void dimmer_stop(struct k_work *work)
{
struct dimmer_ctx *ctx = CONTAINER_OF(k_work_delayable_from_work(work), struct dimmer_ctx,
long_press_stop_work);

struct bt_mesh_lvl_move_set move_set = {
.delta = 0,
.transition = NULL,
};

if (bt_mesh_model_pub_is_unicast(ctx->lvl_client.model)) {
bt_mesh_lvl_cli_move_set(&ctx->lvl_client, NULL, &move_set, NULL);
} else {
bt_mesh_lvl_cli_move_set_unack(&ctx->lvl_client, NULL, &move_set);
}
}

static struct dimmer_ctx dimmer = {
.lvl_client = BT_MESH_LVL_CLI_INIT(NULL),
.onoff_client = BT_MESH_ONOFF_CLI_INIT(NULL),
.ctl_client = BT_MESH_LIGHT_CTL_CLI_INIT(&ctl_handlers),
.press_start_time = 0,
.direction = DIM_DOWN,
.current_lightness = 0
};

/* Helper function to map lightness level to color temperature */
static uint16_t lightness_to_temperature(uint16_t lightness)
{
/* Linear mapping: 0 lightness = 2700K, 65535 lightness = 6500K */
uint32_t temp_range = CTL_TEMP_MAX - CTL_TEMP_MIN;
uint32_t temp = CTL_TEMP_MIN + ((uint32_t)lightness * temp_range) / 65535;
return (uint16_t)temp;
}

/* Helper function to set both lightness and temperature */
static int set_light_ctl(uint16_t lightness, const struct bt_mesh_model_transition *transition)
{
uint16_t temperature = lightness_to_temperature(lightness);

struct bt_mesh_light_ctl_set set = {
.params = {
.light = lightness,
.temp = temperature,
.delta_uv = CTL_DELTA_UV,
},
.transition = transition
};

dimmer.current_lightness = lightness;

LOG_INF("Setting CTL: lightness=%u, temp=%uK, delta_uv=%d", lightness, temperature, CTL_DELTA_UV);

/* Use unacknowledged message for group addresses or to avoid blocking */
return bt_mesh_light_ctl_set_unack(&dimmer.ctl_client, NULL, &set);
}

/* CTL status handlers */
static void ctl_status_handler(struct bt_mesh_light_ctl_cli *cli,
struct bt_mesh_msg_ctx *ctx,
const struct bt_mesh_light_ctl_status *status)
{
LOG_INF("CTL status: light=%u, temp=%u", status->current_light, status->current_temp);
dimmer.current_lightness = status->current_light;
}

static void temp_status_handler(struct bt_mesh_light_ctl_cli *cli,
struct bt_mesh_msg_ctx *ctx,
const struct bt_mesh_light_temp_status *status)
{
LOG_INF("CTL temp status: temp=%u, delta_uv=%d",
status->current.temp, status->current.delta_uv);
}

static void dimmer_button_handler(struct dimmer_ctx *ctx, bool pressed)
{
int err;

if (pressed) {
ctx->direction = (ctx->direction == DIM_UP) ? DIM_DOWN : DIM_UP;

ctx->press_start_time = k_uptime_get();
err = k_work_reschedule(&ctx->long_press_start_work,
K_MSEC(SHORT_PRESS_THRESHOLD_MS));

if (err < 0) {
LOG_ERR("Scheduling dimming to start failed: %d", err);
}
} else {
if ((k_uptime_get() - ctx->press_start_time) >= SHORT_PRESS_THRESHOLD_MS) {
/** Button was released after a long time.
* Stop dimming immediately.
*/
err = k_work_reschedule(&ctx->long_press_stop_work, K_NO_WAIT);

if (err < 0) {
LOG_INF("Scheduling dimming to stop failed: %d", err);
}

} else {
/** Button was released after a short time.
* Cancel dimming operation and toggle light on/off with CTL.
*/
k_work_cancel_delayable(&ctx->long_press_start_work);

uint16_t target_lightness = (ctx->direction == DIM_UP) ? 65535 : 0;
LOG_INF("Toggle light %s with CTL (lightness=%u)",
(ctx->direction == DIM_UP ? "ON" : "OFF"), target_lightness);

err = set_light_ctl(target_lightness, NULL);
if (err) {
LOG_ERR("Failed to send CTL set message: %d", err);

/* Fallback to basic on/off control */
struct bt_mesh_onoff_set set = {
.on_off = ctx->direction,
};

if (bt_mesh_model_pub_is_unicast(ctx->onoff_client.model)) {
err = bt_mesh_onoff_cli_set(&ctx->onoff_client, NULL, &set, NULL);
} else {
err = bt_mesh_onoff_cli_set_unack(&ctx->onoff_client, NULL, &set);
}

if (err) {
LOG_ERR("Failed to send OnOff fallback message: %d", err);
}
}
}
}
}

static struct scene_btn_ctx scene_btn = {
.current_scene = 1,
.press_start_time = 0
};

static void scene_button_handler(struct scene_btn_ctx *ctx, bool pressed)
{
if (pressed) {
ctx->press_start_time = k_uptime_get();
} else {
int err;

if (k_uptime_get() - ctx->press_start_time > SHORT_PRESS_THRESHOLD_MS) {
/* Long press, store scene */
LOG_INF("Storing scene %d", ctx->current_scene);
err = bt_mesh_scene_cli_store_unack(&ctx->client, NULL,
ctx->current_scene);

if (err) {
LOG_ERR("Failed to send Scene Store message: %d", err);
}
} else {
/* Short press, recall next scene */
ctx->current_scene = (ctx->current_scene >= SCENE_COUNT) ?
1 : ctx->current_scene + 1;
LOG_INF("Recalling scene %d", ctx->current_scene);
err = bt_mesh_scene_cli_recall_unack(&ctx->client, NULL,
ctx->current_scene, NULL);

if (err) {
LOG_ERR("Failed to send Scene Recall message: %d", err);
}
}
}
}

static void button_handler_cb(uint32_t pressed, uint32_t changed)
{
if (!bt_mesh_is_provisioned()) {
LOG_ERR("Node is not provisioned");
return;
}

if (changed & BIT(0)) {
dimmer_button_handler(&dimmer, pressed & BIT(0));
}
if (changed & BIT(1)) {
scene_button_handler(&scene_btn, pressed & BIT(1));
}
}

/* Set up a repeating delayed work to blink the DK's LEDs when attention is
* requested.
*/
static struct k_work_delayable attention_blink_work;
static bool attention;

static void attention_blink(struct k_work *work)
{
static int idx;
const uint8_t pattern[] = {
#if DT_NODE_EXISTS(DT_ALIAS(sw0))
BIT(0),
#endif
#if DT_NODE_EXISTS(DT_ALIAS(sw1))
BIT(1),
#endif
#if DT_NODE_EXISTS(DT_ALIAS(sw2))
BIT(2),
#endif
#if DT_NODE_EXISTS(DT_ALIAS(sw3))
BIT(3),
#endif
};

if (attention) {
dk_set_leds(pattern[idx++ % ARRAY_SIZE(pattern)]);
k_work_reschedule(&attention_blink_work, K_MSEC(30));
} else {
dk_set_leds(DK_NO_LEDS_MSK);
}
}

static void attention_on(const struct bt_mesh_model *mod)
{
attention = true;
k_work_reschedule(&attention_blink_work, K_NO_WAIT);
}

static void attention_off(const struct bt_mesh_model *mod)
{
/* Will stop rescheduling blink timer */
attention = false;
}

static const struct bt_mesh_health_srv_cb health_srv_cb = {
.attn_on = attention_on,
.attn_off = attention_off,
};

static struct bt_mesh_health_srv health_srv = {
.cb = &health_srv_cb,
};

BT_MESH_HEALTH_PUB_DEFINE(health_pub, 0);

static struct bt_mesh_elem elements[] = {
BT_MESH_ELEM(1,
BT_MESH_MODEL_LIST(BT_MESH_MODEL_CFG_SRV,
BT_MESH_MODEL_HEALTH_SRV(&health_srv, &health_pub),
BT_MESH_MODEL_ONOFF_CLI(&dimmer.onoff_client),
BT_MESH_MODEL_LVL_CLI(&dimmer.lvl_client),
BT_MESH_MODEL_LIGHT_CTL_CLI(&dimmer.ctl_client),
BT_MESH_MODEL_SCENE_CLI(&scene_btn.client)),
BT_MESH_MODEL_NONE),
};

static const struct bt_mesh_comp comp = {
.cid = CONFIG_BT_COMPANY_ID,
.elem = elements,
.elem_count = ARRAY_SIZE(elements),
};

const struct bt_mesh_comp *model_handler_init(void)
{
#if IS_ENABLED(CONFIG_BT_MESH_NLC_PERF_CONF)
if (bt_mesh_comp2_register(&comp_p2)) {
printf("Failed to register comp2\n");
}
#endif

static struct button_handler button_handler = {
.cb = button_handler_cb,
};

dk_button_handler_add(&button_handler);
k_work_init_delayable(&attention_blink_work, attention_blink);
k_work_init_delayable(&dimmer.long_press_start_work, dimmer_start);
k_work_init_delayable(&dimmer.long_press_stop_work, dimmer_stop);

return &comp;
}

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Wed, 09 Apr 2025 21:31:37 GMT

I was able to provision with the Android app without error. It seems they added an assert to keep CONFIG_BT_MESH_MAX_CONN = 1. I haven't tested the actual functionality yet.

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Wed, 09 Apr 2025 15:32:09 GMT

Hi Elfving,

I appreciate all your help. Understood about the testing situation. I'll check the new example out and let you know how it goes.

Jack

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Mon, 07 Apr 2025 14:21:34 GMT

Hi Jack, I am deeply sorry about the wait.

I have had one from the relevant R&D team add Light CTL to the light_ctrl example here.

It is worth noting that this sample could be tested more. And one thing he for instance finds missing here is that transitions for Temperature are not printed in console. It is useful to add such printing (to show demonstration of simultaneous transitions for Lightness and Temperature).

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Wed, 12 Mar 2025 17:55:31 GMT

Elfving,

No, I last set:

CONFIG_BT_MAX_CONN=5

CONFIG_BT_MESH_MAX_CONN=1

CONFIG_BT_EXT_ADV_MAX_ADV_SET=10

CONFIG_BT_BUF_CMD_TX_COUNT=5

which doesn't produce an error when configuring.

Other values of MAX_CONN and MESH_MAX_CONN are also ok as long as (I think) MAX_CONN > MESH_MAX_CONN.

If I set MESH_MAX_CONN to 2 or greater I get problems.

Jack

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Wed, 12 Mar 2025 14:45:34 GMT

Thanks for the patience Jack,

I'm waiting for a response from the relevant R&D team. Just one question.

[quote user="ji_584"]

It seems to compile, provision and configure if and only if

CONFIG_BT_MESH_MAX_CONN == 1

[/quote]

This is interesting. But that is in addition to setting CONFIG_BT_MAX_CONN to 1, right?

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Thu, 06 Mar 2025 20:55:08 GMT

Edit: corrected variable name CONFIG_BT_MAX_CONN below

Elfving,

It seems to compile, provision and configure if and only if

CONFIG_BT_MESH_MAX_CONN == 1

Increasing CONFIG_BT_EXT_ADV_MAX_ADV_SET and/or CONFIG_BT_MAX_CONN didn't seem to change this.

Is there a drawback to this setting of CONFIG_BT_MESH_MAX_CONN?

Also, can you tell me the best resources for learning the effects and interactions of these configuration variables? I know how to look up the name to get a description, but the context is sometimes lacking.

I still haven't functionally tested the model once it doesn't throw errors, so I'll do that. It seems like the nRF Mesh app doesn't have a color temperature control, so I'll set up a dimmer example.

Thanks,

Jack

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Thu, 06 Mar 2025 14:00:31 GMT

Hi,

So this issue could be connected to that CONFIG_BT_MESH_MAX_CONN should be set to less than CONFIG_BT_MAX_CONN if you'd use BLE for other purposes in addition to mesh, like SMP. Although it doesn't immediately make sense to me why putting CONFIG_BT_MAX_CONN to 1 should make things work, try lowering CONFIG_BT_MESH_MAX_CONN.

Of course, CONFIG_BT_EXT_ADV_MAX_ADV_SET should be increased by one for each additional advertising set you want to use. If you didn't know exactly how many sets you are using, you could simply increase it one by one and see when it works (ideally for optimum memory use, you should add only that as many as you are using in the application). If this was set to 1 currently, that could also be something that helps us here.

[quote user="ji_584"]

The code that we've been discussing was a graft of the Zephyr test suite with the light_ctrl example code and, as I said earlier, is a mess. Everything else I have tried works worse than that one though. I don't know if that's the best baseline, but there we are.

[/quote]

Understood. I can see if I can get something neater for you later on, though for the time being the project you sent is what we're looking at. You haven't added any other BLE connection to this, like SMP right?

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Fri, 28 Feb 2025 07:49:23 GMT

Elfving, thanks for the update. Just to review (it's been a long thread), I'm looking for an example of CTL working with other relevant models (lightness, on/off, temperature, maybe some others). If someone could just take the light_ctrl example (or any other example) and add CTL, that would be ideal. I'm just trying to get CTL to work some way.

It's not extremely time-critical, we have plenty of other things to do, but if we could get something in the next few weeks it would be helpful. We definitely need to get this working in the end.

Also, we have switched from nRF52840 to nRF54L15 in the meantime, and the behavior is similar. The build files, etc. I have been sending are still from the 840 build.

Thanks,
Jack

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Thu, 27 Feb 2025 13:28:11 GMT

Great! I've forwarded this to the relevant R&D team, and I'll let you know once I hear from them. They said they wanted this. Let me know if there are any updates regarding the urgency of getting this issue fixed.

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Mon, 24 Feb 2025 19:48:27 GMT

By the way, I previously said the error wasn't catastrophic, however, today when I try the issue again, it does sometimes crash after several seconds.

There was one .config in project\build\zephyr and one in project\build\project\, both are included.

devzone.nordicsemi.com/.../.config-light_5F00_ctrl_5F00_sample_2D00_build_2D00_light_5F00_ctrl_5F00_sample_2D00_zephyr.zip

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Mon, 24 Feb 2025 13:26:59 GMT

Could you send me the .config file you get generated for the build?

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Mon, 17 Feb 2025 20:26:11 GMT

Call stack when the error occurs:

[The error occurs due to a message received at this level. The debugger didn't help me trace it further]

bt_hci_cmd_send_sync(uint16_t opcode, struct net_buf * buf, struct net_buf ** rsp) (/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/host/hci_core.c:440)

bt_le_adv_set_enable_ext(struct bt_le_ext_adv * adv, _Bool enable, const struct bt_le_ext_adv_start_param * param) (/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/host/adv.c:371)

[this is where the error is printed]

bt_le_ext_adv_start(struct bt_le_ext_adv * adv, const struct bt_le_ext_adv_start_param * param) (/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/host/adv.c:1656)

adv_start(struct bt_mesh_ext_adv * ext_adv, const struct bt_le_adv_param * param, struct bt_le_ext_adv_start_param * start, const struct bt_data * ad, size_t ad_len, const struct bt_data * sd, size_t sd_len) (/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/mesh/adv_ext.c:203)

bt_mesh_adv_gatt_start(const struct bt_le_adv_param * param, int32_t duration, const struct bt_data * ad, size_t ad_len, const struct bt_data * sd, size_t sd_len) (/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/mesh/adv_ext.c:603)

bt_mesh_pb_gatt_srv_adv_start() (/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/mesh/pb_gatt_srv.c:308)

bt_mesh_adv_gatt_send() (/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/mesh/adv.c:301)

send_pending_adv(struct k_work * work) (/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/mesh/adv_ext.c:359)

work_queue_main(void * workq_ptr, void * p2, void * p3) (/home/user/ncs/v2.8.0/zephyr/kernel/work.c:688)

z_thread_entry(k_thread_entry_t entry, void * p1, void * p2, void * p3) (/home/user/ncs/v2.8.0/zephyr/lib/os/thread_entry.c:48)

[Unknown code] (Unknown Source:0)

The error seems to arise here:

In bt_hci_cmd_send_sync()

(/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/host/hci_core.c:440)

...

case BT_HCI_ERR_INSUFFICIENT_RESOURCES:

return -ENOMEM; (-12)

When there a command

This error code gets returned back up the chain to:

In bt_le_ext_adv_start()

(/home/user/ncs/v2.8.0/zephyr/subsys/bluetooth/host/adv.c:1657)

The error is printed:

...

err = bt_le_adv_set_enable_ext(adv, true, param);

if (err) {

LOG_ERR("Failed to start advertiser");

if (IS_ENABLED(CONFIG_BT_PERIPHERAL) && conn) {

bt_conn_set_state(conn, BT_CONN_DISCONNECTED);

bt_conn_unref(conn);

}

return err;

}

I guess it's something down in the Bluetooth controller.

I tried to turn on some logging and am getting

[00:08:20.424,499] <wrn> bt_hci_core: opcode 0x2039 status 0x0d

[00:08:20.424,560] <err> bt_adv: Failed to start advertiser

[00:08:20.424,591] <err> bt_mesh_adv_ext: Advertising failed: err -12

I think status 0x0d is BT_HCI_ERR_INSUFFICIENT_RESOURCES above, so that's at least consistent.

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Fri, 14 Feb 2025 15:13:48 GMT

I see.

Could you try debugging and figure out where it fails, and exactly what is returning bt_mesh_adv_ext: Advertising failed: err -12?

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Wed, 12 Feb 2025 16:42:30 GMT

I don't see the problem with the default sample app light control.

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Tue, 11 Feb 2025 09:25:31 GMT

Right, sorry about that. Sysbuild is a bit new to me. <project>/build/zephyr/.config contains configs for the entire build, while the configs I referred to can be found in <project>/build/<project>/zephyr/.config. Check there.

[quote user="ji_584"]I don't believe the sysbuild/ipc_radio/prj.conf [/quote]

Good. You having a sysbuild folder there surprised me a bit, as that is something you would typically need for changes in configurations across multiple images, as if you are working with multi-core chips like the 53 or 54. A sysbuild folder doesn't spawn on my side when building light_ctrl for the 52840dk.

[quote user="ji_584"]

autoconf.h contains the line:

[/quote]

Great! Autoconf is essentially the same as .config, just a different use-case.

So I guess that didn't help.

Btw, I assume selecting the device in the scanner page of the app when using a completely default sample works fine? Could you check?

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Fri, 07 Feb 2025 23:03:40 GMT

Elfiving,

Thank you for your continued support.

<project>/build/zephyr/.config only contains entries of the form SB_CONFIG.... It doesn't have any text matching MAX_ADV_SET.

When I add the suggested config variable to prj.conf (see below) nothing matching appears in .../.config

When I grep the entire project, MAX_ADV_SET appears in:

light_ctrl_sample/build/light_ctrl_sample/zephyr/misc/generated/configs.c

light_ctrl_sample/build/light_ctrl_sample/zephyr/include/generated/zephyr/autoconf.h

light_ctrl_sample/sysbuild/ipc_radio/prj.conf

light_ctrl_sample/build/light_ctrl_sample/zephyr/misc/generated/syscalls_links/include_zephyr_bluetooth/bluetooth.h

I don't believe the sysbuild/ipc_radio/prj.conf is being used in the build -- I inserted a syntax error into that file and the build proceeded without errors.

autoconf.h contains the line:

#define CONFIG_BT_EXT_ADV_MAX_ADV_SET 5

configs.c contains the line:

GEN_ABSOLUTE_SYM_KCONFIG(CONFIG_BT_EXT_ADV_MAX_ADV_SET, 5);

Next, I added

CONFIG_BT_EXT_ADV_MAX_ADV_SET=10

to the main prj.conf

autoconf.h and configs.c changed accordingly.

I compiled and ran, and got the same error.

[00:00:22.033,569] <wrn> bt_hci_core: opcode 0x2039 status 0x0d
[00:00:22.033,599] <err> bt_adv: Failed to start advertiser
[00:00:22.033,630] <err> bt_mesh_adv_ext: Advertising failed: err -12

Jack

RE: Bluetooth Mesh Light CTL (color tuned light) sample

Elfving — Fri, 07 Feb 2025 12:10:49 GMT

Could you check the value of CONFIG_BT_EXT_ADV_MAX_ADV_SET in the final generated .config file of the build. You can find it in /build/zephyr/.config.

Regards,

Elfving

RE: Bluetooth Mesh Light CTL (color tuned light) sample

ji_584 — Tue, 04 Feb 2025 22:08:13 GMT

Elfving,

I made the conf changes you suggested with no change.

Here is the log for the event. The error message appears as soon as I select device in the scanner page of the app.

*** Booting Mesh Light Fixture v2.8.0-9913506ff072 ***
*** Using nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
Initializing...
[00:00:00.009,002] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.009,033] <inf> fs_nvs: alloc wra: 0, fe8
[00:00:00.009,033] <inf> fs_nvs: data wra: 0, 0
[00:00:00.009,185] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision:
fe 2c f9 6a 7f 36 22 2e a0 79 c0 40 be 2c 03 20 |.,.j.6". .y.@.,.
40 c2 f3 32 |@..2
[00:00:00.013,275] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.013,305] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.013,336] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 254.63788 Build 573996906
[00:00:00.013,854] <inf> bt_hci_core: No ID address. App must call settings_load()
Bluetooth initialized
[00:00:00.015,197] <wrn> bt_mesh_access: Unused space in relation list: 14
[00:00:00.430,297] <inf> bt_hci_core: Identity: D4:B8:86:BC:1B:BE (random)
[00:00:00.430,328] <inf> bt_hci_core: HCI: version 6.0 (0x0e) revision 0x104e, manufacturer 0x0059
[00:00:00.430,358] <inf> bt_hci_core: LMP: version 6.0 (0x0e) subver 0x104e
[00:00:00.435,852] <inf> bt_mesh_provisionee: Device UUID: 8d065d07-ab75-4658-b2f9-a2f8548ac9a7
Mesh initialized
[00:00:04.135,528] <wrn> bt_hci_core: opcode 0x2039 status 0x0d
[00:00:04.135,589] <err> bt_adv: Failed to start advertiser
[00:00:04.135,620] <err> bt_mesh_adv_ext: Advertising failed: err -12

Thanks,

Jack

By the way, I can get another error without rebooting by backing out of the provisioning page and selecting the device from the scanner page again. Apparently, the error isn't catastrophic.

[00:00:00.015,197] <wrn> bt_mesh_access: Unused space in relation list: 14
[00:00:00.430,297] <inf> bt_hci_core: Identity: D4:B8:86:BC:1B:BE (random)
[00:00:00.430,328] <inf> bt_hci_core: HCI: version 6.0 (0x0e) revision 0x104e, manufacturer 0x0059
[00:00:00.430,358] <inf> bt_hci_core: LMP: version 6.0 (0x0e) subver 0x104e
[00:00:00.435,852] <inf> bt_mesh_provisionee: Device UUID: 8d065d07-ab75-4658-b2f9-a2f8548ac9a7
Mesh initialized
[00:00:04.135,528] <wrn> bt_hci_core: opcode 0x2039 status 0x0d
[00:00:04.135,589] <err> bt_adv: Failed to start advertiser
[00:00:04.135,620] <err> bt_mesh_adv_ext: Advertising failed: err -12
[00:08:52.918,304] <wrn> bt_hci_core: opcode 0x2039 status 0x0d
[00:08:52.918,365] <err> bt_adv: Failed to start advertiser
[00:08:52.918,395] <err> bt_mesh_adv_ext: Advertising failed: err -12
[00:09:08.785,827] <wrn> bt_hci_core: opcode 0x2039 status 0x0d
[00:09:08.785,858] <err> bt_adv: Failed to start advertiser
[00:09:08.785,888] <err> bt_mesh_adv_ext: Advertising failed: err -12

devzone.nordicsemi.com/.../45853.prj.conf