NCS Mesh: Transferring Composition Data fails

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Mon, 12 Dec 2022 10:01:38 GMT

Hello, provided fix seems to solve the issue, thank you.

However I am getting warning "W: No matching TX context for ack". What it actually means and how to resolve it?

My Mesh buffers are configured with following:

CONFIG_BT_MESH_ADV_BUF_COUNT=35
CONFIG_BT_MESH_TX_SEG_MAX=32
CONFIG_BT_MESH_RX_SEG_MAX=32
CONFIG_BT_MESH_PB_GATT=y
CONFIG_BT_MESH_PB_ADV=y
CONFIG_BT_MESH_TX_SEG_MSG_COUNT=5

I have tried to increase ADV_BUF_COUNT to 45 and TX_SEG_MSG_COUNT to 7 but that did not help.

RE: NCS Mesh: Transferring Composition Data fails

tesc — Mon, 31 Oct 2022 15:37:56 GMT

Hi,

The fixes were merged to the Zephyr project through the following pull requests, about half a year ago:

I am however unable to find any mention of those fixes in the release notes, just as you are.

There is no table of nRF Connect SDK to Zephyr version mapping, but the nRF Connect SDK release notes list the upstream Zephyr commit, as can be seen e.g. for the current main branch of nRF Connect SDK: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/releases/release-notes-changelog.html#zephyr

You can also deduce Zephyr version from the Zephyr Project documentation hosted on developer.nordicsemi.com, where there is a drop-down in the top right corner of the page for selecting nRF Connect SDK version.

Regards,
Terje

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Mon, 31 Oct 2022 09:59:59 GMT

Hi Mttrinh,

I do not see this fix in a list of addressed issues of Zephyr 3.1.0 documentation.

Also is there available table of Zephyr version used in particular NCS version, so I can check which NCS version contains e.g. Zephyr 3.1.0.

RE: NCS Mesh: Transferring Composition Data fails

Mttrinh — Fri, 24 Jun 2022 13:26:31 GMT

Hi,

The fixes are in downstream already, in zephyr-v3.1.0. You can check yourself in your version by calling this:

git show 0aa0913ca5d6ca1708b720d28ade8c99a16a416c
git show dbc76894049660b007342b8b33fb2dab45980186

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Thu, 23 Jun 2022 13:40:07 GMT

Hi, Mttrinh. Thanks for the provided solution.

Will these bugs be fixed in the next SDK release?

RE: NCS Mesh: Transferring Composition Data fails

Mttrinh — Fri, 06 May 2022 13:20:51 GMT

Hi,

There was Bluetooth Host bug for authentication frames with data larger than 255 bytes. This is fix in upstream: https://github.com/zephyrproject-rtos/zephyr/pull/45232

Timeout is also possible since default configuration client timeout doesn't consider large composition data. This PR allows to tune timeout:
https://github.com/zephyrproject-rtos/zephyr/pull/44825

You can apply changes from these PRs to your project. Unfortunately both PRs are on upstream and will be available in NCS repo after next upmerge.

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Thu, 05 May 2022 08:58:19 GMT

Hi, did you reproduce the issue with provided files?

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Mon, 25 Apr 2022 11:47:55 GMT

Yes, please find the project files attached.

I am using VS Code with Connect SDK 1.7.0.

Project Files

RE: NCS Mesh: Transferring Composition Data fails

Mttrinh — Mon, 25 Apr 2022 10:58:11 GMT

Hi,

Sorry for the late update.

I haven't been able to run the project with the changes you provided. Can you provide me the files including the changes?

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Tue, 12 Apr 2022 14:16:04 GMT

[quote userid="15475" url="~/f/nordic-q-a/85847/ncs-mesh-transferring-composition-data-fails/363050#363050"]Also, what phones have you tested it on?[/quote]

I tested it on iPad, Mesh app version 3.1.4. And also tested it with BlueZ stack on proprietary hardware.

RE: NCS Mesh: Transferring Composition Data fails

Mttrinh — Tue, 12 Apr 2022 13:57:56 GMT

Hi,

Also, what phones have you tested it on?

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Tue, 12 Apr 2022 09:35:23 GMT

