ncs-zigbee - Configuration issue with custom cluster

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Wed, 18 Mar 2026 13:44:39 GMT

Hello!
Thank you 🙂 I will keep it in mind if I actually get to test some of the Nordic Devices to use with Home Assistant (with Z2M). Thank you 🙂

Best regards,

Edvin

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Tue, 17 Mar 2026 20:54:07 GMT

Hi Edvin,

thanks for testing it! I´m curious. After all, I never checked the attribute count because I was sure it was correct...

Anyway, I think it was a good lesson for me because this shell application is really helpful, and it looks like Zigbee2Mqtt is now working as well. I also updated the configuration files to the latest version of Z2M (tested with my DK).

I think we can close the thread here.

Many thanks for your patience 🙂.

Feel free to share the GitHub project from me as a reference for using ncs-zigbee together with Zigbee2Mqtt and custom clusters, if someone faces similar issues.

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Tue, 17 Mar 2026 14:18:12 GMT

Hello,

Thank you. That was it.

So I fiddled around with this for a bit.

There were two issues. One was that the command for enabling subscribtions was wrong (or the configuration of the attribute was incorrect).

Without any modifications to your application, this command worked:

uart:~$ zcl subscribe on 0x98e5 10 0x1A0B 0x0104 0x00 33 5 20

As you can see, I replaced 16 with 33. This parameter in particular, refers to the attribute type, and it is a hexadecimal number. In your zb_beelight_voc_cluster.h:

#define ZB_SET_ATTR_DESCR_WITH_ZB_BEELIGHT_ATTR_VOC_MEASUREMENT_VALUE_ID(data_ptr)      \
{                                                                                       \
    ZB_BEELIGHT_ATTR_VOC_MEASUREMENT_VALUE_ID,                                          \
    ZB_ZCL_ATTR_TYPE_U16,                                                               \
    ZB_ZCL_ATTR_ACCESS_READ_ONLY | ZB_ZCL_ATTR_ACCESS_REPORTING,                        \
    (ZB_ZCL_NON_MANUFACTURER_SPECIFIC),                                                 \
    (void*) data_ptr                                                                    \
}

you state that this attribute is using ZB_ZCL_ATTR_TYPE_U16, which is defined as 0x21 (=33). This is the parameter you should use in your "subscribe on" command.

However, it still failed, but increasing the BEELIGHT_REPORT_ATTR_COUNT to 10 sovled this issue.

Now I was able to both bind, read and enable subscriptions on the device.

Best regards,

Edvin

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Mon, 16 Mar 2026 18:32:04 GMT

Hi Edvin

please use these modified files. Just replace the folder from your ncs-zigbee addon.

devzone.nordicsemi.com/.../ncs_2D00_zigbee.zip

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Mon, 16 Mar 2026 15:03:49 GMT

Ah now I get your point. Are you testing with Windows? AFAIK patching causes trouble on Windows. I will send you the modified files and the locations later.

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Mon, 16 Mar 2026 14:52:45 GMT

I don't think those patches work for me. They don't output anything. It just fails silently. The only instances I have of ZB_BEELIGHT_DECLARE_CO2_MEASUREMENT_ATTRIB_LIST is in main.c and in the patch file itself.

That is why I was hoping you could provide them.

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Mon, 16 Mar 2026 14:09:23 GMT

The patch 0001-Add-BeeLight-specific-clusters.patch from "patches" should add them

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Mon, 16 Mar 2026 13:50:43 GMT

Ok, in my NCS (v2.9.2 and zigbee addon), ZB_BEELIGHT_DECLARE_CO2_MEASUREMENT_ATTRIB_LIST is not defined. In what file is that defined? Are there any other custom files that are present there? Can you please let me know the path to them, and upload them here?

BR,
Edvin

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Mon, 16 Mar 2026 13:15:51 GMT

Hi Edvin ,

I tested the app directory on my Ubuntu machine and after adding "+bsec" to the group-filter in the west.yml of the "app" directory, it works:

1. Change group-filter in west.yml to group-filter: [+bsec, +bsec2]
2. Run west init -l . in "app" directory
3. Run "west update"
4. Run a build for the nRF54L15 DK

