Zigbee HA Atrribute Reporting

RE: Zigbee HA Atrribute Reporting

bjorn-spockeli — Tue, 26 Mar 2019 14:53:20 GMT

I think that you should be able to subscribe to the attribute change without having to bind two endpoints prior to calling zcl subscribe.

RE: Zigbee HA Atrribute Reporting

longrain — Wed, 27 Feb 2019 09:50:40 GMT

Why use "bind on ",before "subscribe "? Do "subscribe" depend on "binding"?

RE: Zigbee HA Atrribute Reporting

bjorn-spockeli — Wed, 12 Dec 2018 13:50:17 GMT

Jimmy: I'm still waiting to hear back from the Zigbee developers who are in contact with the 3rd party stack developer regarding subscribing to changes for any attribute on any cluster.Will update once I hear back from them.

Bjørn

RE: Zigbee HA Atrribute Reporting

Jimmy@zone — Wed, 28 Nov 2018 11:07:54 GMT

param and test are params to the function i schedule it using ZB_GET_OUT_BUF_DELAYED2

RE: Zigbee HA Atrribute Reporting

inv4 — Wed, 28 Nov 2018 08:22:56 GMT

Hi, where are you getting param and test from?

RE: Zigbee HA Atrribute Reporting

Jimmy@zone — Thu, 22 Nov 2018 11:14:53 GMT

I am in a good mood =)

zb_buf_t* p_buf = ZB_BUF_FROM_REF(param);

zb_buf_t* tb = ZB_BUF_FROM_REF(test);
send_command__req_t* cmd = (send_command__req_t*)ZB_BUF_BEGIN(tb);

zb_zdo_bind_req_param_t* req;
req = ZB_GET_BUF_PARAM(p_buf, zb_zdo_bind_req_param_t);

    zb_address_ieee_by_short(cmd->addr, req->src_address);
    req->req_dst_addr   = cmd->addr;
    req->src_endp       = cmd->endpoint;

    zb_get_long_address(req->dst_address.addr_long);
    req->dst_addr_mode          = ZB_APS_ADDR_MODE_64_ENDP_PRESENT;
    req->dst_endp               = ZIGBEE_CLI_ENDPOINT;

req->cluster_id = cmd->cluster_id;

    zb_uint8_t tsn = zb_zdo_bind_req(ZB_REF_FROM_BUF(p_buf), bind_acked_cb);
    ZB_FREE_BUF_BY_REF(test);
    LOG("Binding %d\n", tsn );

RE: Zigbee HA Atrribute Reporting

bjorn-spockeli — Thu, 22 Nov 2018 09:58:26 GMT

I guess you should be able to do that using the ZCL API and ZDO API of the Zigbee stack.

RE: Zigbee HA Atrribute Reporting

inv4 — Thu, 22 Nov 2018 09:07:30 GMT

Is there a way to create the binding from the router to coordinator? In the example that you mention this is done via CLI but In reality it would be more like Light node to Zigbee coordinator/gateway.

RE: Zigbee HA Atrribute Reporting

bjorn-spockeli — Thu, 22 Nov 2018 08:17:00 GMT

HI inv4,

I think thats a typo and it should be zdo bind on and not zcl bind.

Best regards

Bjørn

RE: Zigbee HA Atrribute Reporting

inv4 — Thu, 22 Nov 2018 05:29:45 GMT

Hi bjorn-spockeli, can you clarify step 5? there is no sign of this command in the documentation: zcl bind or zcl_bind.

Thanks in advance!

RE: Zigbee HA Atrribute Reporting

Jimmy@zone — Wed, 21 Nov 2018 11:47:16 GMT

Thanks, A good code snippet on how to best set it up if not would still be good ;)

RE: Zigbee HA Atrribute Reporting

bjorn-spockeli — Wed, 21 Nov 2018 10:42:47 GMT

Hi Jimmy,

we need to look into if subscribing to changes for any attribute on any cluster is supported by our 3rd party Zigbee stack. Will get back to you on this.

Best regards

Bjørn

