Adding device in nRF Mesh app: the existing one disappears

RE: Adding device in nRF Mesh app: the existing one disappears

AHaug — Thu, 24 Aug 2023 13:56:21 GMT

Noted,

I've still not excluded if this is the intended way to operate for the test-mesh sample, but in case this is a bug, can you verify the procedure for the bug report you've used to provision the devices? Based on your description this is what I assume you've done:

Build and flash two firmware versions for the DK and the Dongle. No modifications to the code has been made other than building for the different targets
Flash the DK with west/VS Code extension for NCS, and program the Dongle with the programmer found in nRF Connect for Desktop
Open the shell for device 1:
1. mesh init (if not already done)
2. mesh prov pb-gatt on to enable advertising
3. Add node in nRF Mesh app, press the device that shows up
4. Identify and provision. Device shows up on the main page with Zephyr Mesh as its name. (Unicast address is 0x0009 in my case)
Provision the first device by scanning for provisionable nodes in the nRF Mesh app
Repeat the procedure for the second device using the same parameters (automatically assigned a new unicast address, (0x0012 in my case)
Observe that the first device (even when changing names) is overwritten by the second device

Kind regards,
Andreas

RE: Adding device in nRF Mesh app: the existing one disappears

Marius Waage Aabel — Wed, 23 Aug 2023 12:34:38 GMT

Yes, it's probably some number that is not unique. So probably you can check the app code, find which number is uses as key.

- NCS 2.4.1
- Android 13
-nRF Mesh 3.3.0

Btw, this is not a big problem for me, I only use the app to provision, so the post is just to make you aware of the bug.

Marius

RE: Adding device in nRF Mesh app: the existing one disappears

AHaug — Wed, 23 Aug 2023 08:36:49 GMT

Hi,

I will look into this, in the meanwhile could you also answer the following:

Which version of NCS are you using?
Which Android OS are you running?

What I believe is happening is the devices is somehow sharing the same Node ID or something similar which causes the second provisioning to overwrite the first one, so you and I will have to investigate that before we conclude that this is the case

Kind regards,
Andreas