RSSI Value of the client from server

RE: RSSI Value of the client from server

Duy — Fri, 28 Dec 2018 08:35:45 GMT

Hi Hung Bui,

Thank you for your reminding, I checked back and I discovered that I have to increase the period to 1s for the health server to publish (the default is 100ms, but it works when using with the on/off model and level model). The health model works when using with cell phone but the smallest period is 1s which I still haven't known why...

RE: RSSI Value of the client from server

Hung Bui — Fri, 28 Dec 2018 07:37:47 GMT

Hi Duy,

I'm not possible to test it right now. But have you configured the publication period ? Also there is a special thing about the health model is that both the source and the destination need to match as I mentioned in the last reply above. Maybe it's the reason why you can't configure it as a normal model.

RE: RSSI Value of the client from server

Duy — Fri, 21 Dec 2018 09:35:42 GMT

Hi Hung Bui, hi aditya,

Continue aditya's question, as I understand, the provisioner configures the health servers to publish to its health client model. In case I use the nRF Mesh and my cellphone as the provisioner, I can also do the same: bind the same app key for both health client and health servers, then set the health servers to publish to the health client.

I tested with the nRF Mesh app but it didn't work. There was no event to the health client. You have any idea to check whether there is a misconfiguration in the firmware or it's because of the mobile app?

Thank you

RE: RSSI Value of the client from server

Hung Bui — Wed, 05 Sep 2018 16:03:44 GMT

Hi ,
Health server and health client are independent. You can have them both on one device, but they need to be on different elements.

RE: RSSI Value of the client from server

aditya — Wed, 05 Sep 2018 09:51:57 GMT

Hi Hung Bui,

I have one doubt, if we make one node as health client other than provisioner, will it also acts as health server to send its health status?

RE: RSSI Value of the client from server

Hung Bui — Fri, 03 Aug 2018 16:18:37 GMT

Hi Arya,

I haven't done this myself. But my understanding on how to do this, is: first you need to configure your device to listen to particular heartbeat. You do that by calling config_client_heartbeat_subscription_set() from the config client (of the provisioner for example) to configure the source and the destination of heartbeats the node(s) should listen to.

Then in your node, if you have a matched heartbeat, you will receive an event TRANSPORT_CONTROL_OPCODE_HEARTBEAT and it will be processed in heartbeat_opcode_handle() inside that you have the RSSI value in p_rx_metadata to be used.

RE: RSSI Value of the client from server

Arya — Fri, 03 Aug 2018 10:33:49 GMT

Hi Hung Bui,

Can you help me some more for getting rssi from heartbeat messages? Now I am sending a message from client to server and from that packet I am receiving the rssi. How to do that through heartbeat messages?

RE: RSSI Value of the client from server

Hung Bui — Tue, 31 Jul 2018 16:23:00 GMT

Hi Arya,

If you have a look at the node_setup.c you can find that when the provisioner configure a node, it will set the publication address of the health server to the provisioner address. So they will only send health message to the provisioner. If you want to have other node to be able to receive health message you need to configure the publication address to the node or to a group address. And then you configure the health client to subscribe to that address.

Also you would need to bind the app key of the health client to the app key that the provisioner assign to the health server.

But for your purpose, I would suggest to use HeartBeat to detect RSSI and the TTL to other node. Please read more about that in the mesh spec (section 3.6.7).