Light switch mesh client to server and vica versa RSSI value

RE: Light switch mesh client to server and vica versa RSSI value

WHui — Mon, 11 Feb 2019 16:40:09 GMT

Hello Edvin,

I have found the app_onoff.c in nRF5_Mesh_SDK_v2.2.0 > examples > common > src, however if I made the changes, but I rebuild the project in examples > light_switch > thingy_provisioning_demo_generic_OnOff_Blink > light_switch_proxy_server_nRF52.emproject, the changes saved from the app_onoff.c won't have effect on the hex file generated by the .emproject file right?

Best regards,

WHui

RE: Light switch mesh client to server and vica versa RSSI value

fahad — Thu, 17 Jan 2019 11:46:48 GMT

hi edvin

thank yoou so much it works fine.

RE: Light switch mesh client to server and vica versa RSSI value

Edvin — Thu, 17 Jan 2019 11:27:14 GMT

Hello,

It is possible to check the RSSI value, but you should be aware that in Mesh, you don't necessarily receive the packet directly from the device that sent it. It may be several hops between the source and the destination of the packet. This is how mesh works to extend the range of the network, by retransmitting received packets.

In the light_switch\server example you can check the RSSI the following way:

In app_onoff.c there is already a line in the generic_onoff_state_set_cb() function that is printing "msg: SET" in the log. If you paste this line below that, you will see the rssi of the received message:

__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "rssi: %d\n", p_meta->p_core_metadata->params.scanner.rssi);

In addition, it may be a good idea to check the address. You can print this the following way:

    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "msg: SET: %d\n", p_in->on_off);
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "rssi: %d\n", p_meta->p_core_metadata->params.scanner.rssi);
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "addr %02x:%02x:%02x:%02x:%02x:%02x\n", p_meta->p_core_metadata->params.scanner.adv_addr.addr[0],
                                                                                p_meta->p_core_metadata->params.scanner.adv_addr.addr[1],
                                                                                p_meta->p_core_metadata->params.scanner.adv_addr.addr[2],
                                                                                p_meta->p_core_metadata->params.scanner.adv_addr.addr[3],
                                                                                p_meta->p_core_metadata->params.scanner.adv_addr.addr[4],
                                                                                p_meta->p_core_metadata->params.scanner.adv_addr.addr[5]);

Best regards,

Edvin

RE: Light switch mesh client to server and vica versa RSSI value

fahad — Wed, 16 Jan 2019 10:09:38 GMT

i got the rssi value of provision from client and server but how can i get rssi from client and server ?