bt_mesh_model_send doesn't go back to sleep

[Shahin97]

Hello, 

I have a custom board running as a low power node, consuming around 17uA during sleep. When I have messages back and forth, the node goes back to sleep as usual. However, After I send my first unsolicited message, the device goes to 200uA and never goes back to 17uA.

int32_t bmns_init_sendVndMsg(bmns_opcode_def opcode, uint8_t *bufferIn, uint32_t len)
{
    struct bt_mesh_model *mod = vnd_mod_pub_ctx.mod;

    struct bt_mesh_msg_ctx ctx = {
            .addr = 0x0001,
            .app_idx = mod->keys[0],
            .send_ttl = BT_MESH_TTL_DEFAULT,
    };

    BT_MESH_MODEL_BUF_DEFINE(buf, opcode, len);
    bt_mesh_model_msg_init(&buf, opcode);

    net_buf_simple_add_mem(&buf, bufferIn, len);
    net_buf_simple_add(&buf, '\0');

    return bt_mesh_model_send(mod, &ctx, &buf, &bmns_vnd_model_cb, NULL);
}

Thank you, 

Shahin.

[Didrik Rokhaug]

Hi,

Our BT Mesh expert is out of office today due to a public holiday in Norway, but we will get back to you next week.

We apologize for the inconvenience.

Best regards,

Didrik

[Shahin97]

Hiya, I've had over a dozens of notifications with "An engineer has been assigned to bt_mesh_model_send doesn't go back to sleep" over the past few weeks. Is there an issue with then notifications?

[tesc]

Hi,

Rather it's human error. My appologies.

Regards,
Terje

[tesc]

Hi,

From what I can tell, it looks like the simple buffer cannot be safely extended past the originally configured length, which you seem to do by adding the null terminator (the '\0' byte) at the end. Does adjusting the length correspondingly (or adding one less byte with net_buf_simple_add_mem) solve the issue?

Regards,
Terje

[Shahin97]

@tesc

I have removed that, no difference, the problem isn't the payload being sent out. The payload is sent and received fine. However after that payload the node does not go back to sleep. 

This is only with unsolicited messages