QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

RE: QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

Maria Gilje — Tue, 06 Aug 2024 11:56:10 GMT

Hi Deepika B.

[quote user="Deepu Prashanth"]For Developing the code i am Using nRFSDK v2.2.0.[/quote]

This is good to know, thank you. Is there any particular reason that you are not using a more recent version like NCS v2.7.0 or v2.6.1?

[quote user="Deepu Prashanth"]and is there any another way to get temperature value from Bulb(EndDevice) using Report Attribute?[/quote]

Another way to get the data from the light bulb is to send an attribute request from the light switch every time you want to read the temperature value. This does not require a binding.

[quote user="Deepu Prashanth"]1. In this case, once switch found the bulb then we can communicate directly with bulb Without Bind_Req right ? and if switch found bulb then we can receive temperature data without Bind_Req also right?[/quote]

The switch can communicate with the bulb as long as you have the endpoint and short address. If you send an attribute request the binding is not required. You do need to set up a binding to enable attribute reporting though.

[quote user="Deepu Prashanth"]After using modified code also still i am getting same Status 132.[/quote]

Please verify that the temperature cluster is supported on your light bulb by using the zdo_simple_desc_req command in a shell and finding 0x0402 in the out_clusters list.

Build and flash the Zigbee shell sample to an nRF5x DK of your choice. Connect the shell device to a supported serial terminal. Run the shell commands below on the zigbee shell device. Restart the light bulb after starting the network (bdb start).

bdb role zc

bdb start

zdo simple_desc_req 0x2325 10

I inferred the address and endpoint from previous replies. Please correct them if they are incorrect.

If the temperature measurement cluster is not in the out_clusters list, it is not supported on the light bulb and I will help to find out why that is and what we can do.

If you find the temperature measurement cluster in the out_clusters list, please do a sniffer trace of your network and share the capture as a .pcap file here (insert->Image/video/file). See the nRF Sniffer for 802.15.4 user guide if you are unfamiliar.

Best regards,

Maria

RE: QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

Deepu Prashanth — Thu, 01 Aug 2024 13:27:20 GMT

Hi Maria,

For Developing the code i am Using nRFSDK v2.2.0.

After using modified code also still i am getting same Status 132.

LIGHT_SWITCH EXAMPLE 



// Define the IEEE address of the source device (end device)
static zb_ieee_addr_t arr1 = { 0x00, 0x12, 0x4B, 0x00, 0x0A, 0x12, 0x34, 0x56 };

int SendBindReq()
{
    zb_ret_t zb_err_code;
    zb_err_code = (zb_buf_get_out_delayed(send_bind_req));
    if (!zb_err_code)
    {
        LOG_DBG("Buffer is full");
    }
    else
    {
        LOG_INF("SendBindReq: Buffer obtained successfully.");
    }
    return zb_err_code;
}

void send_bind_req(zb_uint8_t param)
{
    zb_bufid_t buf = param;
    zb_zdo_bind_req_param_t *req;
    
    LOG_INF("send_bind_req: >> bind_device param %hd", param);

    req = ZB_BUF_GET_PARAM(buf, zb_zdo_bind_req_param_t);
	ZB_MEMCPY(req->src_address, arr1, sizeof(zb_ieee_addr_t));    
	req->src_endp = bulb_ctx.endpoint;
    req->cluster_id = ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT;  // Correct cluster ID
    req->dst_addr_mode = ZB_APS_ADDR_MODE_64_ENDP_PRESENT;
    req->dst_endp = LIGHT_SWITCH_ENDPOINT;
    req->req_dst_addr = bulb_ctx.short_addr;

	 // Store parameters in the global structure
    bind_req_params.src_endp = bulb_ctx.endpoint;
    bind_req_params.dst_endp = LIGHT_SWITCH_ENDPOINT;
    //bind_req_params.src_address = arr1;
    bind_req_params.cluster_id = ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT;
    bind_req_params.req_dst_addr = bulb_ctx.short_addr;
    
    
    LOG_INF("send_bind_req: Sending bind request to endpoint %d with cluster ID 0x%04x", req->dst_endp, req->cluster_id);
    
    zb_zdo_bind_req(param, zb_bind_callback);
    
    LOG_INF("send_bind_req: << bind_device");
}

