mesh light_switch_server not sending massage to other server in mesh

[nikunj8086]

hi,

i doing a project where i have combined light switch server from nrf_mesh sdk 1.0.0 with nrf5 sdk 14.2.0 ble_uart_example to send.

my aim is to send on_off command from nrf tool_box app to ble_uart_example and according to that input light_switch_server should operate and send command to mesh if command is for other node in mesh.

so far i have done is that flashed 3 nrf 52832 with my light_switch_ble_uart example, and provisioned with a separate light switch client.

so now i am able to send command from node 1 which has provision address of 0x0100 to other 2 nodes.

but when i tried same with other nodes which has provision address 0x0101 and 0x0102, i am not seeing any response on other nodes.(but all 3 nodes are flashed with same code).

please help me.

[Mttrinh]

Hi,

It is possible that you haven't configured your nodes properly. It is not enough to just provision them, they also have to be configured, like the light switch example does with the server-models. 

I need more details to help you with the issue. Do you configure your devices or are you just provisioning them? Which modifications have you done to the example? Which mesh-address are you sending to?

[nikunj8086]

hi  Mttrinh,

yes, you are right since i was using custom nrf_mesh_config_app.h from this link.(ble_app_proximity_mesh_lightswitch_server.zip).

so i change it back to original light switch server example's "nrf_mesh_config_app.h" file and then it works.

i was able to send set commands to other node from light switch server its self.

but still i am not able to understand how to reduce mesh activity from Coexistence with other Nordic SDKs about "Concurrent SoftDevice and mesh activity" where it says that "You should also reduce mesh activity while the SoftDevice is doing fast advertising ".

please let me know.

thanks.

[Mttrinh]

To reduce mesh activity, you just have to send less data. There aren't much else you can control from the application. There shouldn't be any problem unless you stream data over the mesh.

So until you detect NO_MEM-errors on any of your TX calls, you have nothing to worry about.