Assigning unicast address as 1 while provisioning

[Anaya]

Hello,

I am using android nrf mesh app as a base app and using the latest nrf mesh library version.

I am taking provisioning trails on inline on-off controller.

While provisioning, I am facing a random issue of assigning unicast address as 1 which is same as provisioner address.

When I debug the application I found that the method network.nextAvailableUnicastAddress() which is called in ProvisioningActivity returning 1 which is further assigned to node and provisioning processed further, but stuck into getting composition data.

Can you suggest some solution to this issue?

[Joakim Jakobsen]

Are you trying to assign the same unicast address to a node, that the provisioner already posess? The unicast address is unique and should not be the same as an existing node in the network.

Br,
Joakim

[Anaya]

hello,

I don't want to assign the same unicast address to a node, that the provisioner already posess, but the method in library network.nextAvailableUnicastAddress() is returning the same address.

I could not find the reason, why this method is working uexpectedly?

Can you tell me the reason and suggest the corrective actions?

[Joakim Jakobsen]

Talking to our mobile developers we can't seem to pinpoint the exact problem.

Can you provide some steps to be able to reproduce the issue?

Br,
Joakim

[DevHachi]

Hello,

I had a similar problem. That seem to happen when you forget to call ConfigComposionDataGet.
So after provisioning is complete you should send this mentioned message to the device. After that the provisionedMeshNode does have the needed elements information and everything works as expected. Hope this will help.

Best Regards