Hi, thanks for reply.

I reproduced the issue with samples/bluetooth/mesh/light project. However I do not always get error from the device, most of the time composition reading fails without anything printed out via RTT.

I used nrf52840dk board. And made following modifications. In prj.conf added:

CONFIG_BT_MESH_DK_PROV_OOB_BLINK=n
CONFIG_BT_MESH_DK_PROV_OOB_BUTTON=n

CONFIG_BT_MESH_LIGHT_CTL_SRV=y
CONFIG_BT_MESH_LIGHTNESS_SRV=y
CONFIG_BT_MESH_LIGHT_TEMP_SRV=y

CONFIG_BT_MESH_DTT_SRV=y
CONFIG_BT_MESH_DTT_SRV_PERSISTENT=y
CONFIG_BT_MESH_PONOFF_SRV=y
CONFIG_BT_MESH_SCENE_SRV=y
CONFIG_BT_MESH_LVL_SRV=y
CONFIG_BT_MESH_TIME_SRV=y
CONFIG_BT_MESH_SCHEDULER_SRV=y
CONFIG_BT_MESH_SENSOR_SRV=y
CONFIG_BT_MESH_SENSOR_SRV_SENSORS_MAX=6
CONFIG_BT_MESH_SENSOR_SRV_SETTINGS_MAX=12
CONFIG_BT_MESH_PROP_SRV=y
CONFIG_BT_MESH_LIGHT_CTRL_SRV=y
CONFIG_BT_MESH_LIGHT_HSL_SRV=y

# Set RTT console
CONFIG_USE_SEGGER_RTT=y
CONFIG_CONSOLE=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n

# Set logging
CONFIG_LOG=y
CONFIG_LOG_DEFAULT_LEVEL=4

# Set Mesh Buffer Size
CONFIG_BT_MESH_ADV_BUF_COUNT=35
CONFIG_BT_MESH_TX_SEG_MAX=32

# Set Zephyr BT Controller
CONFIG_BT_LL_SOFTDEVICE=n
CONFIG_BT_LL_SW_SPLIT=y

# Error Tracing
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_DEBUG=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_OPTIMIZATIONS=n
CONFIG_ASSERT_NO_MSG_INFO=n
CONFIG_THREAD_ANALYZER=y
CONFIG_THREAD_NAME=y

In model_handler.c added:

/* Light Lightness Server */
static void light_set(struct bt_mesh_lightness_srv *srv,
		      struct bt_mesh_msg_ctx *ctx,
		      const struct bt_mesh_lightness_set *set,
		      struct bt_mesh_lightness_status *rsp)
{
}

static void light_get(struct bt_mesh_lightness_srv *srv,
		      struct bt_mesh_msg_ctx *ctx,
		      struct bt_mesh_lightness_status *rsp)
{
}


/* Light CTL */
static void light_ctl_temp_set(struct bt_mesh_light_temp_srv *srv,
			struct bt_mesh_msg_ctx *ctx,
			const struct bt_mesh_light_temp_set *set,
			struct bt_mesh_light_temp_status *rsp)
{
}

static void light_ctl_temp_get(struct bt_mesh_light_temp_srv *srv,
			struct bt_mesh_msg_ctx *ctx,
			struct bt_mesh_light_temp_status *rsp)
{	
}

static void light_ctl_range_update(struct bt_mesh_light_temp_srv *srv,
			struct bt_mesh_msg_ctx *ctx,
			const struct bt_mesh_light_temp_range *old_range,
			const struct bt_mesh_light_temp_range *new_range)
{	
}
static const struct bt_mesh_lightness_srv_handlers ctl_lightness_srv_handlers = {
	.light_set = light_set,
	.light_get = light_get,
};

static const struct bt_mesh_light_temp_srv_handlers ctl_light_temp_handlers = {
	.set = light_ctl_temp_set,
	.get = light_ctl_temp_get,
	.range_update = light_ctl_range_update,
};

static struct bt_mesh_light_ctl_srv light_ctl_srv = 
	BT_MESH_LIGHT_CTL_SRV_INIT(&ctl_lightness_srv_handlers, &ctl_light_temp_handlers);