RE: Zigbee HA Atrribute Reporting

inv4 — Wed, 21 Nov 2018 00:52:02 GMT

Please don´t edit your comments because context of the subsequent comments is lost.

RE: Zigbee HA Atrribute Reporting

Jimmy@zone — Fri, 16 Nov 2018 18:06:46 GMT

preferably any attribute on any cluster. Or do I need to list all the attributes that I might be interested in ? For instance I might want to know if the wallplugg is turend off manualy using the button, if the power consumption is changed, a door lock is unlocked etc.

RE: Zigbee HA Atrribute Reporting

wbober — Fri, 16 Nov 2018 15:28:55 GMT

Could you please elaborate on " is there a way to subscribe to all attribute changes ?" Are you asking about a change of any attribute on a cluster or any change of a given attribute?

RE: Zigbee HA Atrribute Reporting

bjorn-spockeli — Fri, 16 Nov 2018 14:30:41 GMT

I've forwarded the question to the Zigbee team again so will comment once they get back to me.

Bjørn

RE: Zigbee HA Atrribute Reporting

Jimmy@zone — Fri, 16 Nov 2018 14:06:56 GMT

I was but its unstable, don't know what the problem is. Might be develco smart plug I am testing with or I have a bug =) A question I still have is the first on, is there a way to subscribe to all attribute changes ?

RE: Zigbee HA Atrribute Reporting

bjorn-spockeli — Fri, 16 Nov 2018 13:47:30 GMT

Saw you edited your comment. So you're getting the attribute reports?

Best regards

Bjørn

RE: Zigbee HA Atrribute Reporting

Jimmy@zone — Fri, 16 Nov 2018 12:59:03 GMT

Thanks

RE: Zigbee HA Atrribute Reporting

bjorn-spockeli — Thu, 15 Nov 2018 10:23:55 GMT

Found this in internal FAQ page:

Do we have a ZCL attribute reporting example

We do not have an example created specifically to demonstrate attribute reporting, although:

From server/advertiser site: for every cluster there is a set of attributes, that shall have attribute reporting implemented and available. As a result, a simple light bulb example may be used as reporting ZCL server.
From client/subscriber site: all commands required to configure reporting and logic to parse reports were added to the CLI Agent Router example.

Combination of those two gives a complete "reporting" example.

Additionally, the CLI uses a "raw" technique of intercepting ZCL reports. There is also a dedicated ZBOSS callback, that may be used to get ZCL attribute reports, but it was not used, as there might be only one reporting-callback defined.

Steps to test ZCL reporting:

Flash light bub example to one board
Flash CLI example (Zigbee CLI Agent example) to another board.
Use CLI as the coordinator:
1. bdb role zc
2. bdb start
Find the light bulb's endpoint, short and long addresses:
1. zdo match_desc 0xFFFD 0xFFFD 0x0104 1 0x0006 0
2. zdo ieee_addr <returned_short_address>
Create binding FROM the light bulb TO the CLI ON the light bulb:
1. zcl bind <bulb_long_addr> <bulb_ep_from_match_desc> <CLI_long_addr> <CLI_endpoint, defaults to 64> 0x0006 <bulb_short_addr>
Subscribe for attribute's changes:
1. zcl subscribe <bulb_long_addr> <bulb_ep_from_match_desc> 0x0006 0x0104 0x0000 16

Magic numbers:

0xFFFD - broadcast address, all devices with RxOnWhenIdle == 1
0x0104 - Home Automation profile ID
0x0006 - On/Off cluster ID
0x0000 - On/Off attribute ID

Hope this helps!

Best regards

Bjørn

RE: Zigbee HA Atrribute Reporting

inv4 — Tue, 13 Nov 2018 18:36:36 GMT

Thanks for the update bjorn-spockeli

RE: Zigbee HA Atrribute Reporting

bjorn-spockeli — Tue, 13 Nov 2018 15:00:10 GMT

Hi inv4,

I've forwarded your question to the Zigbee team and will update the case when they get back to me.

Best regards

Bjørn