Hello
I hope someone can help with my problem.
We have a small to large BT Mesh network and we want to use the URI value to send preliminary information from the node to the provisioner. This URI value contains information, that are different from node to node (ex: serial number, ...), hence just checking that the URI hash value is correct (ex: for a given URL) won't work in this case.
I know, that the unprovisionedbeacon callback contains the UUID, the OOB information and the URI hash value.
I also read in the documentation, that the URI field is optional and that this information is advertised separately from the unprovisioned beacon. Unfortunately, I have no idea how my provisioner can extract this information...
I did a test and let the node starts sending the beacon and also saw with the nRF connect mobile app the node "advertising" its beacon, however, there was no other advertise packet containing the URI value.
Does Zephyr contain a mechanism to get this URI value? I could see that the URI hash value is different from node to node, so I assume that adding that information is done correctly, but only the hash value won't be enough because the provisioner needs to know those additional information.
Any help is appreciated.
/thierry