west build --build-dir /home/daniel/Downloads/app/build /home/daniel/Downloads/app --pristine --board nrf54l15dk/nrf54l15/cpuapp -- -DNCS_TOOLCHAIN_VERSION="NONE" -DEXTRA_CONF_FILE="config/debug.conf;boards/log_on_uart.conf" -DEXTRA_DTC_OVERLAY_FILE=boards/nrf54l15dk_nrf54l15_cpuapp.overlay -DDEBUG_THREAD_INFO=Off -Dapp_DEBUG_THREAD_INFO=Off

I use VS Code for building

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Mon, 16 Mar 2026 11:58:12 GMT

Hi Edvin,

No, I didn´t test it in an unmodified version of the Zigbee Addon because it requires additional clusters. I will test the app folder on my system and see what´s going on here and keep you updated.

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Mon, 16 Mar 2026 11:44:15 GMT

I see the same build log now, that I did when I tried to pull it from github:
devzone.nordicsemi.com/.../1067.build_5F00_log.txt

I did not see the same in the previous version of the app that you uploaded (the one where I couldn't read the cluster).

Did you test this in an unmodified version of the zigbee addon? One where you, apart from the two west commands in this guide, doesn't have any modified files inside the SDK?

BR,
Edvin

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Mon, 16 Mar 2026 11:14:34 GMT

Hi,

please use this app folder. I also add the README so you have everything in place.

devzone.nordicsemi.com/.../0131.app.zip

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Mon, 16 Mar 2026 11:05:36 GMT

Ok, it no longer complains about that. But it still doesn't build. Can you please a standalone application folder that will build with the NCS Zigbee addon v1.2.1, with no other modifications than the bme68x driver, please?

Best regards,

Edvin

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Mon, 16 Mar 2026 09:14:29 GMT

Hi Edvin,

it´s the BME driver from the Nordic repo

https://docs.nordicsemi.com/bundle/ncs-3.1.0/page/nrf/drivers/bme68x_iaq.html

It should work when you use this west.yml

https://github.com/Kampi/BeeLight/blob/2.1_Dev/firmware/app/west.yml

Everything special is added by batches, and regular Nordic stuff is the base.

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Mon, 16 Mar 2026 08:58:38 GMT

I am sorry, but now I can't build it. Did you by chance add some external drivers for the BME688 in your NCS? If so, you will probably see it in your manifest file (west.yml, either in zephyr\west.yml or nrf\west.yml)? If so, can you share what you added? Or the entire files if you are not sure?

Best regards,

Edvin

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Sat, 14 Mar 2026 10:04:59 GMT

Hi Edvin

I was able to reproduce the issue. The issue is caused by a missing BME688 in the device tree and config. Please use the attached files. I added the sensor to the firmware, but didn´t connect it. You can now read the cluster.

uart:~$ zcl attr read 0x4b08 10 0x1A0A 0x0104 0x0000
ID: 0 Type: 21 Value: 131
Done
[00:03:22.843,872] <inf> zigbee.eprxzcl: Received ZCL command (1): src_addr=0x4b08(short) src_ep=10 dst_ep=64 cluster_id=0x1a0a profile_id=0x0104 cmd_dir=1 common_cmd=1 cmd_id=0x01 cmd_seq=1 disable_def_resp=1 manuf_code=void payload=[000000218300] (1)

Please download the latest "app" from the GitHub repo:

https://github.com/Kampi/BeeLight/tree/2.1_Dev/firmware/app

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Fri, 13 Mar 2026 11:17:11 GMT

Hello,

Thank you,

I was able to build and connect to your device, but I was not able to read the attribute, as you described:

[00:00:00.000,872] <inf> ieee802154_nrf5: nRF5 802154 radio initialized
*** Booting nRF Connect SDK v2.9.2-4ab7b98fc76f ***
*** Using Zephyr OS v3.7.99-aa34a5632971 ***
[00:00:00.008,578] <inf> app: Starting Zigbee R23 shell application
[00:00:00.008,767] <inf> app: Zigbee R23 shell application started
uart:~$ bdb role zc
Zigbee shell does not erase the NVRAM between reboots, but is not aware of the previously configured role.
Remember to set the coordinator role after rebooting the device.
Coordinator set
Done
uart:~$ bdb channel 21
Setting channel to 21
Done
uart:~$ bdb start
Started coordinator
Done
[00:00:13.863,309] <inf> zigbee_app_utils: Production configuration is not present or invalid (status: -1)
[00:00:13.863,533] <inf> zigbee_app_utils: Zigbee stack initialized
[00:00:13.865,561] <inf> zigbee_app_utils: Device started for the first time
[00:00:13.865,569] <inf> zigbee_app_utils: Start network formation
[00:00:14.374,291] <inf> zigbee_app_utils: Unimplemented signal (signal: 59, status: 0)
[00:00:14.374,868] <inf> zigbee_app_utils: Network formed successfully, start network steering (Extended PAN ID: f4ce368b0c20a0f3, PAN ID: 0x97c3)
[00:00:14.858,785] <inf> zigbee_app_utils: Unimplemented signal (signal: 59, status: 0)
[00:00:14.859,419] <inf> zigbee_app_utils: Joined network successfully (Extended PAN ID: f4ce368b0c20a0f3, PAN ID: 0x97c3)
[00:00:23.230,935] <inf> zigbee_app_utils: Device authorization event received (short: 0x2496, long: 86d79ac5bae41f11, authorization type: 3, authorization status: 0)
[00:00:23.231,157] <inf> zigbee_app_utils: Unimplemented signal (signal: 53, status: 0)
[00:00:23.231,371] <inf> zigbee_app_utils: Device update received (short: 0x2496, long: 86d79ac5bae41f11, status: 1)
[00:00:23.415,910] <inf> zigbee_app_utils: New device commissioned or rejoined (short: 0x2496)
[00:00:24.250,079] <inf> zigbee_app_utils: Unimplemented signal (signal: 53, status: 0)
[00:00:24.265,098] <inf> zigbee_app_utils: Unimplemented signal (signal: 59, status: 0)
uart:~$ zdo bind on 86d79ac5bae41f11 10 f4ce368b0c20a0f3 64 0x1A0A 0x2496
Done
uart:~$ zdo bind on 86d79ac5bae41f11 10 f4ce368b0c20a0f3 64 0x1A0B 0x2496
Done
uart:~$ zdo bind on 86d79ac5bae41f11 10 f4ce368b0c20a0f3 64 0x1A0C 0x2496
Done
uart:~$ zcl attr read 0x2496 10 0x1A0A 0x0104 0x0000
Error: Default Response received;
Command: 0, Status: 195
[00:02:34.121,247] <inf> zigbee.eprxzcl: Received ZCL command (0): src_addr=0x2496(short) src_ep=10 dst_ep=64 cluster_id=0x1a0a profile_id=0x0104 cmd_dir=1 common_cmd=1 cmd_id=0x0b cmd_seq=0 disable_def_resp=1 manuf_code=void payload=[00c3] (0)
uart:~$ zcl subscribe on 0x2496 10 0x1A0B 0x0104 0x00 16 5 20
[00:03:23.684,734] <inf> zigbee.eprxzcl: Received ZCL command (1): src_addr=0x2496(short) src_ep=10 dst_ep=64 cluster_id=0x1a0b profile_id=0x0104 cmd_dir=1 common_cmd=1 cmd_id=0x0b cmd_seq=1 disable_def_resp=1 manuf_code=void payload=[06c3] (1)
Error: Request timed out
uart:~$

Are you sure we are running the same application? The only change I did was that I changed the network channel map in the zigbee_conf.yml.

Best regards,

Edvin

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Thu, 05 Mar 2026 19:23:37 GMT

Hi Edvin,

I prepared a configuration for the nRF54L15DK that uses generated values rather than sensor values.

You must do the following:

- Build and flash the app for the nRF54L15DK. Use the debug.conf from "config" to enable the debug mode

devzone.nordicsemi.com/.../3073.app.zip

- Build the config (zigbee_config.yaml) with the right address from PM_ZBOSS_PRODUCT_CONFIG_OFFSET in build/<app>/zephyr/include/generated/pm_config.h with

nrfutil nrf5sdk-tools zigbee production_config zigbee_config.yml zigbee_config.hex --offset <Address>

- Upload the config

nrfjprog --program zigbee_config.hex --verify

- On the Zigbee shell run

nvram disable
bdb role zc
bdb channel 11
bdb start

- Reset the nRF54L DK

- Start with the Zigbee commands

- You should get this output on the nRF54L15DK

00> [00:02:00.007,045] <inf> light: 5-minute periodic callback triggered, sampling light sensor...

00> [00:02:00.007,049] <wrn> light: Device is not ready!

00> [00:02:00.007,053] <inf> light: Sending fake data...

00> [00:02:00.007,104] <dbg> app: zbus_on_light_callback: Light value: 10414

00> [00:02:00.007,119] <dbg> app: zbus_on_light_callback: Light min: 0

00> [00:02:00.007,127] <dbg> app: zbus_on_light_callback: Light max: 3011

00> [00:02:10.006,954] <dbg> events: handle_5min_timeout: 5 min timeout

00> [00:02:10.006,979] <wrn> env: Device is not ready!

00> [00:02:10.006,984] <inf> env: Sending fake data...

00> [00:02:10.007,029] <dbg> app: zbus_on_env_callback: Temperature: 3600

00> [00:02:10.007,066] <dbg> app: zbus_on_env_callback: Pressure: 0

00> [00:02:10.007,102] <dbg> app: zbus_on_env_callback: Humidity: 3800

00> [00:02:10.007,115] <inf> light: 5-minute periodic callback triggered, sampling light sensor...

00> [00:02:10.007,119] <wrn> light: Device is not ready!

00> [00:02:10.007,123] <inf> light: Sending fake data...

00> [00:02:10.007,178] <dbg> app: zbus_on_light_callback: Light value: 10792

00> [00:02:10.007,193] <dbg> app: zbus_on_light_callback: Light min: 0

00> [00:02:10.007,200] <dbg> app: zbus_on_light_callback: Light max: 3011

00> [00:02:20.007,013] <dbg> events: handle_5min_timeout: 5 min timeout

00> [00:02:20.007,038] <wrn> env: Device is not ready!

00> [00:02:20.007,043] <inf> env: Sending fake data...

00> [00:02:20.007,089] <dbg> app: zbus_on_env_callback: Temperature: 3900

00> [00:02:20.007,125] <dbg> app: zbus_on_env_callback: Pressure: 0

00> [00:02:20.007,161] <dbg> app: zbus_on_env_callback: Humidity: 4100

00> [00:02:20.007,174] <inf> light: 5-minute periodic callback triggered, sampling light sensor...

00> [00:02:20.007,178] <wrn> light: Device is not ready!

00> [00:02:20.007,182] <inf> light: Sending fake data...

00> [00:02:20.007,237] <dbg> app: zbus_on_light_callback: Light value: 11140

00> [00:02:20.007,252] <dbg> app: zbus_on_light_callback: Light min: 0

00> [00:02:20.007,259] <dbg> app: zbus_on_light_callback: Light max: 3011

Edit:
Don´t forget to enable the BME688 in Kconfig / remove the ifdef to use the VOC, IAQ and CO2 cluster. I missed it in my app.

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Thu, 05 Mar 2026 13:22:51 GMT

That is great. Are you able to reproduce this on a DK without any external components? Only using the zigbee parts of the application? If so, can you please upload the project here (just zip the application folder and upload it here by dragging and dropping it into the textbox), then I can try to reproduce it locally.

Best regards,

Edvin

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Tue, 03 Mar 2026 19:09:00 GMT

Hi Edvin

I got the shell running and tested my application.

Shell:

Runs on nRF5340DK with the following commands

nvram disable
-> Done
bdb role zc
-> Done
bdb channel 11
-> Done
bdb start
-> Done

[01:00:26.796,112] <inf> zigbee_app_utils: Device update received (short: 0x98e5, long: 86d79ac5bae41fa3, status: 1)

Then I created a binding for the IAQ, VOC and CO2 clusters without issue

zdo bind on 86d79ac5bae41fa3 10 f4ce36b2d4c06ca0 64 0x1A0A 0x98e5
-> Done
zdo bind on 86d79ac5bae41fa3 10 f4ce36b2d4c06ca0 64 0x1A0B 0x98e5
-> Done
zdo bind on 86d79ac5bae41fa3 10 f4ce36b2d4c06ca0 64 0x1A0C 0x98e5
-> Done

And I can also read the clusters

uart:~$ zcl attr read 0x98e5 10 0x1A0A 0x0104 0x0000
ID: 0 Type: 21 Value: 50
Done
[01:10:50.024,078] <inf> zigbee.eprxzcl: Received ZCL command (3): src_addr=0x98e5(short) src_ep=10 dst_ep=64 cluster_id=0x1a0a profile_id=0x0104 cmd_dir=1 common_cmd=1 cmd_id=0x01 cmd_seq=3 disable_def_resp=1 manuf_code=void payload=[000000213200] (3)
uart:~$ zcl attr read 0x98e5 10 0x1A0B 0x0104 0x0000
ID: 0 Type: 21 Value: 0
Done
[01:10:55.334,350] <inf> zigbee.eprxzcl: Received ZCL command (4): src_addr=0x98e5(short) src_ep=10 dst_ep=64 cluster_id=0x1a0b profile_id=0x0104 cmd_dir=1 common_cmd=1 cmd_id=0x01 cmd_seq=4 disable_def_resp=1 manuf_code=void payload=[000000210000] (4)
uart:~$ zcl attr read 0x98e5 10 0x1A0C 0x0104 0x0000
ID: 0 Type: 21 Value: 500
Done
[01:11:00.429,870] <inf> zigbee.eprxzcl: Received ZCL command (5): src_addr=0x98e5(short) src_ep=10 dst_ep=64 cluster_id=0x1a0c profile_id=0x0104 cmd_dir=1 common_cmd=1 cmd_id=0x01 cmd_seq=5 disable_def_resp=1 manuf_code=void payload=[00000021f401] (5)
uart:~$

But I can´t create reporting for the VOC cluster (33 for uint16_t)

uart:~$ zcl subscribe on 0x98e5 10 0x1A0B 0x0104 0x00 16 5 20
Error: Unable to configure attribute 0 reporting. Status: 141

Error: One or more attributes reporting were not configured successfully[01:32:32.295,776] <inf> zigbee.eprxzcl: Received ZCL command (9): src_addr=0x98e5(short) src_ep=10 dst_ep=64 cluster_id=0x1a0b profile_id=0x0104 cmd_dir=1 common_cmd=1 cmd_id=0x07 cmd_seq=9 disable_def_resp=1 manuf_code=void payload=[8d000000] (9)
uart:~$ zcl subscribe on 0x98e5 10 0x1A0B 0x0104 0x00 33 5 20
Error: Unable to configure attribute 0 reporting. Status: 1

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Tue, 03 Mar 2026 11:40:37 GMT

Hi Edvin,

thanks. I found this article already, but I missed the channel command for some reason. I also figured out that the shell example doesn´t work well on the nRF54 because the UART drops characters, etc. I fixed it by using a slower baud rate. Maybe you want to take the issue with you for one of your collegues.

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Tue, 03 Mar 2026 11:32:53 GMT

Hello,

Please check how to use the zigbee shell sample here:

https://docs.nordicsemi.com/bundle/addon-zigbee-r23-latest/page/lib/shell.html#lib-zigbee-shell

The reason it failed was because you didn't specify what role it was supposed to use.

Run these commands first:

bdb role zc (this means "zigbee coordinator". Use bdb role zr for "zigbee router")

bdb channel 21 (or whatever channel you want to use)

bdb start.

See if you can replicate the behavior using the zigbee shell as the coordinator. Then it is easier to say what it is that the Z2M integration tries to do, that is not supported.

Initially, we don't support Z2M, but perhaps I can understand what is failing if I can reproduce the issue you are seeing using something that we do support.

Best regards,

Edvin

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Tue, 03 Mar 2026 09:49:54 GMT

Hi Edvin ,

I´ve tested a bit further with my nRF54L15 DK because my nRF5340 has the same issue. I must modify my project to support the regular nRF54DK so I decided to play around with the light bulb example with Zigbee2MQTT. The example is working without issues in a basic installation Zigbee2Mqtt and then I added the temperature cluster

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

#ifndef ZB_DIMMABLE_LIGHT_H
#define ZB_DIMMABLE_LIGHT_H 1

/**
 *  @defgroup ZB_DEFINE_DEVICE_DIMMABLE_LIGHT Dimmable Light
 *  @{
 *  @details
 *      - @ref ZB_ZCL_BASIC \n
 *      - @ref ZB_ZCL_IDENTIFY \n
 *      - @ref ZB_ZCL_SCENES \n
 *      - @ref ZB_ZCL_GROUPS \n
 *      - @ref ZB_ZCL_ON_OFF \n
 *      - @ref ZB_ZCL_LEVEL_CONTROL
 */

/** Dimmable Light Device ID */
#define ZB_DIMMABLE_LIGHT_DEVICE_ID 0x0101

/** Dimmable light device version */
#define ZB_DEVICE_VER_DIMMABLE_LIGHT 1

/** @cond internals_doc */

/** Dimmable Light IN (server) clusters number */
#define ZB_DIMMABLE_LIGHT_IN_CLUSTER_NUM 7

/** Dimmable Light OUT (client) clusters number */
#define ZB_DIMMABLE_LIGHT_OUT_CLUSTER_NUM 0

/** Dimmable light total (IN+OUT) cluster number */
#define ZB_DIMMABLE_LIGHT_CLUSTER_NUM \
	(ZB_DIMMABLE_LIGHT_IN_CLUSTER_NUM + ZB_DIMMABLE_LIGHT_OUT_CLUSTER_NUM)

/** Number of attribute for reporting on Dimmable Light device */
#define ZB_DIMMABLE_LIGHT_REPORT_ATTR_COUNT \
	(ZB_ZCL_ON_OFF_REPORT_ATTR_COUNT + ZB_ZCL_LEVEL_CONTROL_REPORT_ATTR_COUNT)

/** Continuous value change attribute count */
#define ZB_DIMMABLE_LIGHT_CVC_ATTR_COUNT 1

/** @endcond */ /* internals_doc */

/**
 * @brief Declare cluster list for Dimmable Light device
 * @param cluster_list_name - cluster list variable name
 * @param basic_attr_list - attribute list for Basic cluster
 * @param identify_attr_list - attribute list for Identify cluster
 * @param groups_attr_list - attribute list for Groups cluster
 * @param scenes_attr_list - attribute list for Scenes cluster
 * @param on_off_attr_list - attribute list for On/Off cluster
 * @param level_control_attr_list - attribute list for Level Control cluster
 */
#define ZB_DECLARE_DIMMABLE_LIGHT_CLUSTER_LIST(					   \
	cluster_list_name,							   \
	basic_attr_list,							   \
	identify_attr_list,							   \
	groups_attr_list,							   \
	scenes_attr_list,							   \
	on_off_attr_list,							   \
	level_control_attr_list,						   \
    temp_sensor_attr_list)						   \
	zb_zcl_cluster_desc_t cluster_list_name[] =				   \
	{									   \
		ZB_ZCL_CLUSTER_DESC(						   \
			ZB_ZCL_CLUSTER_ID_IDENTIFY,				   \
			ZB_ZCL_ARRAY_SIZE(identify_attr_list, zb_zcl_attr_t),	   \
			(identify_attr_list),					   \
			ZB_ZCL_CLUSTER_SERVER_ROLE,				   \
			ZB_ZCL_MANUF_CODE_INVALID				   \
		),								   \
		ZB_ZCL_CLUSTER_DESC(						   \
			ZB_ZCL_CLUSTER_ID_BASIC,				   \
			ZB_ZCL_ARRAY_SIZE(basic_attr_list, zb_zcl_attr_t),	   \
			(basic_attr_list),					   \
			ZB_ZCL_CLUSTER_SERVER_ROLE,				   \
			ZB_ZCL_MANUF_CODE_INVALID				   \
		),								   \
		ZB_ZCL_CLUSTER_DESC(						   \
			ZB_ZCL_CLUSTER_ID_SCENES,				   \
			ZB_ZCL_ARRAY_SIZE(scenes_attr_list, zb_zcl_attr_t),	   \
			(scenes_attr_list),					   \
			ZB_ZCL_CLUSTER_SERVER_ROLE,				   \
			ZB_ZCL_MANUF_CODE_INVALID				   \
		),								   \
		ZB_ZCL_CLUSTER_DESC(						   \
			ZB_ZCL_CLUSTER_ID_GROUPS,				   \
			ZB_ZCL_ARRAY_SIZE(groups_attr_list, zb_zcl_attr_t),	   \
			(groups_attr_list),					   \
			ZB_ZCL_CLUSTER_SERVER_ROLE,				   \
			ZB_ZCL_MANUF_CODE_INVALID				   \
		),								   \
		ZB_ZCL_CLUSTER_DESC(						   \
			ZB_ZCL_CLUSTER_ID_ON_OFF,				   \
			ZB_ZCL_ARRAY_SIZE(on_off_attr_list, zb_zcl_attr_t),	   \
			(on_off_attr_list),					   \
			ZB_ZCL_CLUSTER_SERVER_ROLE,				   \
			ZB_ZCL_MANUF_CODE_INVALID				   \
		),								   \
		ZB_ZCL_CLUSTER_DESC(						   \
			ZB_ZCL_CLUSTER_ID_LEVEL_CONTROL,			   \
			ZB_ZCL_ARRAY_SIZE(level_control_attr_list, zb_zcl_attr_t), \
			(level_control_attr_list),				   \
			ZB_ZCL_CLUSTER_SERVER_ROLE,				   \
			ZB_ZCL_MANUF_CODE_INVALID				   \
		),								   \
    	ZB_ZCL_CLUSTER_DESC( \
			ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT, \
			ZB_ZCL_ARRAY_SIZE(temp_sensor_attr_list, zb_zcl_attr_t), \
			(temp_sensor_attr_list), \
			ZB_ZCL_CLUSTER_SERVER_ROLE, \
			ZB_ZCL_MANUF_CODE_INVALID \
    )										\
}


