After the Bluetooth mesh dfu is completed, the distribution network information of the node is cleared

[llly]

I have implemented DFU functionality in my Bluetooth mesh project and used device A as the distributor and device B as the node to be updated. I have already configured both devices and they can communicate with each other. Then I use the distributor to send new firmware to the node. After the node firmware is successfully updated, the original distribution network information of the node is cleared. At this point, the distributor and the node cannot communicate and need to manually reconfigure the distribution network. How can the original distribution network data be retained during DFU updates?

[llly]

Okay, I'll test it later

[llly]

I have tested it with three devices and can confirm that the problem is with the updated node

The log in the figure shows that the distributor can receive messages from two nodes with unicast addresses 0x8e and 0x8d

Then I started updating node 8e. During the process of sending firmware to 8e by the distributor, mesh communication was still normal, and the distributor was able to receive messages from both nodes

After the update is completed, the original version number of 8e has been changed to the new version number, indicating that the update was successful. At this point, the distributor can only receive messages from 8d

[Hung Bui]

Hi Illy, 
Thanks for the info. 
Do you have any log from the updated note after DFU update? Did it advertise as unprovisioned node or you have to manually clear it ? 
There is a chance that if the sequence number of the updated note reset and it will not be able communicate if it does. 
What you do you mean by "original version number of 8e" ? 

[llly]

Hi

After the update is completed, there are no special logs, it just starts normally.In the NRF Mesh app, it appears as an unconfigured node

"original version number of 8e" refers to the app version number before the update, which I have customized

I tested again with 52840dk today (in yesterday's and previous tests, the distributor and two nodes were both 54l15). Use the distributor (54l15dk) to update 52840dk. After the update is completed, the situation remains the same as yesterday, so this issue should not be related to the chip model

[Hung Bui]

Hi Illy, 
Please clarify, the node appear as "unconfigured node" or "unprovisioned node" ? They are different. 
If possible please provide the log on the device get provisioned. 
Have you tried to test with one of our sample (light switch for example) to see if you have the same issue ?