nRF Mesh not finding proxy node

[bluetooth_mdw]

Hi

I have a test mesh network, with several devices provisioned using nRF Mesh and.... a proxy node which has been provisioned using an alternative method but with the same netkey, appkey and so on as the other nodes. In other words it is part of the same mesh network, albeit not listed in the nRF Mesh provisioning database. nRF Mesh cannot find the proxy to connect to it though. It is advertising using network identity, so I think that should be sufficient to identify it as a proxy which belongs to this network. Does nRF Mesh ignore nodes which are not in its database though, maybe using the BD_ADDR?

nRF Connect can see the node fine:

Any ideas why I can't use this proxy from nRF Mesh?

Thanks

Martin

[Aleksander Nowakowski]

Hello,

After reading the source code of nRF Mesh (https://github.com/NordicSemiconductor/Android-nRF-Mesh-Library/blob/aa21e2d6c6be5bad5a9b9bcb4bf91f58ec11c7d6/Example/nrf-mesh/app/src/main/java/no/nordicsemi/android/nrfmeshprovisioner/viewmodels/ScannerRepository.java#L84) I would say, that the new Node should pop up on the "Scanner" screen, even though it wasn't added by the app itself or is not in the local database. This is if the app knows the Network Key, that the new node used to calculate Network ID, which I suppose it does. To be 100%, and to find out why you can't see it, I can ask the author of the Android nRF Mesh, which comes back from vacations on Monday.

Did you happen to try the same scenario on the nRF Mesh for iOS, but on the version that is available on GitHub (not the one on App Store)?
https://github.com/NordicSemiconductor/iOS-nRF-Mesh-Library/ -> branch *version2*

[bluetooth_mdw]

Hi! See my answer to Roshan.... but no, I haven't tried the iOS version of the app. Maybe next time.....