Unicast Address not accepting beyond 0x0FFF

[hiteshk014]

Hi,

We're using nRF Connect SDK V1.9.1 & nRF Mesh app

During provisioning when we provide Unicast address up 0x0FFF while provisioning it accepts upto 0x0FFF, but when we provision after mentioning 0x1FFF it provides a error message of "Address assigned to node is outside of provisioner's allocated unicast range", 

Actual unicast address range is 0x0001 to 0x7FFF.

Please find attached screenshots with the mentioned error message

Mentioned range:

Kindly help us with this issue for the mentioned acceptable range

Thank you,

Regards,

Hitesh

[tesc]

Hi,

Thank you for the detailed description and screenshots.

The error message is wrong, for two reasons:

1. The unicast address range in Bluetooth mesh is 1 through 0x1FFF, but the error message claims 0x1FFFF which is one F too many.
2. The full unicast address range is not necessarily assigned to the peripheral, since multiple peripherals can divide the address range between them.

By default in the nRF Mesh app, the first provisioner gets a range of around a quarter or so of the address range. The exact value may differ between the Android and iOS version. On Android the first provisioner is assigned 0x1 through 0x199A. For iOS I am not sure what the exact range is. In the app, go to Settings -> Provisioners -> select the provisioner -> Unicast addresses -> select the range, to change it.

I have reported to our mobile apps team, that they must correct the error message.

Regards,
Terje

[hiteshk014]

Hi Tesc,

As you can see in the attached screenshot unicast address value is 0x1FFF, we've not added extra F, still we are getting the error of "Address assigned to node is outside of provisioner's allocated unicast range", 

we would like to understand more in detail about unicast address which we provide during provisioning, Is it like if Device-1 is having unicast address as 0x2 and while provisioning Device-2 we can't set 0x1FFF as unicast address as the difference between these 2 address is more ?

Thank you,

Regards,

Hitesh

[hiteshk014]

I Just checked in nRF Mesh App source code, It is having a condition of High_address which is in limit of 6554 (0x199A) can you please suggest why this cap is in place when we have a range of 0 to 0x7FFF

For better reference I'm attaching screenshot:

Thank you,

Regards,

Hitesh
 

[tesc]

Hi,

We seem to have a misunderstanding. What I meant is, the error message contains an error. The error message states 0x1FFFF, not you. I was referring to the red text in one of your screenshots, which is an error message which comes from the nRF Mesh app itself.

As I wrote in my previous answer, you should be able to configure a larger range for your provisioner. By default the provisioner can only assign addresses from a limited range, but this range can be extended.

You need to go back, to the "main" page of the nRF Mesh app, then go to the Settings tab, then Provisioners -> select the provisioner -> Unicast addresses -> select the range -> change it.

Unfortunately I do not have an iOS device here, so the above is based off of nRF Mesh for Android. It should however be very similar for iOS. If you are unable to navigate to the correct setting, let me know and I will get a colleague to check the exact details for iOS.

The important takeaways are:

• We agree that the error message is not clear enough, as well as it is inaccurate, and we will fix this.
• Your provisioner can only assign addresses from a small range, but this is configurable.

Regards,
Terje

[tesc]

Hi,

The cap of 0x199A is the default range for how many addresses one provisioner gets to assign. For networks with more than one provisioner, each provisioner gets one range of this size. This way, two provisioners will not assign the same address to two different nodes. There is a setting in the nRF Mesh app, for the network, what address ranges each provisioner control. This is configurable, see the instructions in my other answers.

Regards,
Terje