NRF MESH provisioner node - appKey error

RE: NRF MESH provisioner node - appKey error

loulou1844 — Fri, 26 Jun 2020 16:52:00 GMT

I get it now and it seems obvious. Correct me if I am wrong, it is because the address has been used before that it can't add the key.

It was 100% my fault, but a little error saying "this address has been used before" might have helped. ;-)

Thank you for what you did. You have been great.

RE: NRF MESH provisioner node - appKey error

Hung Bui — Wed, 24 Jun 2020 08:30:50 GMT

So we do *2 or *3 instead of *1 as in the original code because on each of our server we have 2 elements, instead of 1 element as in the original example, hence *2. But when we do *2 we still end up each of the server primary element will be all odd address (0x0201, 0x0203...), if we want odd and even (and so on) we do *3 so we have 0x0201, 0x0204, 0x0207 and so on. Having both odd and even primary address will allow us to receive the command from both button 1 and button 2 on the client.
But if you have your own way of configuring the subscription address, that doesn't really matter.

RE: NRF MESH provisioner node - appKey error

loulou1844 — Tue, 23 Jun 2020 14:04:15 GMT

Thank you for the update. I will try it.

I am not sure to understand why we should add *2 or *3.

I have identified the subscription part, I think I can manage it.

RE: NRF MESH provisioner node - appKey error

Hung Bui — Tue, 23 Jun 2020 13:17:24 GMT

Just an update:
If you do:

target_address = ONOFF_SERVER_INITIAL_ADDRESS + m_provisioner.p_nw_data->onoff_server_counter*2

The configuration would work, but you may notice that both of the server on 2 elements on the same node will subscribe to same group address (most likely the odd one)
And when you configure the next node, if the primary address is odd, both of the elements will subscribe to the odd address again.
So either you modify the node_setup.c to configure the subscription address to use the element address instead of address or you change the code to:

target_address = ONOFF_SERVER_INITIAL_ADDRESS + m_provisioner.p_nw_data->onoff_server_counter*3

Then you will have odd and even servers. But both elements on same node will still subscribe to same address.

RE: NRF MESH provisioner node - appKey error

Hung Bui — Mon, 22 Jun 2020 16:02:50 GMT

Hi Loulou,

I think we found where the issue is. In next_target_address_get(), if you have 2 elements in the server you need to change the code from

target_address = ONOFF_SERVER_INITIAL_ADDRESS + m_provisioner.p_nw_data->onoff_server_counter

target_address = ONOFF_SERVER_INITIAL_ADDRESS + m_provisioner.p_nw_data->onoff_server_counter*2

diff --git a/examples/provisioner/src/provisioner_helper.c b/examples/provisioner/src/provisioner_helper.c
index 2caf61b97..0a118dca5 100644
--- a/examples/provisioner/src/provisioner_helper.c
+++ b/examples/provisioner/src/provisioner_helper.c
@@ -86,7 +86,7 @@ static uint16_t next_target_address_get(void)
     }
     else if (strcmp(EX_URI_LS_SERVER, m_provisioner.p_nw_data->current_uri) == 0)
     {
-        target_address = ONOFF_SERVER_INITIAL_ADDRESS + m_provisioner.p_nw_data->onoff_server_counter;
+        target_address = ONOFF_SERVER_INITIAL_ADDRESS + m_provisioner.p_nw_data->onoff_server_counter * 2;
         m_provisioner.p_nw_data->onoff_server_counter++;
     }
     else if (strcmp(EX_URI_LL_SERVER, m_provisioner.p_nw_data->current_uri) == 0)

RE: NRF MESH provisioner node - appKey error

loulou1844 — Mon, 15 Jun 2020 12:36:50 GMT

Thank you for your time. I look forward to your reply.

RE: NRF MESH provisioner node - appKey error

Hung Bui — Mon, 15 Jun 2020 12:22:01 GMT

Hi Loulou,
Now when I test with 2 servers (2 elements each) I could see the issue on the 2nd server. I have forwarded this to the Mesh team for investigation. Will get back to you when we find the bug.

RE: NRF MESH provisioner node - appKey error

loulou1844 — Mon, 15 Jun 2020 09:49:38 GMT

Hi,

I downloaded again the both sdk and added 1 element on the server boards. I'm facing the same error.

devzone.nordicsemi.com/.../Terminal_5F00_provisioner_5F00_view_5F00_new_5F00_sdk.txt

I can't believe this is working for the first time for you. I can't see my mistake.

RE: NRF MESH provisioner node - appKey error

Hung Bui — Fri, 12 Jun 2020 14:51:41 GMT

Yes, please debug deeper and find why it crashes/stop continuing. Testing on a fresh copy of the SDK could be a good idea.

RE: NRF MESH provisioner node - appKey error

loulou1844 — Fri, 12 Jun 2020 14:03:05 GMT

Hi,

[quote userid="2121" url="~/f/nordic-q-a/62447/nrf-mesh-provisioner-node---appkey-error/254757"]I tried your code here but I didn't see the crash. I assume you saw the provisioner crashed ?[/quote]

Yes, on my side it crashes during the second configuration.

I did something similare with the senario file but it seems like the previous random bug.