void zb_bind_callback(zb_uint8_t param)
{
    zb_bufid_t buf = param;
    zb_zdo_bind_resp_t *bind_resp = (zb_zdo_bind_resp_t*)zb_buf_begin(buf);
	//zb_zdo_bind_req_param_t *req;

     if (param)
    {
        LOG_INF("zb_bind_callback: Bind response received");
        LOG_INF("zb_bind_callback: Status %hd", bind_resp->status);
        if (bind_resp->status != ZB_ZDP_STATUS_SUCCESS)
        {
            // Additional information on the bind request context
            LOG_INF("zb_bind_callback: Status indicates an error or specific condition.");
        }
        LOG_INF("zb_bind_callback: Dst Address %d", bind_req_params.req_dst_addr);
        //LOG_INF("zb_bind_callback: Src Endpoint %d", bind_req_params.src_endp);
        LOG_INF("zb_bind_callback: Dst Endpoint %d", bind_req_params.dst_endp);
		LOG_INF("zb_bind_callback: Src Addr %d",  bind_req_params.src_address);
        zb_buf_free(buf);
    }
    else
    {
        LOG_ERR("zb_bind_callback: Bind response error, param is 0");
    }
}

and i called SendBindReq Function in Find_Light_Bulb_cb Function because i want bind when the switch found Bulb(EndDevice).

/**@brief Callback function receiving finding procedure results.
 *
 * @param[in]   bufid   Reference to Zigbee stack buffer used to pass
 *                      received data.
 */
static void find_light_bulb_cb(zb_bufid_t bufid)
{
	/* Get the beginning of the response. */
	zb_zdo_match_desc_resp_t *resp =
		(zb_zdo_match_desc_resp_t *) zb_buf_begin(bufid);
	/* Get the pointer to the parameters buffer, which stores APS layer
	 * response.
	 */
	zb_apsde_data_indication_t *ind = ZB_BUF_GET_PARAM(bufid,
							   zb_apsde_data_indication_t);
	zb_uint8_t *match_ep;

	if ((resp->status == ZB_ZDP_STATUS_SUCCESS) &&
	    (resp->match_len > 0) &&
	    (bulb_ctx.short_addr == 0xFFFF)) {

		/* Match EP list follows right after response header. */
		match_ep = (zb_uint8_t *)(resp + 1);

		/* We are searching for exact cluster, so only 1 EP
		 * may be found.
		 */
		bulb_ctx.endpoint = *match_ep;
		bulb_ctx.short_addr = ind->src_addr;

		LOG_INF("Found bulb addr: %d ep: %d",
			bulb_ctx.short_addr,
			bulb_ctx.endpoint);

		k_timer_stop(&bulb_ctx.find_alarm);
		dk_set_led_on(BULB_FOUND_LED);

		/* Send bind request */
		LOG_INF("Sending bind request...");
		SendBindReq();

		// /* Send bind request */
		// LOG_INF("Sending bind request...");
		// SendBindReq();
		// Register the callback function for handling attribute reports
    	//ZB_ZCL_REGISTER_DEVICE_CB(temperature_measurement_report_handler);

		
		
	} else {
		LOG_INF("Bulb not found, try again");
	}

	if (bufid) {
		zb_buf_free(bufid);
	}
}

LOGS:
These are the switch Example Serial Terminal Logs:

I: nRF5 802154 radio initialized
*** Booting Zephyr OS build v3.2.99-ncs1 ***
I: Starting ZBOSS Light Switch example
I: ZBOSS Light Switch example started
I: Production configuration is not present or invalid (status: -1)
I: Zigbee stack initialized
I: Joined network successfully on reboot signal (Extended PAN ID: f4ce360848c8e4b3, PAN ID: 0xc863)
I: Found bulb addr: 2325 ep: 10
I: Sending bind request...
I: send_bind_req: >> bind_device param 7
I: send_bind_req: Sending bind request to endpoint 1 with cluster ID 0x0402
I: send_bind_req: << bind_device
I: zb_bind_callback: Bind response received
I: zb_bind_callback: Status 132
I: zb_bind_callback: Status indicates an error or specific condition.
I: zb_bind_callback: Dst Address 2325
I: zb_bind_callback: Dst Endpoint 1
I: zb_bind_callback: Src Addr 536880428
I: Bulb not found, try again

For these Status Issues whether i need to enable anything to support Bind_Req in Switch_Example?

From Past 2 weeks i am facing this issue if i solve this then only i can get Temperature Value from Bulb right? and is there any another way to get temperature value from Bulb(EndDevice) using Report Attribute?

Here, My doubt is usually Bind_Req is for to communicate directly with another device right? so, here I am implementing code once switch found the bulb after i want to send Bind_Req to Light_Bulb.

