How to configure Nodes using a Custom Provisioner

RE: How to configure Nodes using a Custom Provisioner

Hung Bui — Wed, 13 Mar 2019 15:55:45 GMT

Hi Kilian,

I understand that sometime it seems to be overcomplicated but to be able to make the library generic enough we would need to do so.

Please be aware that provisioning and configuration are 2 different procedures. Provisioning can only be done by the provisioner directly when the configuration is just normal Mesh activity and can be performed by any node (which has configuration client) and can be relayed.

What you described is correct. You can find the list of the steps we design the provisioner to do in the light switch example in node_setup.c, please look for client_config_steps. We basically have a state machine and going through every step in the array starting with NODE_SETUP_CONFIG_COMPOSITION_GET.

RE: How to configure Nodes using a Custom Provisioner

Biliban Tierli — Wed, 13 Mar 2019 13:21:27 GMT

Hi Hung,

Yes I have tried the Provisioner example. The Problem with that is, that it is very complex and hard to understand. It uses a lot of interleaved functions and structures to do extremely simple thing (same with the light switch example...).

I have already figured out, how to provision a node. To be exact: I receive a NRF_MESH_PROV_EVT_LINK_CLOSED in my provision_evt_handler following the procedure i pointed to. My problem is that I now want to set the publication address of the just provisioned node to the unicast address of my provisioner (or any other address).

If I compare it to the example i see, that in the "provisioner_helper.c -> prov_evt_handler -> case: NRF_MESH_PROV_EVT_LINK_CLOSED -> Provisioning Successful" the function node_setup_start() from node_setup.c gets called. Somewhere in there the publication and subscription addresses must be set. After some digging around I think in the function config_step_execute(). According to that function i need to do the following:

Get the Composition Data: config_client_composition_data_get(0x00);
Add Appkey to the Node: config_client_appkey_add(NETKEY_INDEX, m_appkey_idx, mp_appkey);
Bind Appkey to the Model: config_client_model_app_bind(element_address, m_appkey_idx, model_id);
Set Publication of Model: config_client_model_publication_set(&pubstate);

Is that correct?

Cheers,

Kilian

RE: How to configure Nodes using a Custom Provisioner

Hung Bui — Wed, 13 Mar 2019 12:55:51 GMT

Hi Kilian,

Have you tried to test the Provisioner example ? You were asking for "Example of what to do with the standard API" but isn't it the provisioner example does exactly that ?

I understand that you may want to do something not exactly the same as what the provisioner doing. But I would suggest to modify the provisioner instead of copy ans paste the code into your application before you fully understand how to modify the provisioner.

If possible, could you give some more information on what you are planing to do ?

Please note that provisioning process requires much more than what you posted. What you posted is how to generate and assign the key internally on the provisioner, not about provisioning a peer device. Please refer to the provisioning procedure in the documentation that you pointed to. This is handled in prov_provisioner.c and provisioning.c

RE: How to configure Nodes using a Custom Provisioner

Biliban Tierli — Tue, 12 Mar 2019 13:23:43 GMT

Hi Hung,

thanks for your fast answer. Is there also a an Example of what to do with the standard API, instead of the PyACI?

I was already modifying the Light Switch Provisioner, but I just don't understand the whole Key Handling. I have copied this Code from the Light Switch Provisioner Example:

// Node Setup --------------------------------
mesh_key_index_t netkey_handle;
mesh_key_index_t appkey_handle;
mesh_key_index_t devkey_handle;

uint8_t netkey;
uint8_t appkey;
uint8_t self_devkey;

/* Generate keys */
rand_hw_rng_get(&netkey, NRF_MESH_KEY_SIZE);
rand_hw_rng_get(&appkey, NRF_MESH_KEY_SIZE);
rand_hw_rng_get(&self_devkey, NRF_MESH_KEY_SIZE);

/* Add default Netkey and App Key */
ERROR_CHECK(dsm_subnet_add(0, netkey, &netkey_handle));
ERROR_CHECK(dsm_appkey_add(0, netkey_handle, appkey, &appkey_handle));

/* Add device key for the own config server */
ERROR_CHECK(dsm_devkey_add(0x0001, netkey_handle, &self_devkey, &devkey_handle));

This works and doesn't give an Error. When I now try to set a publication for my Model I get a NRF_ERROR_INVALID_PARAM Error. This is the Code for that:

nrf_mesh_address_t addr = {
.type = NRF_MESH_ADDRESS_TYPE_UNICAST ,
.value = 0x0001, // Address of my Provisioner
.p_virtual_uuid = NULL
};

access_publish_period_t pub_period = {
.step_res = ACCESS_PUBLISH_STEP_RES_BITS,
.step_num = ACCESS_PUBLISH_STEP_NUM_BITS
};

config_publication_state_t pubstate = {
  .element_address = 0x00F0, // Address of my Node
  .publish_address = addr,
  .appkey_index = 0,
  .frendship_credential_flag = false,
  .publish_ttl = ACCESS_TTL_USE_DEFAULT,
  .publish_period = pub_period,
  .retransmit_count = 1,
  .retransmit_interval = 1,

.model_id = ACCESS_MODEL_VENDOR(0xFFAA, 0xF001) // Model ID and Vendor ID of my Node
};

uint32_t status = config_client_model_publication_set(&pubstate); // This Returns the Error

Do I need to add the Appkey to my Node first? and if so how? Or do you see any other mistake I could have made?

Cheers,

Kilian

RE: How to configure Nodes using a Custom Provisioner

Hung Bui — Tue, 12 Mar 2019 13:03:51 GMT

Hi Biliban,

Have you tried our provisioner inside light switch example ? Please refer to the node_setup.c where we do the configuration for the light switch client and light switch server.

You can also have a look here to get to know what a provisioner should do when doing configuration.