/** @cond internals_doc */
/**
 * @brief Declare simple descriptor for Dimmable Light device
 * @param ep_name - endpoint variable name
 * @param ep_id - endpoint ID
 * @param in_clust_num - number of supported input clusters
 * @param out_clust_num - number of supported output clusters
 */
#define ZB_ZCL_DECLARE_HA_DIMMABLE_LIGHT_SIMPLE_DESC(ep_name, ep_id, in_clust_num, out_clust_num) \
	ZB_DECLARE_SIMPLE_DESC(in_clust_num, out_clust_num);					  \
	ZB_AF_SIMPLE_DESC_TYPE(in_clust_num, out_clust_num) simple_desc_##ep_name =		  \
	{											  \
		ep_id,										  \
		ZB_AF_HA_PROFILE_ID,								  \
		ZB_DIMMABLE_LIGHT_DEVICE_ID,							  \
		ZB_DEVICE_VER_DIMMABLE_LIGHT,							  \
		0,										  \
		in_clust_num,									  \
		out_clust_num,									  \
		{										  \
			ZB_ZCL_CLUSTER_ID_BASIC,						  \
			ZB_ZCL_CLUSTER_ID_IDENTIFY,						  \
			ZB_ZCL_CLUSTER_ID_SCENES,						  \
			ZB_ZCL_CLUSTER_ID_GROUPS,						  \
			ZB_ZCL_CLUSTER_ID_ON_OFF,						  \
			ZB_ZCL_CLUSTER_ID_LEVEL_CONTROL,					  \
    		ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT, \
		}										  \
	}