1. In this case, once switch found the bulb then we can communicate directly with bulb Without Bind_Req right ? and if switch found bulb then we can receive temperature data without Bind_Req also right?

If there is a way can you suggest me how to do that?

Thanks a lot 🙂!!!

Best Regards,
Deepika B.

RE: QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

Maria Gilje — Wed, 31 Jul 2024 13:46:35 GMT

[quote user="Deepu Prashanth"] I implemented Bind_req code in switch example.[/quote]

Your code looks mostly ok, but here are some lines which you need to change.

On line 33 you use &req, but you should not use addressof operator here. Replace the line with ZB_MEMCPY(req->src_address, arr1, sizeof(zb_ieee_addr_t));
On line 34 the source referenced is the source for the ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT, that is: the light bulb. Change the line to req->src_endp = bulb_ctx.endpoint;
On line 37 you need to change the destination to be the light switch, so change the line to req->dst_endp = LIGHT_SWITCH_ENDPOINT;
On line 40 you should log the src_endp instead of the dst_endp.

I am also including the edited version of send_bind_req to make the changes more clear.

void send_bind_req(zb_uint8_t param)
{
    zb_bufid_t buf = param;
    zb_zdo_bind_req_param_t *req;
    static int bind_retry_count = 0;

    LOG_INF("send_bind_req: >> bind_device param %hd", param);

    req = ZB_BUF_GET_PARAM(buf, zb_zdo_bind_req_param_t);
	ZB_MEMCPY(req->src_address, arr1, sizeof(zb_ieee_addr_t));    
	req->src_endp = bulb_ctx.endpoint;
    req->cluster_id = ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT;  // Correct cluster ID
    req->dst_addr_mode = ZB_APS_ADDR_MODE_64_ENDP_PRESENT;
    req->dst_endp = LIGHT_SWITCH_ENDPOINT;
    req->req_dst_addr = bulb_ctx.short_addr;

    LOG_INF("send_bind_req: Sending bind request to endpoint %d with cluster ID 0x%04x", req->src_endp, req->cluster_id);
    
    zb_zdo_bind_req(param, zb_bind_callback);

    LOG_INF("send_bind_req: << bind_device");

    // Increment retry count if needed
    if (bind_retry_count < MAX_BIND_RETRIES)
    {
        bind_retry_count++;
    }
    else
    {
        LOG_ERR("send_bind_req: Maximum bind retries reached");
    }
}

[quote user="Deepu Prashanth"]1. Here, my question is, in switch example i wrote BIND_REQUEST and ZB_BIND_CALLBACK functions and in BULB Example is it required to write BIND_RESPONSE[/quote]

No this is not needed because the ZBOSS stack handles the bind response.

[quote user="Deepu Prashanth"]3. In which switch example how switch will receive the temperature value from bulb?[/quote]

Register an endpoint handler in the switch with ZB_AF_SET_ENDPOINT_HANDLER(<light-switch-endpoint>, <light-switch-endpoint-handler>). You can see an example on how this is done in the Zigbee shell library and in your case the endpoint handler will look something like this:

zb_uint8_t light_switch_ep_handler(zb_bufid_t bufid)
{
	zb_zcl_parsed_hdr_t *cmd_info = ZB_BUF_GET_PARAM(bufid, zb_zcl_parsed_hdr_t);
	size_t payload_length = zb_buf_len(bufid);
	const zb_uint8_t *payload = zb_buf_begin(bufid);

	zb_uint16_t short_addr;
	zb_ieee_addr_t ieee_addr;
	
	switch (ZB_ZCL_PARSED_HDR_SHORT_DATA(cmd_info).source.addr_type) {
	case ZB_ZCL_ADDR_TYPE_SHORT:
		short_addr = ZB_ZCL_PARSED_HDR_SHORT_DATA(cmd_info).source.u.short_addr;
		zb_address_ieee_by_short(short_addr, ieee_addr);
		break;
	case ZB_ZCL_ADDR_TYPE_IEEE:
		ZB_IEEE_ADDR_COPY(ieee_addr, ZB_ZCL_PARSED_HDR_SHORT_DATA(cmd_info).source.u.ieee_addr);
		short_addr = zb_address_short_by_ieee(ieee_addr);
		break;
	}

	char ieee_addr_str[IEEE_ADDR_BUF_SIZE] = { 0 };
	char payload_str[255];
	ieee_addr_to_str(ieee_addr_str, IEEE_ADDR_BUF_SIZE, ieee_addr);
	to_hex_str(payload_str, sizeof(payload_str), payload, payload_length, false);

	LOG_INF("Received ZCL cmd: IEEE_src_addr=%s, cluster_id=0x%04x, cmd_id=0x%02x, payload=[%s]", 
						ieee_addr_str, 
						cmd_info->cluster_id,
						cmd_info->cmd_id,
						payload_str);

	return 0;
}

