pb remote client doesn't work

[Duy]

Hello,

I used 3 nRF52-DKs to run the pb_remote and it ran well with the Mesh SDK v0.10.1. Then I created my own project and copied the code from the pb_remote client and server and put in my project. But the code didn't run well. The servers were ok but when I used the client to remote provisioning, the console displayed ERROR 4 from the nrf_mesh_sdk. Here is the error

Then I used the server code of my project and the client code from the example and it ran well. I don't know what happened to it? Is it because of the conflict between library files? By the way, can I use remote provisioning with simple_on_off_model or health_model?

Thank you so much.

[Hung Bui]

When you see an issue and you see the error code, you can check for the error code inside nrf_error.h (NRF_ERROR_NO_MEM)

Please check the function that cause the error at line 180 in main_simple_client.c

[Duy]

Thank you Hung Bui. I did check and I found that it was because of a wrong configuration. But when do you release a newer mesh sdk version?

[Hung Bui]

We are working on new release of the mesh SDK, but is there any blocking feature missing on current SDK that you are looking for in the newer one ?

[Duy]

Actually I am a student working on my Graduation Thesis on Bluetooth Mesh and I find that it is very interesting.

I tried combining the serial example with the light switch example but it didn't work, the serial doesn't jump into the rx callback. And I wonder If the client (provisioner dies), is there any function or way to discover that event? I want a random provisionee (server) to become a provisionee in that case or may be I can use a new provisionee. I am reading the document but I haven't seen any place mentioned about that. Thank you

[Hung Bui]

I'm not sure I understand what you are asking. But serial example is not related to this question, you can create a new case, with more description. Also please don't convert every comment into answer.