Reply
Posts: 26
Registered: ‎02-13-2014

EMBER_NETWORK_DOWN

Hi All,

 

Just curious, why on a sleepy end-node, right when the device awakes after 10 minutes would it right away report EMBER_NETWORK_DOWN?

 

 

#define EMBER_AF_PLUGIN_END_DEVICE_SUPPORT
#define EMBER_AF_PLUGIN_END_DEVICE_SUPPORT_SHORT_POLL_INTERVAL_SECONDS 1

#define EMBER_AF_PLUGIN_END_DEVICE_SUPPORT_LONG_POLL_INTERVAL_SECONDS 4800
#define EMBER_AF_PLUGIN_END_DEVICE_SUPPORT_WAKE_TIMEOUT_SECONDS 2
#define EMBER_AF_PLUGIN_END_DEVICE_SUPPORT_WAKE_TIMEOUT_BITMASK 0x00000018
#define EMBER_AF_PLUGIN_END_DEVICE_SUPPORT_MAX_MISSED_POLLS 50

#define EMBER_AF_REJOIN_ATTEMPTS_MAX NEVER_STOP_ATTEMPTING_REJOIN

#define EMBER_END_DEVICE_POLL_TIMEOUT 30

#define EMBER_END_DEVICE_POLL_TIMEOUT_SHIFT 14

 

wakeup 606039 ms
Next poll nwk 0 in 256 ms
EMBER_NETWORK_DOWN 145
EMBER_NETWORK_UP
Processing message: len=12 profile=0000 cluster=0013
poll nwk 0: got data
Next poll nwk 0 in 256 ms

Posts: 5
Registered: ‎09-04-2015

Re: EMBER_NETWORK_DOWN

Are you 100% sure that the end point on the end device is configured as a sleepy end device and not RxOn by mistake? I have seen this problem when an rxon device is being made orphaned after about 8 minutes of inactivity.

 

(just a thought anyway)

Posts: 144
Registered: ‎11-06-2014

Re: EMBER_NETWORK_DOWN

Hi jlabute,

 

I'm guessing that its parent has aged it out of its child table after 10 minutes, so when it wakes up and polls, it's told to leave and rejoin. If you look at the packet trace you may be able to check if that's the case or not. BTW what is your end device poll timeout?

 

Best regards,

Yuping Xiao

Posts: 144
Registered: ‎11-06-2014

Re: EMBER_NETWORK_DOWN

[ Edited ]

Hi jlabute,

 

Ok, I just saw that you already mentioned your timeout value defines. Are those defined on the parent side?

 

 

Best regards,

Yuping

Posts: 26
Registered: ‎02-13-2014

Re: EMBER_NETWORK_DOWN

Hi Yuxiao,

 

The parent is 'sometimes' the co-ordinator, which doesn't seem to cause an issue. Sometimes the parent is a router and I've seen this issue when the parent is our router. I just added:

 

#define EMBER_END_DEVICE_POLL_TIMEOUT 30

#define EMBER_END_DEVICE_POLL_TIMEOUT_SHIFT 14

 

to the router code and I am testing it. Of course, routers could potentially be from many different vendors. Could this be an on-going issue depending whose routers we integrate with??