Other Parts Discussed in Thread: Z-STACK
Hi,
We have been observing a issue with ZED leaving the network randomly and not rejoining back to the coordinator.
There are mutliple such ZEDs on the same network, but not all of them leave.
We experienced some power cuts and suspected that the issue could be because of that.
However, when we tried to reproduce the issue with the following scenarios :
1. Simulate power cut. ZC and all ZR on network are powered down. ZEDs stll running.
ZEDs go into a rejoin loop(configured to 40s) and rejoin to network when a nearby ZC or ZR powers up.
Tested for time gap of 24hrs b/w power down and power up
2. Simulate ZC down. ZR powered up. ZEDs still running
ZEDs are still in sleep loop(configured to 240s) and poll the nearby parent ZR regularly.
The ZR performs route discovery on pending messages.
When ZC powers up then any further messages are processed successfully.
Tested for time gap of 24hrs b/w ZC power down and power up.
In either of the case we could not reproduce the ZED resetting itself or leaving the network.
The ZC logs have no leave request.
Since the Leave is unpredictable, I cannot sniff for a leave event.
What could the possible cause for ZED leaving the network ?
Please could you outline the possible causes for a ZED to leave the network ?
Thanks
Akhilesh
<Configuration of my ZED>
Rejoin timeout -> 40 seconds
Sleep poll rate rate -> 240 seconds
Minimum time between consecutive message sends from ZED -> 200 ms
