Find out provisioned server nodes around the client?

[Andy]

I am currently using Mesh SDK 3.1, running on NRF52480 with SoftDevice140.  We are currently modifying the light switch client, and would like to know which servers are available, is that possible?   We would want to find out the IDs and RSSIs of the servers, but not clients or any other BLE devices.  Is this possible?  And which way is the easiest?

Thank you in advance!

[Joakim Jakobsen]

Hi.

Are you looking for the servers available to provision into the Mesh network?

Or servers already provisioned?

Best regards,
Joakim.

[Andy]

Thank you for the reply. I am looklng for provisioned servers, essentially servers that is in the same network as the client.

Thanks.

[Joakim Jakobsen]

Hi.

I suggest that you take a closer look at heartbeat messages.
Heartbeat messages are transmitted by nodes periodically. A heartbeat message indicates to other nodes in
the network that the node sending the heartbeat is still active. In addition, heartbeat messages contain
data which allows receiving nodes to determine how far away the sender is, in terms of the number of hops
required to reach it. This knowledge can be exploited with the TTL field.

Best regards,
Joakim.

[P Sumanth]

hey joakim jakobsen

I would like to know how can these heartbeat messages are used in main.c for usage in mesh and configure them with provisioner .I it possible to find RSSI for these messges and how. My idea is, I have two devices, one which publishes the data and other which subscribe, they should blink the led when both are out of range(ref distance). How can i do these with heartbeat message,i looked at the mesh profile specs, how i should implement practically.

regards

sumanth

[Joakim Jakobsen]

Hi. 

You should take a look at this post: 

https://devzone.nordicsemi.com/f/nordic-q-a/39270/ble-mesh-heartbeat-example 

Best regards, 
Joakim

[P Sumanth]

Hey i have gone through the post

I couldn't understand the procedure in following lines 

 "place the provisioner - HeartBeat & server - Heartbeat folders in the light_switch folder of the mesh sdk. Then, open the provisioner & client Segger Embedded Studio projects, go to Tools -> Options ... -> Building -> Global Macros & make sure the SDK_ROOT & MESH_SDK point to the correct paths."

Heartbeat is a c file, i couldn't understand how where he moved it since it was mentioned as folders, could you please explain elaborately and also about the rssi mentioned at the end of the post.

Regards

sumanth