a couple of questions about the mesh pb_remote mesh example

RE: a couple of questions about the mesh pb_remote mesh example

FormerMember — Mon, 18 Jun 2018 12:55:19 GMT

To implement simple on/off model from scratch, I would recommend you to base your application on the light switch example, and then modify/add what is needed.

This thread shows what is needed in the provisioner to add custom group.

RE: a couple of questions about the mesh pb_remote mesh example

Rcmesh — Sun, 17 Jun 2018 10:35:01 GMT

Okay, I have taken a look at the Simple on/off model, but I have some doubts on how to implement something from scratch (something simple to start, like just a client and a server comunicating). I know the light switch example uses this model, so I guess I could use it. Anyway, what would be the steps to build my own project that includes this model, if that is possible?

Thanks.

RE: a couple of questions about the mesh pb_remote mesh example

Rcmesh — Tue, 12 Jun 2018 15:40:19 GMT

Thanks for the response, I will take a look at the Simple on/off model.

Regarding the packet sniffing, I already use nrF Sniffer v. 2.0 (with Wireshark). My question was more oriented towards if it is possible at all to "disable" data encryption, because I see the sniffed packets have the data encrypted and I would like to see their content.

Thank you again!

RE: a couple of questions about the mesh pb_remote mesh example

FormerMember — Tue, 12 Jun 2018 08:39:05 GMT

If you want "bi-directional" communication, you can use the SET (or GET functions), see Simple on/off model in the documentation.

For sniffing mesh packets, the nRF Sniffer v. 2.0 has to be used.

Note: I would recommend you to switch to nRF52 instead of using nRF51, because the from nRF5 SDK for Mesh v.2.0.0, support for nRF51 is deprecated.