#define CONFIG_SCENARIO_LIGHT_SWITCH_SERVER_EXAMPLE    \
    CONFIG_SCENARIO_COMMON,                            \
    CONFIG_ONOFF_SERVER,                               \
    NODE_SETUP_GET_NEXT_ELEMENT,                         \
    CONFIG_ONOFF_SERVER,                               \
    NODE_SETUP_DONE

If you say that you can't see the crash, I will try to reset my setup.

RE: NRF MESH provisioner node - appKey error

Hung Bui — Fri, 12 Jun 2020 13:34:03 GMT

Hi LouLou,

I tried your code here but I didn't see the crash. I assume you saw the provisioner crashed ?
However, I had a look at the provisioner and it seems that the provisioner was not designed to provision the 2nd element of the server.

If you look at the config_scenarios.h you can find how it's defined. For example the light switch client will be configured as follow:

#define CONFIG_SCENARIO_LIGHT_SWITCH_CLIENT_EXAMPLE    \
    CONFIG_SCENARIO_COMMON,                            \
    CONFIG_ONOFF_CLIENT,                               \
    CONFIG_ONOFF_CLIENT,                               \
    NODE_SETUP_DONE

You can find that there are 2 CONFIG_ONOFF_CLIENT being configured. And on top of each CONFIG_ONOFF_CLIENT there is a NODE_SETUP_GET_NEXT_ELEMENT . The reason for this is that the config_onoff_client is not located on the first element but located on the 2nd and 3rd element.

It's a little bit different in your 2 elements server case. Your first server model is located on the 1st element with other model for example the Health model.

So what I did to modify the configuration scenario is to add CONFIG_ONOFF_SERVER2 as follow:

#define CONFIG_SCENARIO_LIGHT_SWITCH_SERVER_EXAMPLE    \
    CONFIG_SCENARIO_COMMON,                            \
    CONFIG_ONOFF_SERVER,                               \
    CONFIG_ONOFF_SERVER2,                               \
    NODE_SETUP_DONE

#define CONFIG_ONOFF_SERVER2                      \
    NODE_SETUP_GET_NEXT_ELEMENT,                 \
    NODE_SETUP_CONFIG_APPKEY_BIND_ONOFF_SERVER,  \
    NODE_SETUP_CONFIG_PUBLICATION_ONOFF_SERVER,  \
    NODE_SETUP_CONFIG_SUBSCRIPTION_ONOFF_SERVER

Attached is the config_scenatios.h I used. Note that I haven't modified the subscription address for the 2nd server, so it subscribe to the same group as the 1st server.

devzone.nordicsemi.com/.../config_5F00_scenarios.h

RE: NRF MESH provisioner node - appKey error

loulou1844 — Thu, 11 Jun 2020 16:17:01 GMT

Thank you for your quick responses.

I had time to retry your question : "If you configure 2 servers each with 2 elements would it work ?" I have attached the full terminal with one succes and one failure. I tried around 10 times and it had succed 3, it seems random.

devzone.nordicsemi.com/.../Terminal_5F00_provisioner_5F00_view_5F00_provisioning_5F00_2_5F00_x_5F00_2_5F00_elements_5F00_nodes.txt

My modifications of the server are inspired by this. However, I have attached my modified files.

Any modification on the provisioner exemple.

**\nrf5_SDK_for_Mesh_v4.1.0_src\examples\light_switch\client\src\main.c

devzone.nordicsemi.com/.../715441.main.c

**\nrf5_SDK_for_Mesh_v4.1.0_src\examples\light_switch\server\include\nrf_mesh_config_app.hdevzone.nordicsemi.com/.../nrf_5F00_mesh_5F00_config_5F00_app.h

I hope you can reproduce the issue.

(using 3 x nrf52840-DK / Mesh v4.1.0 / SDK v16.0.0)

RE: NRF MESH provisioner node - appKey error

Hung Bui — Thu, 11 Jun 2020 14:53:00 GMT

Could you provide us the server code so we can reproduce the issue here ?

RE: NRF MESH provisioner node - appKey error

loulou1844 — Thu, 11 Jun 2020 13:57:25 GMT

Hi,

This function returns 0 in any case. (bug and not)

No problem with the client, its configuration is a success every time.

I can understand that senario are quite rigid but an unconfigured element should not cause probleme.

[quote userid="2121" url="~/f/nordic-q-a/62447/nrf-mesh-provisioner-node---appkey-error/254494"]If you configure 2 servers each with 2 elements would it work ? [/quote]

It depends, sometimes yes, sometimes no. It's very difficult to study this kind of random bug. That's why I found a case where it crashes every time: configuring a node with 2 elements and then a node with 1 element.

Thanks

RE: NRF MESH provisioner node - appKey error

Hung Bui — Thu, 11 Jun 2020 12:49:30 GMT

Hi Loulou,

Could you debug and check what's the value of the return code when config_client_appkey_add() called in the provisioner ?

What's the output of the log on the client ? has it receive the app_key adding packet ?

The node_setup.c is designed with some specific scenario so it might not work out of the box when you add more element into the server. The node_setup.c might need to be modified, I'm not sure.
If you configure 2 servers each with 2 elements would it work ?