static struct bt_mesh_lightness_srv lightness_srv =
	BT_MESH_LIGHTNESS_SRV_INIT(&ctl_lightness_srv_handlers);

/* Light LC Server */
static struct bt_mesh_light_ctrl_srv light_ctrl_srv =
	BT_MESH_LIGHT_CTRL_SRV_INIT(&light_ctl_srv.lightness_srv);

/* Scene Server */
static struct bt_mesh_scene_srv scene_srv[7];

/* Generic Property Server */
static struct bt_mesh_prop prop[2] = {0};
static struct bt_mesh_prop_srv prop_srv = BT_MESH_PROP_SRV_INIT((struct bt_mesh_prop *const)&prop, 2, NULL, NULL);
static struct bt_mesh_prop_srv prop_srv1 = BT_MESH_PROP_SRV_INIT((struct bt_mesh_prop *const)&prop, 2, NULL, NULL);
static struct bt_mesh_prop_srv prop_srv2 = BT_MESH_PROP_SRV_INIT((struct bt_mesh_prop *const)&prop, 2, NULL, NULL);
static struct bt_mesh_prop_srv prop_srv3 = BT_MESH_PROP_SRV_INIT((struct bt_mesh_prop *const)&prop, 2, NULL, NULL);
static struct bt_mesh_prop_srv prop_srv4 = BT_MESH_PROP_SRV_INIT((struct bt_mesh_prop *const)&prop, 2, NULL, NULL);



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_SRV(&led_ctx[0].srv),
			BT_MESH_MODEL_LIGHT_CTL_SRV(&light_ctl_srv),
			BT_MESH_MODEL_SCENE_SRV(&scene_srv[0]),
			BT_MESH_MODEL_PROP_SRV_USER(&prop_srv),
			BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv),
			BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv)
			),
		BT_MESH_MODEL_NONE),

	BT_MESH_ELEM(
		2, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[1].srv),
		BT_MESH_MODEL_LIGHT_TEMP_SRV(&light_ctl_srv.temp_srv),
		BT_MESH_MODEL_PROP_SRV_USER(&prop_srv1),
		BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv1),
		BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv1)
		),
		BT_MESH_MODEL_NONE),

	BT_MESH_ELEM(
		3, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[2].srv),
		BT_MESH_MODEL_PROP_SRV_USER(&prop_srv2),
		BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv2),
		BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv2)
		),
		BT_MESH_MODEL_NONE),

	BT_MESH_ELEM(
		4, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[3].srv),
		BT_MESH_MODEL_PROP_SRV_USER(&prop_srv3),
		BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv3),
		BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv3)
		),
		BT_MESH_MODEL_NONE),

	BT_MESH_ELEM(
		5, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[3].srv),
		BT_MESH_MODEL_LIGHT_CTRL_SRV(&light_ctrl_srv),
		BT_MESH_MODEL_SCENE_SRV(&scene_srv[1])
		),
		BT_MESH_MODEL_NONE),

	BT_MESH_ELEM(
		6, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[3].srv),
		BT_MESH_MODEL_PROP_SRV_USER(&prop_srv4),
		BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv4),
		BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv4)
		),
		BT_MESH_MODEL_NONE),



	BT_MESH_ELEM(
		7, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[3].srv),
		BT_MESH_MODEL_HEALTH_SRV(&health_srv, &health_pub),
		BT_MESH_MODEL_LIGHTNESS_SRV(&lightness_srv), 
		BT_MESH_MODEL_SCENE_SRV(&scene_srv[2]),
		BT_MESH_MODEL_PROP_SRV_USER(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv)
		),
		BT_MESH_MODEL_NONE),

	BT_MESH_ELEM(
		8, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[3].srv),
		BT_MESH_MODEL_HEALTH_SRV(&health_srv, &health_pub),
		BT_MESH_MODEL_LIGHTNESS_SRV(&lightness_srv), 
		BT_MESH_MODEL_SCENE_SRV(&scene_srv[3]),
		BT_MESH_MODEL_PROP_SRV_USER(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv)
		),
		BT_MESH_MODEL_NONE),

	BT_MESH_ELEM(
		9, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[3].srv),
		BT_MESH_MODEL_HEALTH_SRV(&health_srv, &health_pub),
		BT_MESH_MODEL_LIGHTNESS_SRV(&lightness_srv), 
		BT_MESH_MODEL_SCENE_SRV(&scene_srv[4]),
		BT_MESH_MODEL_PROP_SRV_USER(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv)
		),
		BT_MESH_MODEL_NONE),

	BT_MESH_ELEM(
		10, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[3].srv),
		BT_MESH_MODEL_HEALTH_SRV(&health_srv, &health_pub),
		BT_MESH_MODEL_LIGHTNESS_SRV(&lightness_srv), 
		BT_MESH_MODEL_SCENE_SRV(&scene_srv[5]),
		BT_MESH_MODEL_PROP_SRV_USER(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv)
		),
		BT_MESH_MODEL_NONE),

	BT_MESH_ELEM(
		11, BT_MESH_MODEL_LIST(
		BT_MESH_MODEL_ONOFF_SRV(&led_ctx[3].srv),
		BT_MESH_MODEL_HEALTH_SRV(&health_srv, &health_pub),
		BT_MESH_MODEL_LIGHTNESS_SRV(&lightness_srv), 
		BT_MESH_MODEL_SCENE_SRV(&scene_srv[6]),
		BT_MESH_MODEL_PROP_SRV_USER(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_MFR(&prop_srv),
		BT_MESH_MODEL_PROP_SRV_ADMIN(&prop_srv)
		),
		BT_MESH_MODEL_NONE),
};

