https://devzone.nordicsemi.com/f/nordic-q-a/38793/mesh-sdk---reasoning-behind-destination-address-handlesI 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 theen-USTelligent Community 13Mon, 24 Sep 2018 12:19:05 GMThttps://devzone.nordicsemi.com/thread/150047?ContentTypeID=1Mon, 24 Sep 2018 12:19:05 GMT137ad170-7792-4731-bb38-c0d22fbe4515:091befb8-19c3-40fa-94f8-ef4c0b738eb4Edvin<p>Hello,</p> <p>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.</p> <p>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.&nbsp;</p> <p></p> <p>Best regards,</p> <p>Edvin</p><div style="clear:both;"></div>