[BitCloud] Bindings on end-device

1 post / 0 new
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

when creating binding(s) from a end-device (light switch) to some routers (lights) it seems that the creation of the bindings alone is not enough to do establish a reliable communication link.

i often run into the APS_NO_SHORT_ADDRESS trap on the end-device , so my question is - is there any stack support to to automatically resolve the short address of a binding for which only the ieee address is known? or must the application take care of all bindings and zdp check for valid nwk addresses from time to time?

the documentation states

After binding has been established, the application can start sending data to the destination device.
I think this is only the half truth, since without a valid nwk address nothing will be send and also if the target device rejoins for some reason the binding is broken because the nwk address changed.

on routers i had much less trouble with this stuff (i guess this is only because the devices where all "hear-range" and it might get clumsy in a multi-hop environment.

as alternative to unicast bindings i tried group bindings, which works but seems to be quite slow compared to the unicast send (the time from the request to confirm is around ~ 1 second)

Last Edited: Fri. Oct 16, 2015 - 02:27 PM