This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NCS: How to en-/disable the BT Mesh Gatt Proxy?

Dear NCS experts,

Considering a Bluetooth Mesh firmware application based on nRF Connect SDK 1.7.1 that is running on a nRF52832:
How do you enable/disable the gatt proxy? And how do you figure out if it is currently enabled?
 
Lets dig a little deeper:
The API contains two functions that seem promising: bt_mesh_cfg_gatt_proxy_get() and bt_mesh_cfg_gatt_proxy_set(). However, both of them require a net_idx and an address as parameters. It looks a little strange that a net_idx and an address are needed to communicate with the firmware's own (local) gatt proxy, so I doubt that these are the right functions. But if the are the right functions, where do you get the values for the net_idx and address parameters?
 
Any clarification is much appreciated,
Thank you,
Michael.
 

  • Hi Michael, 

    The bt_mesh_cfg_gatt_proxy_get() and bt_mesh_cfg_gatt_proxy_set() are for configuration client to configure a remote node. 


    For local node you can use bt_mesh_gatt_proxy_set() and bt_mesh_gatt_proxy_get(). But you need to enable/disable the support for the feature using macro 
    CONFIG_BT_MESH_GATT_PROXY in prj.conf. 

Related