This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

zigbee binary_input sensor unable to notify reportable attribute

hi,

we are trying to add third sensor to the multi sensor example , new sensor is of type binary_input  (0x000F) ZB_ZCL_CLUSTER_ID_BINARY_INPUT.

We are unable to subscribe to notification for the newly added binary_input sensor. other temp/press sensor can be subscribed   

We can also read the binary_input sensor value directly from the CLI_AGENT .

are we missing any thing in this very simple project. 

Renamed the project as simple sensor , finally have a only simple sensor as a  binary_input and a analog_input  at later stage of the project . 

SDK :  nRF5 SDK for Thread and Zigbee 4.1.0 Software Development Kit ,  SoftDevice S140

H/W: nRF52840_DK (PCA10056).

SEGGER Embedded Studio for ARM Release 5.10  Build 2020080502.43073 Windows x64

Zigbee Server/coordinator/gateway :  cli_agent_router  (PCA10059).

attached is the  complete project folder files used to build the project 

8345.my_simple_sensor.zip

3630.zb_zcl_binary_input_addons.h

the serial command and response using cli_agent

[RX] - version
CLI: Oct 15 2020 23:40:44
ZBOSS: 3.3.0.4
Done
>
[TX] - bdb channel 16
[RX] - bdb channel 16
Done
>
[TX] - bdb nwkkey 1122334455667788
[RX] - bdb nwkkey 1122334455667788
Done
>
[TX] - bdb panid 0xAABB
[RX] - bdb panid 0xAABB
Done
>
[TX] - bdb role zc
[RX] - bdb role zc
Coordinator set
Done
>
[TX] - bdb start

[RX] - bdb start
Started coordinator
Done
>
[TX] - bdb legacy enable
[RX] - bdb legacy enable
[TX] - zdo match_desc 0xffff 0xffff 0x104 1 0 0
[RX] - zdo match_desc 0xffff 0xffff 0x104 1 0 0
Sending broadcast request.
>
src_addr=213B ep=10
>Done

[TX] - zdo simple_desc_req 0x213B 10
[RX] - zdo simple_desc_req 0x213B 10
>
src_addr=0x213B ep=10 profile_id=0x0104 app_dev_id=0x302 app_dev_ver=0x0 in_clusters=0x0000,0x0003,0x0402,0x0403,0x000F out_clusters=0x0003
Done
[TX] - zdo ieee_addr 0x213B
[RX] - zdo ieee_addr 0x213B
> f4ce36ec7343be67
Done
[TX] - zdo bind on f4ce36ec7343be67 10 f4ce3665b527c4ca 64 0x0402 0x213B
[RX] - zdo bind on f4ce36ec7343be67 10 f4ce3665b527c4ca 64 0x0402 0x213B
>
Done
[TX] - zdo bind on f4ce36ec7343be67 10 f4ce3665b527c4ca 64 0x0403 0x213B
[RX] - zdo bind on f4ce36ec7343be67 10 f4ce3665b527c4ca 64 0x0403 0x213B
>
Done
[TX] - zdo bind on f4ce36ec7343be67 10 f4ce3665b527c4ca 64 0x000F 0x213B
[RX] - zdo bind on f4ce36ec7343be67 10 f4ce3665b527c4ca 64 0x000F 0x213B
>
Done
[TX] - zcl subscribe on f4ce36ec7343be67 10 0x0402 0x0104 0 41
[RX] - zcl subscribe on f4ce36ec7343be67 10 0x0402 0x0104 0 41
> Done
[TX] - zcl subscribe on f4ce36ec7343be67 10 0x0403 0x0104 0 41
[RX] - zcl subscribe on f4ce36ec7343be67 10 0x0403 0x0104 0 41
> Done
[TX] - zcl subscribe on f4ce36ec7343be67 10 0x000F 0x0104 55 10
[RX] - zcl subscribe on f4ce36ec7343be67 10 0x000F 0x0104 55 10
>
Error: Unable to configure attribute 55 reporting. Status: 141
Error: One or more attributes reporting were not configured successfully

----------READ THE ATTRIBUTES ----
>
[TX] - zcl attr read f4ce36ec7343be67 10 0x000F 0x104 55
[RX] - zcl attr read f4ce36ec7343be67 10 0x000F 0x104 55
>
ID: 85 Type: 10 Value: False
Done
[TX] - zcl attr read f4ce36ec7343be67 10 0x000F 0x104 55
[RX] - zcl attr read f4ce36ec7343be67 10 0x000F 0x104 55
>
ID: 85 Type: 10 Value: True
Done

-------------------------------------------------------------------------------

Thanks and regards 

Parents
  • Hi,

    I'm looking into your issue. I don't know what might cause the problem, as I can't see anything wrong with the implementation yet. I'll try to reproduce the issue on my side and see what I can figure out. In order to do so, it would help to know where you have created your project folder with regards to the SDK folders, to minimize linker errors when building, as well as any other changes you might have done in the SDK, and where the SDKs are located with regards to each other (the nRF5 SDK and the nRF5 SDK for T&Z).

    Best regards,

    Marte

Reply
  • Hi,

    I'm looking into your issue. I don't know what might cause the problem, as I can't see anything wrong with the implementation yet. I'll try to reproduce the issue on my side and see what I can figure out. In order to do so, it would help to know where you have created your project folder with regards to the SDK folders, to minimize linker errors when building, as well as any other changes you might have done in the SDK, and where the SDKs are located with regards to each other (the nRF5 SDK and the nRF5 SDK for T&Z).

    Best regards,

    Marte

Children
Related