This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Some questions for "nRF Mesh" apps and proxy client/server examples

Hi

I am trying "nRF Mesh" apps to provision and configure proxy client and proxy server node (SDK Mesh v2.2.0).

1. Have user manual or help information for "nRF Mesh" apps?

2. Did Nordic release Android source code of "nRF Mesh"? How about iOS version?

3. I tried connecting proxy client and server by nRF connect, and found Mesh proxy service (UUID:0x1828)

    but no Mesh provisioning service (UUID:0x1827).

    Why not use Mesh provisioning service in proxy client/server examples?

Mesh Provisioning Service: 

    Allows a Provisioning Client to provision a Provisioning Server to allow it to participate in the mesh network.

Mesh Proxy Service:           

    Enables a server to send and receive Proxy Protocol Data Units (PDUs) with a client.

  • Hi,

    1) I would recommend taking a look at this youtube video, which gives a good introduction to the nRF Mesh app.

    2) The source code is available in the comments section of the Youtube video.

    3) The UUID 0x1827 is defined here: #define NRF_MESH_PB_GATT_SERVICE_UUID  (0x1827) in nrf_mesh_prov_bearer_gatt.h. This documentation could also be helpful. I just tested the proxy client example from mesh sdk v2.2.0 & I only find the mesh provisioning service (UUID 0x1827) in the list of services in nRF Connect for iOS. The same goes for Android. Are you sure that you cannot see the proxy service in nRF Connect for Mobile? These two links might also be helpful: link 1 & link 2.

    Kind Regards,

    Bjørn

  • Hi Bjørn

    1. I watched the youtube video. But, the apps was NOT the same as the apps I downloaded fromm Google Play.

        The GUI was different. The apps version at my phone was v1.0. Please confirm it.

    2. OK. I can find the apps source code in Github.

    3. I read the explaination at infocenter. So, mesh provisioning service(UUID 0x1827) was active at provisioning stage. After provisioning was

        completed, apps disconnected  and reconnected device in order to do configuration. Correct?

        Then, mesh proxy service (UUID 0x1828) would replace mesh provisioning service (UUID 0x1827) to finish configuration.

    Now, I can provision and configure PCA10040 which flashed SDK Mesh v2.2.0 proxy client and proxy server.

    But, I also found some problems.

    1.  If all the unprovisioned devices are proxy clients or proxy server sand power on, I can scan all devices at scanner panel of apps.

         Then, try to select one by one to provision and configure all. First device was done successfully.However, as I selected next unprovisioned

         device, apps ran "provision" automatically and didn't wait I click "provision" button. Message was shown " sending composition data...".

         Then, disconnect this device and cancel provisioning.

         But, if I close the apps when current device was provisioned successfully and reopen the apps, next unprovisioned device can also be

         provisioned successfully.

    2.  Can  lighting client or server which didn't have GATT proxy feature also be provisioned and configured by apps via proxy nodes?

         I tried apps to scan unprovisioned lighting client and server when proxy nodes were connected and already provisioned.

         Apps cannot find these devices.

         In my opnion, I think it is more feasible that few proxy nodes exist at one mesh network.

         If all nodes in network have proxy feature, all nodes will broadcast connectable IND ADV packets. It will cause hevay noise for mesh

         network. 

     

     

  • Hi Jeffery,

    1) Yes, the Android app looks slightly different, but should have the same functionality as the iOS app.

    3) Yes, I believe the app disconnects because the softdevice needs to reset. I do not fully remember the details of why this needs to happen, but the behavior you mention should be correct.

    1) Could you please upload the debug log from nRF Mesh. I am not sure I fully understand. When you say: "Then, disconnect this device & cancel provisioning", did the nrf mesh app automatically disconnect from the device?

    2) The main idea with the proxy nodes is to have few proxy nodes which can connect to regular BLE devices. Like you mention, it does not necessarily make sense to only have proxy nodes because not all nodes will have to connect to a regular BLE device. Take a look at this devzone case for more information.

    Kind Regards,

    Bjørn

  • Hi Bjørn

    1. Can nRF Mesh apps  only support Generic ON/OFF model?

    2. If customer want to support variety of models, like Generic Level, and Battery etc., can nRF Mesh apps

        identify these models and show the model type in screen? It's similar to nRF Connect or Master control panel

        to show service types after service discovery. 

  • 1) Yes, that is correct as of today.

    2) This support may be available at a later date. If you send me a private message, I can put you in contact with your local regional sales manager. He may be able to help you further.

Related