Problem with IV index udpate

[Fabbros]

Hi,
I did some test with IV index using nRF Mesh, here the steps:

1. provisioned 2 devices in a new mesh (device that have nordic SDK, IV test flag enabled)
2. from one devices, I triggered the IV index update from 0 to 1
3. after the finish of the IV procedure, I tried to interact with devices using nRF Mesh -> OK (get/set status, bind app key etc)
4. from the same device of point 2, I triggered the IV index update again, from 1 to 2
5. after the finish of the IV procedure, I tried to interact with devices using nRF Mesh -> FAIL (can't get/set status, can't bind app key etc)
6. I also tried to add a third device into the same mesh -> provisioning ok but every next operation fails (can't bind app key, get/set status is not possibile due to missing app key binding)

It seems that when mesh IV is over 1 nRF mesh can't interact with it because app still use IV 0 while the devices use IV 2.

I tried the steps above using:

• Android nRF Mesh v3.2.4
• iOS nRF Mesh v3.2.0

I also opened an issue on GitHub (see https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library/issues/537)

[Fabbros]

Is there anyone who can help me?

[Hung Bui]

Hi Fabbros, 
I'm sorry for the late response. Håkon is on a business trip so I will take over the case. 

I will check with the app team to see if there is any issue with the app.

But in the mean time to isolate the problem to see if it's the issue only on the app or it also an issue with the mesh firmware, could you let me know after you do IV update from 1 to 2 , other devices in the network can still communicate to each other ? For example if you have a client and a server (both running on nRF5 device) can they communicate to each other when doing IV update ? 

At which IV Update state (Normal/In Progress) do you see the app on the phone stopped responding ? When the issue happen, can you control the node that already provisioned to the mesh network ? 

[Fabbros]

Hi Hung Bui, 

thank you for taking over.

I tried setting the Generic_OnOff_Client of device A to publish to the Generic_OnOff_Server of device B and they work fine also with IV 2.

The app stop working after IV Update state change to Normal operation. After that, the only thing I can do is connecting to the proxy. Everything else seem not to work (I checked: apply binding, read/set state to a Generic_OnOff_Server)

[Hung Bui]

Hi Fabbros, 

Thanks for the info. The issue is seem to be on the app side. 
If you disconnect and connect to already provisioned proxy would you be able to communicate with them ? 
We will try to reproduce the issue here and let you know what we find. 

If you can list exact step on how you trigger the IV index update, how you verify that it's on Normal state, etc it would be great. 

[Fabbros]

I work for a Home Automation Company that developed an app (both Android and iOS) which configures our mesh devices (based on Nordic). I'm talking about thousands client that are using our app. We started experiencing several cases where IV is stepped to 1, with the time passing by we are expecting to get cases with IV 2 very soon and that will be dramatic.

First time we saw the issue we were using and old android SDK which wasn't able to communicate with device with IV 1, so we updated the SDK to fix that. Now we're doing some digging into the IV procedure and find out that if the IV step to 2 the app stop working again. To do the test we modify our devices enabling the IV test flag (to skip the canonical 96 hours) and force one of them to trigger the IV procedure from 0 to 1 and then from 1 to 2.

To verify the current IV status, and the current status of IV procedure (Normal vs update) we use nRF Connect because it shows the devices SNB Advertising. 

[Hung Bui]

Thanks for the info. We will try to reproduce the issue here. 
In the mean time could you try to get any log from the app by connecting it to a computer ? 

[Fabbros]

Here are the log and a screen record of the following operations:

1. connect to mesh (with IV 2)
2. try to read a generic_onoff_server status -> FAIL
3. try to set a generic_onoff_server status -> FAIL

Fullscreen get_set_generic_onoff_server.txt Download

--------- beginning of main
10-20 17:00:08.622 21103 21124 E BLASTBufferQueue: BLASTBufferItemConsumer::onDisconnect()
10-20 17:00:08.622 21103 21124 D OpenGLRenderer: endAllActiveAnimators on 0xb400007778986a00 (RippleDrawable) with handle 0xb400007772498180
10-20 17:00:13.682 21103 27900 D SurfaceComposerClient: VRR [FRTC] client handle [bufferId:18446744073709551615 framenumber:0] [ffffffff, ffffffff]
10-20 17:00:23.481 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:23.481 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:23.482 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:23.515 21103 21103 D WindowManager: Add to mViews: DecorView@8d44ea[ScannerActivity],pkg= no.nordicsemi.android.nrfmeshprovisioner
--------- beginning of system
10-20 17:00:23.519 21103 21103 I Quality : Skipped: false 2 cost 48.86976 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:23.531 21103 21103 V OplusZoomWindowDecorViewHelper: setLastReportedMergedConfiguration mZoomDisplayHeight: 2400 getDecorView.9258218
10-20 17:00:23.537 21103 21103 D BluetoothAdapter: isLeEnabled(): ON
10-20 17:00:23.539 21103 24885 D BluetoothLeScanner: onScannerRegistered() - status=0 scannerId=8 mScannerId=0
10-20 17:00:23.540 21103 27900 D SurfaceComposerClient: VRR [FRTC] client handle [bufferId:18446744073709551615 framenumber:0] [ffffffff, ffffffff]
10-20 17:00:23.551 21103 21103 I Quality : Skipped: false 1 cost 28.11499 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:23.966 21103 21124 E BLASTBufferQueue: BLASTBufferItemConsumer::onDisconnect()
10-20 17:00:23.966 21103 21124 D OpenGLRenderer: endAllActiveAnimators on 0xb400007778986a00 (RippleDrawable) with handle 0xb4000077724986e0
10-20 17:00:25.309 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:25.309 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:25.309 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:25.322 21103 21103 E ActivityThread: Failed to find provider info for no.nordicsemi.android.log
10-20 17:00:25.322 21103 21103 D AA      : Connect issued
10-20 17:00:25.325 21103 21103 D BluetoothGatt: connect() - device: DB:C5:F7:AC:85:97, auto: false, eattSupport: false
10-20 17:00:25.325 21103 21103 D BluetoothGatt: registerApp()
10-20 17:00:25.325 21103 21103 D BluetoothGatt: registerApp() - UUID=0f218048-db8d-4e53-bc11-835716cc0e24
10-20 17:00:25.327 21103 24885 D BluetoothGatt: onClientRegistered() - status=0 clientIf=10
10-20 17:00:25.332 21103 21103 D WindowManager: Add to mViews: DecorView@f924470[ReconnectActivity],pkg= no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:25.363 21103 21103 V OplusZoomWindowDecorViewHelper: setLastReportedMergedConfiguration mZoomDisplayHeight: 2400 getDecorView.261244016
10-20 17:00:25.381 21103 24885 D SurfaceComposerClient: VRR [FRTC] client handle [bufferId:18446744073709551615 framenumber:0] [ffffffff, ffffffff]
10-20 17:00:25.790 21103 21124 E BLASTBufferQueue: BLASTBufferItemConsumer::onDisconnect()
10-20 17:00:25.803 21103 21103 D BluetoothAdapter: isLeEnabled(): ON
10-20 17:00:30.386 21103 24885 D BluetoothGatt: onClientConnectionState() - status=0 clientIf=10 device=DB:C5:F7:AC:85:97
10-20 17:00:30.387 21103 21103 I BleManager: Connected to DB:C5:F7:AC:85:97
10-20 17:00:30.689 21103 21103 D BluetoothGatt: discoverServices() - device: DB:C5:F7:AC:85:97
10-20 17:00:30.915 21103 24885 D BluetoothGatt: onConnectionUpdated() - Device=DB:C5:F7:AC:85:97 interval=198 latency=0 timeout=400 status=0
10-20 17:00:33.389 21103 24885 D BluetoothGatt: onConnectionUpdated() - Device=DB:C5:F7:AC:85:97 interval=6 latency=0 timeout=500 status=0
10-20 17:00:33.539 21103 24885 D BluetoothGatt: onSearchComplete() = Device=DB:C5:F7:AC:85:97 Status=0
10-20 17:00:33.540 21103 21103 I BleManager: Services discovered
10-20 17:00:33.541 21103 21103 D BluetoothGatt: configureMTU() - device: DB:C5:F7:AC:85:97 mtu: 517
10-20 17:00:33.559 21103 24885 D BluetoothGatt: onConfigureMTU() - Device=DB:C5:F7:AC:85:97 mtu=69 status=0
10-20 17:00:33.560 21103 21103 I BleManager: MTU changed to: 69
10-20 17:00:33.560 21103 21103 D BluetoothGatt: setCharacteristicNotification() - uuid: 00002ade-0000-1000-8000-00805f9b34fb enable: true
10-20 17:00:33.597 21103 21103 I BleManager: Data written to descr. 00002902-0000-1000-8000-00805f9b34fb, value: (0x) 01-00
10-20 17:00:33.597 21103 21103 I BleManager: Notifications enabled
10-20 17:00:33.634 21103 21156 D BluetoothGatt: onConnectionUpdated() - Device=DB:C5:F7:AC:85:97 interval=198 latency=0 timeout=400 status=0
10-20 17:00:33.636 21103 21103 I BleManager: Notification received from 00002ade-0000-1000-8000-00805f9b34fb, value: (0x) 01-01-02-4E-8C-FD-1C-14-E3-75-9A-00-00-00-02-11-78-EB-61-FA-DB-15-D8
10-20 17:00:33.650 21103 21103 D BluetoothAdapter: isLeEnabled(): ON
10-20 17:00:33.652 21103 21156 D BluetoothLeScanner: onScannerRegistered() - status=0 scannerId=8 mScannerId=0
10-20 17:00:33.660 21103 21103 D MeshManagerApi: Received mesh beacon: SecureNetworkBeacon { KeyRefreshActive: false, IV Index: IV Index: 2, IV Update Active: true, Authentication Value: 0x1178EB61FADB15D8}
10-20 17:00:33.660 21103 21103 D MeshManagerApi: Secure Network Beacon authenticated.
10-20 17:00:33.660 21103 21103 D MeshManagerApi: Last IV Index: 1
10-20 17:00:33.660 21103 21103 W MeshManagerApi: Discarding beacon IV Index: 2, IV Update Active: true, last 1, changed: 0h ago, test mode: true
10-20 17:00:33.687 21103 21156 D SurfaceComposerClient: VRR [FRTC] client handle [bufferId:18446744073709551615 framenumber:0] [ffffffff, ffffffff]
10-20 17:00:33.771 21103 21103 I Quality : Skipped: false 2 cost 33.87801 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:33.772 21103 21156 D SurfaceComposerClient: VRR [FRTC] client handle [bufferId:18446744073709551615 framenumber:0] [ffffffff, ffffffff]
10-20 17:00:33.783 21103 21103 D BluetoothAdapter: isLeEnabled(): ON
10-20 17:00:33.801 21103 21103 V OplusZoomWindowDecorViewHelper: removeZoomView
10-20 17:00:33.803 21103 21124 E BLASTBufferQueue: BLASTBufferItemConsumer::onDisconnect()
10-20 17:00:33.817 21103 21103 I Quality : Skipped: true 1 cost 29.743204 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:34.213 21103 21124 E BLASTBufferQueue: BLASTBufferItemConsumer::onDisconnect()
10-20 17:00:34.239 21103 21103 V OplusZoomWindowDecorViewHelper: removeZoomView
10-20 17:00:36.879 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:36.879 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:36.879 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:36.895 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:36.895 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:36.895 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:36.932 21103 21103 I Quality : ActivityThread: activityStart delay 62 no.nordicsemi.android.nrfmeshprovisioner 21103
10-20 17:00:36.936 21103 21103 D WindowManager: Add to mViews: DecorView@79fea7d[NodeConfigurationActivity],pkg= no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:36.940 21103 21103 I Quality : Skipped: false 3 cost 63.11704 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:36.985 21103 21103 V OplusZoomWindowDecorViewHelper: setLastReportedMergedConfiguration mZoomDisplayHeight: 2400 getDecorView.127920765
10-20 17:00:37.013 21103 21237 D SurfaceComposerClient: VRR [FRTC] client handle [bufferId:18446744073709551615 framenumber:0] [ffffffff, ffffffff]
10-20 17:00:37.019 21103 21103 I Quality : Skipped: false 4 cost 74.74702 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:37.438 21103 21124 E BLASTBufferQueue: BLASTBufferItemConsumer::onDisconnect()
10-20 17:00:37.438 21103 21124 D OpenGLRenderer: endAllActiveAnimators on 0xb40000777893fe00 (RippleDrawable) with handle 0xb4000077724987e0
10-20 17:00:39.776 21103 21103 D OplusSystemUINavigationGesture: [GESTURE_BUTTON] swipe from 1
10-20 17:00:39.777 21103 21103 D OplusSystemUINavigationGesture: [GESTURE_BUTTON] Hit Gesture Region !
10-20 17:00:42.497 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:42.497 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:42.497 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:42.502 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:42.502 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:42.502 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:42.514 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:42.514 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:42.514 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:42.523 21103 21103 W SingleLiveEvent: Multiple observers registered but only one will be notified of changes.
10-20 17:00:42.523 21103 21103 W SingleLiveEvent: Multiple observers registered but only one will be notified of changes.
10-20 17:00:42.525 21103 21103 W SingleLiveEvent: Multiple observers registered but only one will be notified of changes.
10-20 17:00:42.539 21103 21103 I Quality : ActivityThread: activityStart delay 51 no.nordicsemi.android.nrfmeshprovisioner 21103
10-20 17:00:42.542 21103 21103 D WindowManager: Add to mViews: DecorView@b00c692[GenericOnOffServerActivity],pkg= no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:42.546 21103 21103 I Quality : Skipped: false 3 cost 64.33493 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:42.567 21103 21103 V OplusZoomWindowDecorViewHelper: setLastReportedMergedConfiguration mZoomDisplayHeight: 2400 getDecorView.184600210
10-20 17:00:42.598 21103 21103 I Quality : Skipped: false 2 cost 49.369556 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:42.600 21103 21237 D SurfaceComposerClient: VRR [FRTC] client handle [bufferId:18446744073709551615 framenumber:0] [ffffffff, ffffffff]
10-20 17:00:43.025 21103 21124 E BLASTBufferQueue: BLASTBufferItemConsumer::onDisconnect()
10-20 17:00:43.025 21103 21124 D OpenGLRenderer: endAllActiveAnimators on 0xb400007778838200 (RippleDrawable) with handle 0xb40000777838f860
10-20 17:00:44.870 21103 21103 V GenericOnOffServerActivity: Sending message to element's unicast address: 0x0006
10-20 17:00:44.871 21103 21103 V MeshTransport: Src address: 0001
10-20 17:00:44.871 21103 21103 V MeshTransport: Dst address: 0006
10-20 17:00:44.871 21103 21103 V MeshTransport: Key: C8A3CA5CEEEA37E2805710ED1B11CE3F
10-20 17:00:44.871 21103 21103 V MeshTransport: akf: 1
10-20 17:00:44.871 21103 21103 V MeshTransport: aid: 8
10-20 17:00:44.871 21103 21103 V MeshTransport: aszmic: 0
10-20 17:00:44.871 21103 21103 V MeshTransport: Sequence number: 43
10-20 17:00:44.871 21103 21103 V MeshTransport: Access message opcode: 8201
10-20 17:00:44.871 21103 21103 V MeshTransport: Access message parameters: 
10-20 17:00:44.871 21103 21103 V AccessLayer: Created Access PDU 8201
10-20 17:00:44.871 21103 21103 V UpperTransportLayer: Application nonce: 010000002B0001000600000000
10-20 17:00:44.872 21103 21103 V UpperTransportLayer: Encrypted upper transport pdu: C4060431A8C0
10-20 17:00:44.872 21103 21103 V LowerTransportLayer: Unsegmented Lower transport access PDU 48C4060431A8C0
10-20 17:00:44.872 21103 21103 V NetworkLayer: Encryption key: 4FFB990E5BD5414B03CCDD1A49DEFCD5
10-20 17:00:44.872 21103 21103 V NetworkLayer: Privacy key: AF76E5B4807FD1F54CE84403C54AF880
10-20 17:00:44.872 21103 21103 V NetworkLayer: Sequence Number: 00002B
10-20 17:00:44.872 21103 21103 V NetworkLayer: Encrypted Network payload: 2887A1BF383CD4C0DA8C704B99
10-20 17:00:44.886 21103 21103 I BleManager: Data written to 00002add-0000-1000-8000-00805f9b34fb, value: (0x) 00-70-AE-FD-77-54-DA-0B-28-87-A1-BF-38-3C-D4-C0-DA-8C-70-4B-99
10-20 17:00:44.899 21103 21103 V MeshManagerApi: MeshNetwork pdu sent: 0x0070AEFD7754DA0B2887A1BF383CD4C0DA8C704B99
10-20 17:00:54.913 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:54.913 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:54.913 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:54.917 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:54.917 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:54.917 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:00:54.932 21103 21103 D WindowManager: Add to mViews: DecorView@17a1bfd[GenericOnOffServerActivity],pkg= no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:54.939 21103 21103 I Quality : Skipped: false 2 cost 36.52111 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:54.971 21103 21103 V OplusZoomWindowDecorViewHelper: setLastReportedMergedConfiguration mZoomDisplayHeight: 2400 getDecorView.24779773
10-20 17:00:54.993 21103 21103 I Quality : Skipped: false 2 cost 39.662968 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:00:55.005 21103 27900 D SurfaceComposerClient: VRR [FRTC] client handle [bufferId:18446744073709551615 framenumber:0] [ffffffff, ffffffff]
10-20 17:00:56.715 21103 21103 V OplusZoomWindowDecorViewHelper: removeZoomView
10-20 17:00:56.717 21103 21124 E BLASTBufferQueue: BLASTBufferItemConsumer::onDisconnect()
10-20 17:00:56.717 21103 21124 D OpenGLRenderer: endAllActiveAnimators on 0xb400007761c2f600 (RippleDrawable) with handle 0xb4000077724c6f60
10-20 17:00:58.109 21103 21103 V GenericOnOffSet: State: ON
10-20 17:00:58.109 21103 21103 V GenericOnOffSet: Transition steps: 0
10-20 17:00:58.109 21103 21103 V GenericOnOffSet: Transition step resolution: 0
10-20 17:00:58.110 21103 21103 V MeshTransport: Src address: 0001
10-20 17:00:58.110 21103 21103 V MeshTransport: Dst address: 0006
10-20 17:00:58.110 21103 21103 V MeshTransport: Key: C8A3CA5CEEEA37E2805710ED1B11CE3F
10-20 17:00:58.110 21103 21103 V MeshTransport: akf: 1
10-20 17:00:58.110 21103 21103 V MeshTransport: aid: 8
10-20 17:00:58.110 21103 21103 V MeshTransport: aszmic: 0
10-20 17:00:58.110 21103 21103 V MeshTransport: Sequence number: 44
10-20 17:00:58.110 21103 21103 V MeshTransport: Access message opcode: 8202
10-20 17:00:58.110 21103 21103 V MeshTransport: Access message parameters: 01470000
10-20 17:00:58.111 21103 21103 V AccessLayer: Created Access PDU 820201470000
10-20 17:00:58.111 21103 21103 V UpperTransportLayer: Application nonce: 010000002C0001000600000000
10-20 17:00:58.111 21103 21103 V UpperTransportLayer: Encrypted upper transport pdu: 17A375DD66E518AA4303
10-20 17:00:58.111 21103 21103 V LowerTransportLayer: Unsegmented Lower transport access PDU 4817A375DD66E518AA4303
10-20 17:00:58.111 21103 21103 V NetworkLayer: Encryption key: 4FFB990E5BD5414B03CCDD1A49DEFCD5
10-20 17:00:58.112 21103 21103 V NetworkLayer: Privacy key: AF76E5B4807FD1F54CE84403C54AF880
10-20 17:00:58.112 21103 21103 V NetworkLayer: Sequence Number: 00002C
10-20 17:00:58.112 21103 21103 V NetworkLayer: Encrypted Network payload: 8030C03A9DE38C58E5B16A55F89195AD4A
10-20 17:00:58.130 21103 21103 I BleManager: Data written to 00002add-0000-1000-8000-00805f9b34fb, value: (0x) 00-70-A8-CD-B0-23-16-B5-80-30-C0-3A-9D-E3-8C-58-E5-B1-6A-55-F8-91-95-AD-4A
10-20 17:00:58.130 21103 21103 V MeshManagerApi: MeshNetwork pdu sent: 0x0070A8CDB02316B58030C03A9DE38C58E5B16A55F89195AD4A
10-20 17:01:08.163 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:01:08.163 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:01:08.163 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:01:08.167 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:01:08.167 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:01:08.167 21103 21103 I oplus.android.OplusFrameworkFactoryImpl: get feature:IOplusDynamicVsyncFeature
10-20 17:01:08.185 21103 21103 D WindowManager: Add to mViews: DecorView@86e744[GenericOnOffServerActivity],pkg= no.nordicsemi.android.nrfmeshprovisioner
10-20 17:01:08.192 21103 21103 I Quality : Skipped: false 2 cost 40.410442 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:01:08.220 21103 21103 V OplusZoomWindowDecorViewHelper: setLastReportedMergedConfiguration mZoomDisplayHeight: 2400 getDecorView.8841028
10-20 17:01:08.237 21103 21103 I Quality : Skipped: false 2 cost 34.390915 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner
10-20 17:01:08.237 21103 27900 D SurfaceComposerClient: VRR [FRTC] client handle [bufferId:18446744073709551615 framenumber:0] [ffffffff, ffffffff]
10-20 17:01:09.804 21103 21103 V OplusZoomWindowDecorViewHelper: removeZoomView
10-20 17:01:09.809 21103 21124 E BLASTBufferQueue: BLASTBufferItemConsumer::onDisconnect()
10-20 17:01:09.809 21103 21124 D OpenGLRenderer: endAllActiveAnimators on 0xb400007763829600 (RippleDrawable) with handle 0xb4000077725979a0
10-20 17:01:09.834 21103 21103 I Quality : Skipped: true 1 cost 27.746004 refreshRate 0 processName no.nordicsemi.android.nrfmeshprovisioner

[Hung Bui]

Hi Fabbros, 
I would suggest to continue the discussion with Philips on github. 
What we are seeing in your log is that the SNB beacon was rejected because it was going straight from Index 1 active (In progress) state to Index 2 active (In progress) and that's not allowed. 
It must go from Index 1 active to Index 2 normal before go to Index 2 active. 

What need to be checked is that you have test mode set up on all the nodes. And you go step by step, first update form Index 0 to index 1, make Index 1 normal. Then change index 1 to index 2. Make index 2 normal before sending the next one.