(Above code was provided by my colleague, Marte)

[quote user="Deepu Prashanth"]and i am getting logs like this and why i am getting status 132. [/quote]

The relevant status definitions are in zboss_api_zdo.h and status 132 (ZB_ZDP_STATUS_NOT_SUPPORTED) means that the requested feature is unsupported on the target device. Based on my findings in your code from above, this status is expected. Let me know if you get the same status after including the changes above.

[quote user="Deepu Prashanth"]2. In Bulb example i used Start_reporting Function and Configuring_reporting_attribute function for to configure and send temperature report to switch.[/quote]

Is there something specific you want us to look at with your implementation on the light bulb?

Best regards,

Maria

RE: QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

Deepu Prashanth — Tue, 30 Jul 2024 12:18:07 GMT

Hi Maria,

I implemented Bind_req code in switch example.

LIGHT_SWITCH EXAMPLE 


// Define the IEEE address of the source device (end device)
static zb_ieee_addr_t arr1 = { 0x00, 0x12, 0x4B, 0x00, 0x0A, 0x12, 0x34, 0x56 };

#define MAX_BIND_RETRIES 3

int SendBindReq()
{
    zb_ret_t zb_err_code;
    zb_err_code = zb_buf_get_out_delayed(send_bind_req);
    if (zb_err_code != RET_OK)
    {
        LOG_DBG("Buffer is full");
    }
    else
    {
        LOG_INF("SendBindReq: Buffer obtained successfully.");
    }
    return zb_err_code;
}

void send_bind_req(zb_uint8_t param)
{
    zb_bufid_t buf = param;
    zb_zdo_bind_req_param_t *req;
    static int bind_retry_count = 0;

    LOG_INF("send_bind_req: >> bind_device param %hd", param);

    req = ZB_BUF_GET_PARAM(buf, zb_zdo_bind_req_param_t);
    ZB_MEMCPY(&req->src_address, arr1, sizeof(zb_ieee_addr_t));
    req->src_endp = LIGHT_SWITCH_ENDPOINT;
    req->cluster_id = ZB_ZCL_CLUSTER_ID_TEMP_MEASUREMENT;  // Correct cluster ID
    req->dst_addr_mode = ZB_APS_ADDR_MODE_64_ENDP_PRESENT;
    req->dst_endp = bulb_ctx.endpoint;
    req->req_dst_addr = bulb_ctx.short_addr;

    LOG_INF("send_bind_req: Sending bind request to endpoint %d with cluster ID 0x%04x", req->dst_endp, req->cluster_id);
    
    zb_zdo_bind_req(param, zb_bind_callback);

    LOG_INF("send_bind_req: << bind_device");

    // Increment retry count if needed
    if (bind_retry_count < MAX_BIND_RETRIES)
    {
        bind_retry_count++;
    }
    else
    {
        LOG_ERR("send_bind_req: Maximum bind retries reached");
    }
}

void zb_bind_callback(zb_uint8_t param)
{
    zb_bufid_t buf = param;
    zb_zdo_bind_resp_t *bind_resp = (zb_zdo_bind_resp_t*)zb_buf_begin(buf);
    static int bind_retry_count = 0;

    if (param)
    {
        LOG_INF("zb_bind_callback: Bind response received");
        LOG_INF("zb_bind_callback: Status %hd", bind_resp->status);

        if (bind_resp->status != ZB_ZDP_STATUS_SUCCESS)
        {
            LOG_INF("zb_bind_callback: Status indicates an error or specific condition.");
            LOG_INF("zb_bind_callback: Status %d", bind_resp->status);

            if (bind_retry_count < MAX_BIND_RETRIES)
            {
                LOG_INF("zb_bind_callback: Retrying bind request...");
                SendBindReq();
            }
            else
            {
                LOG_ERR("zb_bind_callback: Maximum retries reached. Bind failed.");
            }
        }
        else
        {
            LOG_INF("zb_bind_callback: Bind request successful");
            bind_retry_count = 0; // Reset retry count on success
        }

        LOG_INF("zb_bind_callback: Dst Address %d", bulb_ctx.short_addr);
        LOG_INF("zb_bind_callback: Src Endpoint %d", LIGHT_SWITCH_ENDPOINT);
        LOG_INF("zb_bind_callback: Dst Endpoint %d", bulb_ctx.endpoint);

        zb_buf_free(buf);
    }
    else
    {
        LOG_ERR("zb_bind_callback: Bind response error, param is 0");
    }
}

