This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Mesh SDK - Reasoning behind destination address handles

I am using the mesh SDK 2.1.1 and have one node that uses the serial API.      That node sends mesh packets to the network via the PacketSend serial opcode.       This command uses an indirect address via an address handle that I must 1st have to register via the AddPublicationAdd command.

In my scenario I may have to potentially have to send to packets to any address < 0x7FF as well as the group address.      What is the reason for using handles to an address?    In my use case I potentially have to add and remove address handles quite often as the buffer to store the handles is finite.

I plan on adding a new serial command to take an address directly to work around the current interface but was curious if there was another way I could directly specify the address without having to modify the stack.   I have been trying to minimize patches to the mesh stack to make upgrades to future version easier.

  • Hello,

    I understand. I will forward this to our mesh team. I guess you know that you can change some parts of the stack, but I do get your argument of making it easier to upgrade to future releases of the Mesh SDK.

    I guess that the reason that it is like this is that it is the provisioner that decides and keeps track of what addresses that are used, and which ones that are free, but I have to double check with our Mesh Team. 

    Best regards,

    Edvin

Related