Some questions about how to start the firmware's identification callback of an unprovisioned mesh devices.

RE: Some questions about how to start the firmware's identification callback of an unprovisioned mesh devices.

BlueMike — Mon, 11 Jan 2021 19:02:10 GMT

Never mind, I'll remove the identification feature from the app. It's just way too slow to be useful.

Thanks anyway.

RE: Some questions about how to start the firmware's identification callback of an unprovisioned mesh devices.

Joakim Jakobsen — Thu, 03 Dec 2020 11:29:17 GMT

Thanks for the additional information.

I haven't gotten any response yet, but I'll update you as soon as I do.

Br,
Joakim

RE: Some questions about how to start the firmware's identification callback of an unprovisioned mesh devices.

BlueMike — Thu, 26 Nov 2020 20:11:37 GMT

Hi Joakim,

Thanks for your help in that matter.

Here are little more details:

Device identification is basically working. The problem is that it takes way too long to execute (even after removing the one second delay that's passed to handler.postDelayed() in the nRF Mesh example).

To speed the identification process up, I've tried to start device identification without prior connecting. But this doesn't seem to work - the firmware's identification start callback doesn't get called.
Hence the question if device identification is even supposed to work without prior connecting.

Any clarifications are welcome,
Thank you.

RE: Some questions about how to start the firmware's identification callback of an unprovisioned mesh devices.

Joakim Jakobsen — Thu, 26 Nov 2020 11:15:49 GMT

Hi.

I don't have much experience with Android development, so I'll forward this to our mobile developers and ask if they have some suggestions for you.

Br,
Joakim