and i am getting logs like this and why i am getting status 132.

I: Production configuration is not present or invalid (status: -1)
I: Zigbee stack initialized
I: Device started for the first time
I: Start network steering
I: Started network rejoin procedure.
I: Joined network successfully (Extended PAN ID: f4ce360848c8e4b3, PAN ID: 0x4a7d)
I: Network rejoin procedure stopped as NOT scheduled.
I: Found bulb addr: 47875 ep: 10
I: Sending bind request...
I: send_bind_req: >> bind_device param 7
I: send_bind_req: Sending bind request to endpoint 10 with cluster ID 0x0402
I: send_bind_req: << bind_device
I: zb_bind_callback: Bind response received
I: zb_bind_callback: Status 132
I: zb_bind_callback: Status indicates an error or specific condition.
I: zb_bind_callback: Status 132
I: zb_bind_callback: Dst Address 47875
I: zb_bind_callback: Src Endpoint 1
I: zb_bind_callback: Dst Endpoint 10
again i am geeting logs like this only? i think may be i need to adjuct long poll?

1. Here, my question is, in switch example i wrote BIND_REQUEST and ZB_BIND_CALLBACK functions and in BULB Example is it required to write BIND_RESPONSE and
2. In Bulb example i used Start_reporting Function and Configuring_reporting_attribute function for to configure and send temperature report to switch.
3. In which switch example how switch will receive the temperature value from bulb?

As I am new to this, please help here get the above information.

Thanks a lot 🙂!!!

Best Regards,
Deepika B

RE: QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

Maria Gilje — Thu, 25 Jul 2024 12:38:52 GMT

Hi Deepika B.

I would like to give you some more specific support, but unfortunately we are a bit short-handed currently, so I will need some more time to help with your specific questions.

In the mean time, familiarize yourself with the Zigbee-related topics in our NCS documentation and let me know if you find the solutions for any of the questions you have.

I will be able to spend some time on this on Monday. Thank you for your patience.

RE: QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

Deepu Prashanth — Mon, 22 Jul 2024 09:18:51 GMT

Hi Maria,

last year information is regarding to shell but i want to implement temperature measurement in SWITCH and BULB Samples.

Best Regards,
Deepika B.

RE: QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

Deepu Prashanth — Mon, 22 Jul 2024 05:23:26 GMT

Hi Maria,

Sorry for the late reply !!!😒

Thank you so much for giving reply to my message!!!!

My doubt is for temperature measurement i gave simulated values for temperature and in bulb side i implemented temperature measurement. Now, i want to send these temperature values to switch by using report attribute.

I saw somewhere in document that before sending temperature values using Report attribute first need to bind request to switch and need to configure temperature reporting attribute from bulb side to switch.

Is this two functions ( bind_request and configure temperature reporting attribute) is required or not? if we implement bind req in switch side is it compulsory need to implement bind Response in BULB side?

In some where i saw that don't need to implement BIND_RESPONSE in bulb side because by using

zb_bdb_finding_binding_target this function we don't need to implement BIND_RESPONSE in bulb side is it correct or wrong?

I need Clarification on this functions and how can i report temperature value to switch?

As I am new to this, please help here get the above information.

Thanks a lot 😊!!!

Best Regards,
Deepika B

RE: QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

Maria Gilje — Thu, 18 Jul 2024 14:02:55 GMT

Hello again,

This case from last year has some information on how to add ZCL clusters to an application. It can help you to get started. You can start with the light bulb and light switch samples as the base (instead of the Zigbee template) and add the clusters fror temperature measurement. Follow the guide, but use my reply from the ticket when you see any references to "ZB_HA"-macros.

Next week I'll be able to provide more specific support. Thank you for your patience and best of luck.

Best regards,

Maria

RE: QUERY - [nRF52840][ZIGBEE] getting issue with reporting attribute while sending Temperature Measurement Value From Bulb To switch?

Maria Gilje — Wed, 17 Jul 2024 15:14:41 GMT

Hi Deepika B,

I just want to let you know that I will find some useful information and resources for you tomorrow. Thank you for your patience.

Best regards,

Maria