For reading composition I used nRF Mesh app.

RE: NCS Mesh: Transferring Composition Data fails

Mttrinh — Mon, 11 Apr 2022 14:17:24 GMT

Hi,

We have tried to reproduce the issue on our side but didn't succeed. What example are you testing with and have you made any other modifications?

Can you give me a step-by-step procedure on how to reproduce this?

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Fri, 08 Apr 2022 14:16:01 GMT

Hi, I tried to set it to 5 and 15. However still unable to read Device Composition. Below snippet of the error.

So error slightly changed, if I do not set this config then I have previously posted error.

RE: NCS Mesh: Transferring Composition Data fails

Mttrinh — Mon, 28 Mar 2022 10:55:56 GMT

Hi,

I have been sick the past week and out of office so there haven't been any progress on this issue yet. Did you try increasing CONFIG_BT_MESH_TX_SEG_MSG_COUNT more than 3? Do you get the same error?

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Wed, 23 Mar 2022 07:37:22 GMT

Hi, is there any update regarding this issue?

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Thu, 17 Mar 2022 15:03:04 GMT

I tried, but it did not help.

RE: NCS Mesh: Transferring Composition Data fails

Mttrinh — Thu, 17 Mar 2022 14:30:44 GMT

Hi,

Can you try increasing CONFIG_BT_MESH_TX_SEG_MSG_COUNT in proj.conf to 3? Does it help?

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Thu, 17 Mar 2022 09:58:10 GMT

Yes, see snippet below.

RE: NCS Mesh: Transferring Composition Data fails

Mttrinh — Thu, 17 Mar 2022 09:51:30 GMT

Hi,

Are you receiving any error code on the nRF side?

RE: NCS Mesh: Transferring Composition Data fails

mesh777 — Wed, 16 Mar 2022 15:23:54 GMT

Hi, thanks for reply. This is also what we expect that composition size limit is around 380 Bytes. However in my case transfer fails when data exceeds around 250 Bytes (with 21 segment message it works, 22 does not).

RE: NCS Mesh: Transferring Composition Data fails

Mttrinh — Wed, 16 Mar 2022 15:13:54 GMT

Hi,

Currently only one composition data page is described in the mesh specification, and so if you put too much on the device then you will exceed the available space for composition data. The spec mentions more composition pages, but unfortunately they are only reserved for future use

Mesh Profile Specification v1.0.1 section 4.2.1 Composition Data. The size of the composition data pages are restricted to the maximum useful access payload size of 376 octets, and composition data page 0 should contain, among other things, element descriptions.