RE: Duplicate messages received by mesh server

CodeLoader — Mon, 12 Nov 2018 21:13:58 GMT

Thanks a lot! Even though I think server responds in less than 2 seconds, this value is still too small for the needed application.

RE: Duplicate messages received by mesh server

Bjørn Kvaale — Mon, 12 Nov 2018 13:47:41 GMT

As you can see in the code snippet belo, the add_reliable_message() function will reschedule an event if a timeout occurs:

static void add_reliable_message(uint16_t index, const access_reliable_t * p_message)
{
    NRF_MESH_ASSERT(!m_reliable.pool[index].in_use);
    uint32_t time_now = timer_now();
    memcpy(&(m_reliable.pool[index].params), p_message, sizeof(access_reliable_t));
    m_reliable.pool[index].interval = calculate_interval(p_message);
    m_reliable.pool[index].params.timeout += time_now;
    m_reliable.pool[index].next_timeout = time_now + m_reliable.pool[index].interval;

    bearer_event_critical_section_begin();
    if (is_earliest_timeout(index))
    {
        timer_sch_reschedule(&m_reliable.timer, m_reliable.pool[index].next_timeout);
        m_reliable.next_timeout_index = index;
    }
    m_reliable.pool[index].in_use = true;
    m_reliable.active_count++;
    bearer_event_critical_section_end();
}

If the server takes a bit too long time to respond with a status message, the client may have reached the timeout & sent another set message.

You could try changing the min timeout value for an reliable message in the access layer (see access_reliable.h):

/**
 * Minimum timeout for a reliable message in microseconds.
 * @note Mesh Profile Specification v1.0 recommends this to be minimum 60s.
 */
#define ACCESS_RELIABLE_TIMEOUT_MIN  (SEC_TO_US(2))

/** Maximum timeout for a reliable message in microseconds. */
#define ACCESS_RELIABLE_TIMEOUT_MAX  (SEC_TO_US(60))

It seems the min timeout value used to be 30 seconds in an older mesh sdk version, but I would test out a few values & see if this solves your issue.

RE: Duplicate messages received by mesh server

CodeLoader — Wed, 07 Nov 2018 14:33:23 GMT

I am using Mesh SDK v2.2.0

I put a log into packet_tx function, which is called by access_model_publish, and I could see that sometimes client transmits the message 2 times almost immediately one after another, before receiving the status from the server

And server replies to both of these messages

RE: Duplicate messages received by mesh server

Bjørn Kvaale — Wed, 07 Nov 2018 12:43:12 GMT

Which Mesh SDK version are you currently using? v2.0.1?