Where can i know, in the ZC, the first entry of ZR/ZED

Babu P S

Other Parts Discussed in Thread: Z-STACK

According to the Z-Stack Developer's Guide, in section 3.2.2 where stochastic addressing is described,
It states that "When a device joins, it receives its randomly generated address from its parent".

In the ZC Code Where can i find this ?
I mean i have to get to know of the 64-bit address of the device even before a 16-bit network address is assigned.

Thanks in advance

-Babu P S

over 9 years ago

0 YiKai Chen over 9 years ago

Guru 735685 points

The short address assignment is in Z-Stack library and application cannot see it. When a device joins Zigbee network, it would broadcast end node announcement with its short and IEEE address. You can register a callBack to receive end node announcement to get both short and IEEE address of joined device.

0 Babu P S over 9 years ago in reply to YiKai Chen

Intellectual 580 points

how can i blacklist a particular ZR/ZED, that annoys by repeatedly sending announcement., whenever i open/unlock the network.
Is there a way that i can reject/blacklist the device even before assigning short address or updating the Association and binding tables.

0 YiKai Chen over 9 years ago in reply to Babu P S

Guru 735685 points

You can refer to processors.wiki.ti.com/.../Black_list_implementation

0 Babu P S over 9 years ago in reply to YiKai Chen

Intellectual 580 points

That black list implementation is based on "black listing" PAN_ID, which will help in ZED/ZR to not join the Black-listed PAN_ID.
How does that help ZC in blacklisting certain ZED/ZR ?

0 YiKai Chen over 9 years ago in reply to Babu P S

Guru 735685 points

You can ask device to leave when ZC receives end node announcement from an unwanted device.

0 Babu P S over 9 years ago in reply to YiKai Chen

Intellectual 580 points

Once ZED/ZR joins the ZC, it can deny the leave_request. As defined in the Spec
Until ZC gets the Leave_Request_Response it will not clear the Association & Binding Table.

In other words, if ZED/ZR doesn't support leave_request Command or in case of failure to process/carry out command,
that wouldn't clear the table contents, resulting in "no-room" for new devices.

0 YiKai Chen over 9 years ago in reply to Babu P S

Guru 735685 points

Yes, that's true for all Zigbee spec before R21. In latest Zigbee core spec R21, it defines CHILD_AGING to handle this. A device would be kick out of association table if it doesn't response to parent node for a while.

0 YiKai Chen over 9 years ago in reply to Babu P S

Guru 735685 points

By the way, it's mandatory for ZC/ZED/ZR to support leave_request Command according to spec.

Zigbee & Thread

Zigbee & Thread forum

Where can i know, in the ZC, the first entry of ZR/ZED