RE: How to identify dulicate messages

Hung Bui — Fri, 13 Mar 2020 13:11:25 GMT

Hi Hugh,

Just an update from our team. The status message doesn't have an TID and it's not supposed to have one. It's just a packet represent the latest status of the bulb.

In mesh we do have a way to detect a message that's already received. It's called message caching. And a sequence number is used to detect the message. The sequence number is not forwarded to the access layer. If you really need to detect the duplicated messages you can modify the upper_transport_packet_in() function in transport.c to forward the sequence number of the packet into access layer (upper_transport_access_packet_in() function).

The sequence number is inside network_packet_metadata_t struct, which you can find in p_metadata->net

Another solution, which I think maybe easier is to simply discard status packet that you receive from the gateway if the value doesn't change from the period status.

RE: How to identify dulicate messages

Hung Bui — Thu, 12 Mar 2020 17:54:28 GMT

Hi Hugh,

In theory this issue can be solved by the TID (transaction ID) that should be unique for each message. However it's not included in the Generic On Off Status message definition. I can see in our code that we have the generic_onoff_state_t struct that contain the on_off status and the transaction ID. But we haven't used it.

I would need to double check with the Mesh team to see if there is anything defined in the spec about this.

Otherwise you would need to send it as a proprietary access packet. Or create your own model for the purpose.