Assigning unicast address as 1 while provisioning

RE: Assigning unicast address as 1 while provisioning

DevHachi — Wed, 16 Jun 2021 13:04:54 GMT

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

RE: Assigning unicast address as 1 while provisioning

Joakim Jakobsen — Fri, 22 Jan 2021 11:35:20 GMT

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

RE: Assigning unicast address as 1 while provisioning

Anaya — Tue, 19 Jan 2021 05:27:19 GMT

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?

RE: Assigning unicast address as 1 while provisioning

Joakim Jakobsen — Sun, 17 Jan 2021 21:21:42 GMT

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