Distinguish heartbeat messages from other messages in mesh network

[Mathias]

Hi!

I'm trying to log the flow of communication in the Light Control example of the Mesh SDK. But when I log all the received network messages on a server, I also get a lot of received heartbeat messages. I would like to distinguish between those and packets handling one specific communication between a sender and receiver. I tried several things (Destination address, packet length ...) but I don't seem to be able to find a way to identify a packet as a heartbeat packet alone. How would you guys do this?

Thanks in advance!

Mathias

[Hung Bui]

Hi Mathias,

Are you sure it's heartbeat packet ? not health status packet ? We haven't implemented heartbeat in our mesh SDK.

Have you try to check the opcode of the packet ? If you have a look at health_opcode_t inside health_opcodes.h you can find the list of opcode used for Health model.

By default the server will send fault status with HEALTH_OPCODE_CURRENT_STATUS opcode periodically.

[Mathias]

Hi!

Aha, that could be the case indeed. I'll check it out, thanks man! :)

[matsublox]

Any plans to support the heartbeat function. We are looking into providing some supervision functions of a large-scale network and heartbeat could be a useful part of that (in combination the Health model).

[Hung Bui]

Heartbeat is already supported in SDK v1.0.1. Calling config_client_heartbeat_publication_set() on the config client will configure the node to send heart beat.