Reply
Posts: 4
Registered: ‎10-09-2017
Accepted Solution

Why end device is not removed from child table?

I use EmberZNet 5.6.0 and use host-NCP communication.

 

As per the link (http://community.silabs.com/t5/Mesh-Knowledge-Base/How-long-can-my-end-device-go-without-polling-its...), the end device will removed from child table if the end device doesn't poll its parent in about 5 minutes.

#define EMBER_END_DEVICE_POLL_TIMEOUT 5
#define EMBER_END_DEVICE_POLL_TIMEOUT_SHIFT 6

 

In my case, the coordinator is the parent of an end device. I unplug the battery of the end device, but after enough long time, the end device is still in the child table.

>plugin stack-diagnostics child-table
#  type    id     eui64
0: Sleepy  0xE9EB (>)000D6F000B723223

1 of 6 entries used.

Highlighted
<a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero</font></font> </a> YK
Posts: 215
Registered: ‎02-13-2017

Re: Why end device is not removed from child table?

EmberZNet is somewhat obsolete. I suggest you to use EMberZNet 5.10 to have the test again.

If my reply answers your question, please click on "Kudo"s or "Accept as Solution"s to benefit others who have the same issue.

YK Chen