PB Remote + Configuration model fail

RE: PB Remote + Configuration model fail

Mttrinh — Thu, 30 Jan 2020 10:02:24 GMT

Glad I could help :)

RE: PB Remote + Configuration model fail

Duy — Thu, 30 Jan 2020 07:18:53 GMT

[quote userid="15475" url="~/f/nordic-q-a/56564/pb-remote-configuration-model-fail/231738"]Can you check the dsm to see if you have the correct devkey inside mesh_stack_provisioning_data_store() on the provisionee. You will need to compare this with the devkey you have in the NRF_MESH_PROV_EVT_COMPLETE event on the provisioner.[/quote]

=> After checking back, I found that I generated one net key but I used a different (empty) one when provisioning so I could not bind the key.

It finally works. Thank you for supporting me.

Best regards,

Duy

RE: PB Remote + Configuration model fail

Mttrinh — Wed, 29 Jan 2020 15:56:29 GMT

Hi,

Can you check the dsm to see if you have the correct devkey inside mesh_stack_provisioning_data_store() on the provisionee. You will need to compare this with the devkey you have in the NRF_MESH_PROV_EVT_COMPLETE event on the provisioner.

The appkey/devkey is used to decrypt incoming messages and is located inside this function, upper_trs_packet_decrypt() in transport.c before getting to access layer. You can try and see if a packet(without correct devkey) ends up in that function or not.

RE: PB Remote + Configuration model fail

Duy — Sat, 25 Jan 2020 23:21:02 GMT

Hello Mttrinh,

Thanks for your feedback, I already implemented a configuration clien on the PB Remote provisioner, however the PB Remote provisionee did not receive any signal (opcode) to bind app key + net key. On the PB Remote provisioner side it said that the binding process completed successfully.

Can you give me any advices on this? The code is already in the beginning of this thread. I think I got the wrong configuration somewhere in the code.

Best regards,

Duy

RE: PB Remote + Configuration model fail

Mttrinh — Fri, 24 Jan 2020 16:19:11 GMT

Hi,

The configuration phase doesn't need PB Remote, it can be done as a normal mesh packet. A suggestion from one of my colleauge is that you can implement a configuration client on the PB Remote provisioner, and send it as a normal mesh packet.

RE: PB Remote + Configuration model fail

Mttrinh — Wed, 22 Jan 2020 15:29:19 GMT

Hi,

Its more clear what you are trying to do. I will have a closer look at the issue and see if I can figure out what is going wrong.

RE: PB Remote + Configuration model fail

Duy — Wed, 22 Jan 2020 11:18:38 GMT

Hello Mttrinh,

Do you need any further information? Thanks.

Best regards,

Duy

RE: PB Remote + Configuration model fail

Duy — Fri, 17 Jan 2020 12:54:45 GMT

Hello Mttrinh,

Thank you for your feedback. Sorry not making it clear enough and please correct me if I am wrong.

What I am doing now is to configure the provisionees as the light switch clients or light switch servers, and I have been adding these features in the PB Remote examples.

The provisioning process works fine for provisioner and provisionees. However, for the node setup (configuration) process, I have not made it work yet. The Provisioner in the Light Switch examples can configure the using functions in the node_setup.c file and this file call functions in config_client.c.

I use the same node_setup.c to put into the PB Provisioner with some small modifications to make it run, however I think I may have misused or misuderstood something so the Provisionee does not received the request to add the appkey although I do call it in function prov_evt_handler.

            /* Bind the device key to the configuration server and set the new node as the active server. */
            ERROR_CHECK(config_client_server_bind(m_devkey_handles[1 + m_next_unprov_index]));
            ERROR_CHECK(config_client_server_set(m_devkey_handles[1 + m_next_unprov_index],
                                                 m_device_address_handles[m_next_unprov_index]));

I hope that this is clear enough for you.

Best regards,

Duy

RE: PB Remote + Configuration model fail

Mttrinh — Fri, 17 Jan 2020 09:29:26 GMT

Hi,

I think you might misunderstanding something. Not sure why you need to combine the two examples in device 1, The PB remote client example already contains Remote provisioning client model that acts as provisioner and provisions remote devices. While the PB remote server example acts as provisionees until they are included in the network, after which they will be able to act as servers that are relays to help provision new devices that are out of reach for the client.

Could you give me a bit more details on why you are trying to combine the two examples in device 1 and device 2?

What are your use-case/trying to do? Have you read through this?