BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

bart — Wed, 08 May 2019 09:42:56 GMT

The link is broken

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Thu, 21 Sep 2017 01:56:52 GMT

Hello, I made a mistake and wasn't using the correct main.c. Thank you once again for your help!

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Thomas Stenersen — Wed, 20 Sep 2017 11:37:12 GMT

Please look more closely at the main.c in the light control server application :) Are you using the Simple OnOff Model? If so, the get_cb() andset_cb() should point to functions in your application that should act on a get or set command. For example set a LED or print something on UART.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Wed, 20 Sep 2017 11:26:52 GMT

@thomasstenersen

hal_led_pin_set()

That is very odd! it's not even compiled in my provisionee project!

And I couldn't find "generic_set_cb" either...

There should be code which add "hal_led_pin_set()" or "generic_set_cb" to an event queue somewhere and wait for handling, where is that code?

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Thomas Stenersen — Wed, 20 Sep 2017 11:08:46 GMT

If you're talking about the light control example, look in its main.c file, specifically in the generic_set_cb(). It's calling the hal_led_pin_set() function which in turn toggles the GPIO.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Wed, 20 Sep 2017 10:58:59 GMT

@thomasstenersen Hello again, assume the configuration and everything is successful, the provisionees should have code to turn on and off leds right? Where is that code?? I'm a bit lazy and I've tried for the past a few hours but couldn't locate that code, can you tell me where it is? I know for provsionER it's simple on and off client but I don't know where for provisionEE.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Petter Myhre — Tue, 19 Sep 2017 12:40:25 GMT

The main problem was solved in this thread.

As Thomas mentioned, if you have questions about future releases and timelines you should contact the Regional Sales Manager for your area, if you don't know who it is, send me a PM with your location and I'll let you know.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Thomas Stenersen — Tue, 19 Sep 2017 10:24:07 GMT

Good to hear it's fixed now :) For information about upcoming releases and schedules, you should contact your local sales representative. If you don't know who that is, @petter can help you find him/her.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Tue, 19 Sep 2017 10:13:19 GMT

@Petter @thomasstenersen:

This is well, quite embarrassing and unexpected: it seems that I did not restore the line mentioned above, this line in prov_utils.c:

return memcmp(confirmation, p_ctx->peer_confirmation, sizeof(confirmation)) == 0;

Now that I did, it has reached

case NRF_MESH_EVT_PROV_COMPLETE:

Sorry for all the inconveniences that I may have caused. I swear I did restore that line myself. But clearly for some reason that wasn't the case.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Tue, 19 Sep 2017 07:17:35 GMT

Ok cool, I was just saying.

Will there be a 1.x release for the ble mesh?? When? Will there also be an apple/android app? Can't wait!

You may select OOB method "None", then the provisioning process will work as if the OOB data was all zeros.

Will that help me out of this debug quagmire? Or should I wait for the new release? Does the new release support nrf52840 BTW? You don't have to answer if you are not allowed to...

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Thomas Stenersen — Tue, 19 Sep 2017 06:55:25 GMT

I'm busy providing all the new cool features for upcoming releases ;) @Petter can probably help you further. The static data is provided as Out Of Bound (OOB) data to prevent eavesdroppers "taking over" or getting the keys generated/sent during the provisioning process. You may select OOB method "None", then the provisioning process will work as if the OOB data was all zeros.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Tue, 19 Sep 2017 06:47:24 GMT

@thomasstenersen Awww... can't you just spare a little time, as a hobby? Anyway I very much did roll it back, and it is going the right place. I've also checked the auth data which they provide to each other, it's the same.

Come to think of it, do they have to provide such data to each other? Instead of one doing all the checks?

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Thomas Stenersen — Tue, 19 Sep 2017 06:12:27 GMT

Hi Mitch,
I unfortunately don't have the time to debug :(
But, did you revert back all your changes to the mesh stack? E.g., the changes in prov_utils.c?

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Mon, 18 Sep 2017 12:15:21 GMT

@petter hello again, it still runs to NRF_MESH_EVT_PROV_LINK_CLOSED, caused by a time out. I don't know why... here is the call stack tree:

https://ibb.co/i0ASTk

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Mon, 18 Sep 2017 12:03:41 GMT

@Petter update: the confirmation problem was solved, because of the auth data on both nodes are not the same, now it is the same and the problem was solved. I'm still trying to see if the program will run to "NRF_MESH_EVT_PROV_COMPLETE".

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Mon, 18 Sep 2017 05:47:25 GMT

The download link:

s000.tinyupload.com/

Also you can find the same link in the question's main body.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Mon, 18 Sep 2017 04:02:39 GMT

@petter no problem! Uploaded my project in the main question. All relative directory, should be unzip and play. But you need to install 7zip first. Also it's password protected and I've sent password to your PM.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Petter Myhre — Fri, 15 Sep 2017 11:07:04 GMT

Ok. I don't such a list. Could you share your complete project? Maybe I can figure out what is going on.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Fri, 15 Sep 2017 01:46:27 GMT

Hi @petter, I'll be honest I don't know exactly what those events mean. But could you gave me a list of most probable cause of them so I can eliminate them one by one?

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Petter Myhre — Thu, 14 Sep 2017 11:52:07 GMT

Difficult to say exactly what causes it. It seems that you get the p_ctx->peer_confirmation from the peer with the PROV_PDU_TYPE_CONFIRMATION event. And you get the p_ctx->peer_random with the PROV_PDU_TYPE_RANDOM event. Which is used in the calculation of the confirmation that is compared with p_ctx->peer_confirmation.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Thu, 14 Sep 2017 10:41:14 GMT

Ha, never mind the formalities of formats, what caused the memcmp to return a <0 result?

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Petter Myhre — Thu, 14 Sep 2017 10:37:14 GMT

I converted them to answer in the mission of fixing the formatting, but then I couldn't convert back to comment.

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Thu, 14 Sep 2017 10:32:45 GMT

Hi, my bad, I didn't see the "== 0" part.

Anyway the result is "0x000000AC", or -84.

In other words, confirmation is less than p_ctx->peer_confirmation.

What could have possibly caused this?

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Petter Myhre — Thu, 14 Sep 2017 10:16:38 GMT

I think it is correct. If equal memcmp() will return 0. 0==0 is 1. !1 is 0. Are you saying that memcmp() returns 1?

RE: BLE Mesh light control example won't go to "NRF_MESH_EVT_PROV_COMPLETE"

Mitch996 — Thu, 14 Sep 2017 10:13:57 GMT

Hello Petter, I swear I added as comment, but somehow got converted automatically as answer, I guess it has somethign to do with the character limit.

Anyway it won't happen again!