How can I identify the corresponding provisioned device on firmware upgrade?

[Sa.Ga.]

Hello.

I am developing an application based on IOS-nRF-Mesh-Library,
and currently considering porting firmware upgrade function of IOS-nRF-Connect-Device-Manager for updating nRF5340 device.

I want to update the provisioned devices in the application,
but I cannot find information to identify which provisioned device corresponds to the scanned device.

How can I identify the corresponding provisioned device?
Or is my understanding of porting IOS-nRF-Connect-Device-Manager incorrect?

Best regards.

[Edvin]

So you have updated the firmware of the device via Mesh or BLE, and you want to know which device it is after this update? Is that the correct assumption?

And you know what device it is in the nRF Mesh app, but when you open it in Device Manager, there are a bunch of devices with the same name?

Or did I misinterpret the question?

Best regards,

Edvin

[Sa.Ga.]

Thank you for your response.

Your understanding is close to my question.
I want to know which provisioned device in Mesh application managed corresponds scaned device in Device Manager "before" updating.

I cannot find a unique identifier that can be used in both the Mesh application and Device Manager.

Best regards,

[Edvin]

I understand. Usually, the most common ways to differentiate on devices is either using the BLE address, or the advertising name. I guess in your case, that you have several devices with the same name. 

Unfortunately, the BLE address is hidden by the OS if you are using an iPhone, so it is not possible for the Device Manager app to actually see the BLE address of the devices that it sees. 

So I think the easiest way to determine from the nRF Device Manager whether the device is provisioned would be to change the advertising name (since this is the only thing that is shown in the Device Manager app). Perhaps have the name the same as before, but include the Mesh Unicast address of the device? Or just some letter indicating that it is provisioned. 

In reality, you would probably have your own app, and not the device manager app. In that app, you can look for whatever field you want in the advertising packet. Perhaps you don't want to change the name of the device, but you could add some manufacturer specific data, that can hold any data that you prefer, and use this to determine whether the device is provisioned or not, and what device it is.

Best regards,

Edvin

[Sa.Ga.]

I am currently having the device developer check about changing advertise name in detail, it might not be possible without changes nRF-Connect-SDK.

Are there any other way?

Best regards.

[Edvin]

Not yet sure. But you want to update it/them via BLE, and not through Mesh, right?

BR,
Edvin

[Sa.Ga.]

I am not particular about updating via BLE.
I understand that the nRF5340 can only be updated via BLE.
Am I wrong?

Best regards.

[Sa.Ga.]

I have become unsure whether the update method I was trying to implement is correct or not.
Would you please tell me how to update the nRF5340 using the Mesh application recommended by Nordic?

Best regards.