"Wrong" TTL when replying to a message with TTL set to 0

[JonasJ]

Hi,

In Mesh Profile v1.0 section 3.7.5.2 Acknowledged message one can read the following text.

"... If the acknowledged message has TTL set to 0, it is recommended that the response message should have TTL set to 0."

But it appears that the Mesh SDK doesn't follow this recommendation.

In access.c the function packet_tx() has this part that determines the ttl.

    uint8_t ttl;
    if (m_model_pool[handle].model_info.publish_ttl == ACCESS_TTL_USE_DEFAULT)
    {
        ttl = m_default_ttl;
    }
    else
    {
        ttl = m_model_pool[handle].model_info.publish_ttl;
    }

That is, either use the default TTL or the configured one. I would have expected the code to consider the TTL of the p_rx_message and set it to 0 if needed.

Thanks.

[Mttrinh]

Hi,

I talked to the Mesh team and it seems to be a bug, and will be fixed in the next release.

Thank you for reporting this.