/** @endcond */ /* internals_doc */

/**
 * @brief Declare endpoint for Dimmable Light device
 * @param ep_name - endpoint variable name
 * @param ep_id - endpoint ID
 * @param cluster_list - endpoint cluster list
 */
#define ZB_DECLARE_DIMMABLE_LIGHT_EP(ep_name, ep_id, cluster_list)		      \
	ZB_ZCL_DECLARE_HA_DIMMABLE_LIGHT_SIMPLE_DESC(ep_name, ep_id,		      \
		ZB_DIMMABLE_LIGHT_IN_CLUSTER_NUM, ZB_DIMMABLE_LIGHT_OUT_CLUSTER_NUM); \
	ZBOSS_DEVICE_DECLARE_REPORTING_CTX(reporting_info## ep_name,		      \
		ZB_DIMMABLE_LIGHT_REPORT_ATTR_COUNT);				      \
	ZBOSS_DEVICE_DECLARE_LEVEL_CONTROL_CTX(cvc_alarm_info## ep_name,	      \
		ZB_DIMMABLE_LIGHT_CVC_ATTR_COUNT);				      \
	ZB_AF_DECLARE_ENDPOINT_DESC(ep_name, ep_id, ZB_AF_HA_PROFILE_ID,	      \
		0,								      \
		NULL,								      \
		ZB_ZCL_ARRAY_SIZE(cluster_list, zb_zcl_cluster_desc_t), cluster_list, \
			(zb_af_simple_desc_1_1_t *)&simple_desc_## ep_name,	      \
			ZB_DIMMABLE_LIGHT_REPORT_ATTR_COUNT,			      \
			reporting_info## ep_name,				      \
			ZB_DIMMABLE_LIGHT_CVC_ATTR_COUNT,			      \
			cvc_alarm_info## ep_name)

/** @} */

#endif /* ZB_DIMMABLE_LIGHT_H */

ZB_DECLARE_DIMMABLE_LIGHT_CLUSTER_LIST(
	dimmable_light_clusters,
	basic_attr_list,
	identify_attr_list,
	groups_attr_list,
	scenes_attr_list,
	on_off_attr_list,
	level_control_attr_list,
    temp_sensor_attr_list);

I get the same error when adding a report interval:

[3.3.2026, 10:43:56] z2m: Request 'zigbee2mqtt/bridge/request/device/reporting/configure' failed with error: 'ZCL command 0x86d79ac5bae41fa3/10 msTemperatureMeasurement.configReport([{"attribute":"measuredValue","minimumReportInterval":60,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Status 'FAILURE')'

So I guess it´s the same reason.

Additional question:
How should the firmware handle a periodic update when not using the report intervals? Just waiting x second and then publishing the new value?

Additional informations:
I´ve checked the Zigbee Weather Station example:

https://github.com/nrfconnect/sdk-nrf/blob/v2.9.2/applications/zigbee_weather_station/src/main.c
https://docs.nordicsemi.com/bundle/ncs-2.6.3/page/nrf/applications/zigbee_weather_station/README.html

I´m a bit more confused because this project uses the same temperature cluster as I use in my modified light bulb but the documentation says that it´s possible to add a binding for periodic notifications.

So I have to test my sensor with the nRF54L15DK and the Shell application to make sure to fix everything in my project. This leads back to the question why the shell example is complaining about a missing configuration, even if I upload it.

RE: ncs-zigbee - Configuration issue with custom cluster

Kampino — Mon, 02 Mar 2026 19:46:00 GMT

Hi Edvin,

I will try it with the NCS Zigbee Shell on my nRF54L15 DK and my sensor. I get this output during the first test of the shell sample:

uart:~$ bdb start
Started router
Done
[00:00:04.469,697] <inf> zigbee_app_utils: Production configuration is not present or invalid (status: -1)
[00:00:04.469,918] <inf> zigbee_app_utils: Zigbee stack initialized
[00:00:04.471,944] <inf> zigbee_app_utils: Device started for the first time
[00:00:04.471,952] <inf> zigbee_app_utils: Start network steering
[00:00:04.471,959] <inf> zigbee_app_utils: Started network rejoin procedure.
[00:00:08.167,488] <inf> zigbee_app_utils: Network steering was not successful (status: -1)
[00:00:12.831,348] <inf> zigbee_app_utils: Network steering was not successful (status: -1)
[00:00:19.488,889] <inf> zigbee_app_utils: Network steering was not successful (status: -1)
[00:00:30.138,843] <inf> zigbee_app_utils: Network steering was not successful (status: -1)
[00:00:48.788,114] <inf> zigbee_app_utils: Network steering was not successful (status: -1)

And I flashed the Zigbee config before by running

nrfjprog --program zigbee_config.hex --verify

With this config

# Enable channel 11 and 16
channel_mask: 0x10800

# You can add an installation code here
# NOTE: This code must be added to the Zigbee network too!
#install_code: 83FED3407A939723A5C639B26916D505

# The Zigbee device address
extended_address: 86D79AC5BAE41F11

tx_power: 0

# Use this to pass specific data to the application
#app_data: 01ABCD

Is there anything special to take care of when using this config file, or why isn´t the MCU using this config?

RE: ncs-zigbee - Configuration issue with custom cluster

Edvin — Mon, 02 Mar 2026 13:43:15 GMT

Hello,

The picture you tried to upload didn't load properly. Can you please try to upload it again?

Is there some way for me to reproduce what you are seeing using some DKs, without a 3rd party Zigbee coordinator? Are you able to reproduce it using the ncs-zigbee\samples\shell, and try to do the same that your zigbee coordinator is doing?

Best regards,

Edvin