ESP32 Forum

Hello,

I am using an ESP32-S3 chip to implement a BLE Mesh network, together with the Android nRF Mesh app.

Problem
I am using the Import/Export feature of the app. After exporting the configuration from phone A and importing it to phone B, all data (provisioned nodes, network keys, application keys, etc.) appears to transfer successfully. On phone B, the list of provisioned nodes from phone A is visible, and I am able to establish a connection.

However, immediately after the import, phone B cannot control functions such as on/off. The control only starts working after approximately 10 minutes, and then it operates normally from that point onward.

Expected Behavior
After importing the configuration from phone A to phone B, the provisioned nodes should be controllable immediately.

Actual Behavior
Right after the import, control commands (e.g., on/off) do not work. It takes about 10 minutes before they start working, after which everything functions normally.

Question
What should I do to ensure that, immediately after importing the configuration to a new phone, the provisioned nodes can be controlled without this waiting period?

Thank you.

Unfortunately, the nRF Mesh app currently doesn’t export the exact provisioner sequence number state.

Thank you for your reply.

So, would it be possible to modify the import/export code in the nRF app to add the provisioner sequence number status?

If the provisioner sequence number status is present, will it be controlled immediately?

Unfortunately, the nRF Mesh app currently doesn’t export the exact provisioner sequence number state.

Thank you for your reply.

So, would it be possible to modify the import/export code in the nRF app to add the provisioner sequence number status?

If the provisioner sequence number status is present, will it be controlled immediately?

Yes, you can modify the nRF Mesh app code. Add provisioner sequence number and IV Index to JSON. Import/export logic must handle these extra fields properly. On import, restore sequence number and IV Index. Nodes will then accept messages from phone B immediately. No 10-minute waiting period will be needed. This works only if data is restored correctly. Both phones must not use same sequence simultaneously. Otherwise, nodes may reject duplicate or replayed messages. With correct sync, control is immediate after import.