• State Verified Answer
  • Replies 4 replies
  • Subscribers 75 subscribers
  • Views 1333 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 219904
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE Mesh provision and configuration by a codeword

Patrick_

Hello Nordic community,

is it possible to configure the network key, application key, node address with the help of a byte array? The keys, adresses and all the peripheral configuration shall be included in this array. I have tried some lines of code which were based on the light switch server example but I was not successful. Are there any examles regarding this issue? Can you please give me some hints which function calls are responsible for the provisioning process? I am currently using the Mesh SDK 2.2.0

Patrick

  • 0

    Hi Patrick, 

    What exactly do you want to do ? Could you describe what would be the workflow you want to do provisioning + configuration ? 

    Bluetooth Mesh is an open standard, you would need to follow what describe in the spec in order to pass the qualification and to allow interoperability.

    Of course you can define your own "hard-coded provisioning" but then your device would be out to the market as "preprovisioned" 

    If you want to know more about the provisioning please have a look at the light switch\ provisioning example and the documentation here. 

  • 0 in reply to Hung Bui

    Hi, I would like to implemant the possibility to configure the node via NFC. So I can perform the provisioning process via provisioner node and NFC data. So the node should do self provisioniing in case of a valid incoming NFC configuration command + configuration parameters. In addition I would like to configure also the peripheral which is attached to the nRF microcontroller via NFC data string.

  • +1 in reply to Patrick_

    Thanks, now it makes sense. 

    It's a good idea to send data via NFC as an alternative to the standard provisioning process. I assume you aware that this is proprietary and won't support by other vendors. In addition, if you want to change configuration or do key refresh, you still need to do it the traditional way. You may need to have a way to avoid the risk that the attacker can also use NFC to get the bait device provisioned and get the network key , appkey transferred. 

    To do this you would need to write your own code to read data from NFC and write to flash the provisioning data. 

    I would suggest to have a look at how the provisioning data being stored in our example and follow that (mesh_stack_provisioning_data_store () ) 

Related
Terms of service