Android-nRF-Mesh-Library: How to consume/invalidate a unicast address?

RE: Android-nRF-Mesh-Library: How to consume/invalidate a unicast address?

Simonr — Thu, 28 Oct 2021 12:06:02 GMT

Update: This issue has now been fixed in our GitHub repo, and the changes have now been pushed.

RE: Android-nRF-Mesh-Library: How to consume/invalidate a unicast address?

Simonr — Mon, 02 Aug 2021 12:06:31 GMT

Hi again

The person in charge of the Android nRF Mesh library got back from vacation today and will look at this issue and handle it on GitHub this week.

Best regards,

Simon

RE: Android-nRF-Mesh-Library: How to consume/invalidate a unicast address?

BlueMike — Mon, 26 Jul 2021 09:45:21 GMT

Hello Simon,

Thanks for your help! No big deal if it takes a little longer. I've meanwhile opened an issue at the libraries github repo.

All the best,
Michael.

RE: Android-nRF-Mesh-Library: How to consume/invalidate a unicast address?

Simonr — Mon, 19 Jul 2021 12:53:54 GMT

Due to the summer vacation period we are currently understaffed, so delayed replies must be expected. I am sorry about any inconvenience this might cause. I'm currently waiting for an answer internally on this bug you have reported and it's under investigation. Thank you for your patience. I will get back to you as soon as I have more information.

Best regards,

Simon

RE: Android-nRF-Mesh-Library: How to consume/invalidate a unicast address?

BlueMike — Mon, 12 Jul 2021 10:11:50 GMT

Hi Simon,

Thanks for your help.

[quote userid="75734" url="~/f/nordic-q-a/76535/android-nrf-mesh-library-how-to-consume-invalidate-a-unicast-address/316271#316271"] it seems like you are trying to assign the unicast address twice to the same device. [/quote]

Sorry, I've oversimplified the explanation. My app first provisions a node, then connects to it and (if the connection is established) assigns and binds the app key. The unicast address is assigned only during provisioning (i.e. the first step). This is the exact same behavior as the demo app.

The problem is caused by a bug or "design flaw" in Android-nRF-Mesh-Library:

The bug here is that nextAvailableUnicastAddress() returns an already used address. It obviously shouldn't, but it's happening anyway because Android-nRF-Mesh-Library updates its internal list of nodes (BaseMeshNetwork.nodes) in response of one of the configuration commands (ConfigDefaultTtlGet, ConfigNetworkTransmitSet, ConfigAppKeyAdd, ConfigModelAppBind).
Now if the connection to the freshly provisioned node fails, non of these commands are sent, and hence the library misses the newly provisioned node, causing nextAvailableUnicastAddress() to return an already used unicast address.

The question now is how can we get this fixed asap?

RE: Android-nRF-Mesh-Library: How to consume/invalidate a unicast address?

Simonr — Mon, 21 Jun 2021 12:55:08 GMT

I spoke to one of our developers of the Android nRF Mesh library, and it seems like you are trying to assign the unicast address twice to the same device. Usually, you would assign a unicast address as well as a network key during provisioning, and then add additional network/app keys after you have connected. This is according to the Bluetooth Mesh profile spec. so I'm guessing that's what causing these errors when you try assigning a unicast address after the provisioning.

Best regards,

Simon