BLE mesh : Failed to publish & Out of network adv

RE: BLE mesh : Failed to publish & Out of network adv

Ziyao Zhou — Tue, 13 May 2025 12:39:47 GMT

Thank you for your information！

RE: BLE mesh : Failed to publish & Out of network adv

Amanda Hsieh — Tue, 13 May 2025 12:23:50 GMT

Here is the PR with fix: https://github.com/zephyrproject-rtos/zephyr/pull/89881

RE: BLE mesh : Failed to publish & Out of network adv

Amanda Hsieh — Thu, 27 Mar 2025 15:44:38 GMT

Not fixed in v.2.9.1 yet.

RE: BLE mesh : Failed to publish & Out of network adv

Ziyao Zhou — Tue, 25 Mar 2025 05:11:48 GMT

Hi,

I have test in the new 2.91 sdk, the problems is still there.

RE: BLE mesh : Failed to publish & Out of network adv

Amanda Hsieh — Fri, 21 Feb 2025 15:15:44 GMT

We cannot promise any schedule on Devzone. Sorry for the inconvenience.

RE: BLE mesh : Failed to publish & Out of network adv

Ziyao Zhou — Fri, 21 Feb 2025 00:21:58 GMT

Thank you so much for your information. Could you please let me know when you solve this?

RE: BLE mesh : Failed to publish & Out of network adv

Amanda Hsieh — Thu, 20 Feb 2025 13:30:32 GMT

Hi,

From the team:

Preliminary assesment shows the mesh stack code does not free up advertising memory slabs when mesh is suspended. This, the slabs keep getting consumed during suspend-resume cycles, eventually running out of ADV buffer pool. This requires a bug fix and we might need some time to fix it.

-Amanda H.

RE: BLE mesh : Failed to publish & Out of network adv

Ziyao Zhou — Wed, 19 Feb 2025 09:30:07 GMT

I have put this code in the original sample and will still have this issue, so the NUS service is not the problem.

In addition I change the CONFIG_BT_MESH_ADV_BUF_COUNT to 256, Still cannot use. But I noticed when the CONFIG_BT_MESH_ADV_BUF_COUNT is higher, the time when data read stuck to error log is higher. (I do notice that people count will stop printing and after some time the error log happen).

To make sure every bt_mesh_resume() and bt_mesh_suspend() work. My new code is:

#include <zephyr/bluetooth/bluetooth.h>
#include <bluetooth/mesh/models.h>
#include "model_handler.h"
#include "nus_handler.h" 
#include "pm.h" 

#define GET_DATA_INTERVAL 999

static struct k_work_delayable get_data_work;
BT_MESH_HEALTH_PUB_DEFINE(health_pub, 0);
static bool mesh_suspended = false;


static void sensor_cli_data_cb(struct bt_mesh_sensor_cli *cli,
                               struct bt_mesh_msg_ctx *ctx,
                               const struct bt_mesh_sensor_type *sensor,
                               const struct bt_mesh_sensor_value *value)
{
    if (sensor->id == bt_mesh_sensor_people_count.id) {
        const char *count_str = bt_mesh_sensor_ch_str(value);
        printk("People count is %s\n", count_str);
        nus_update_people_count(count_str);
        if (!mesh_suspended) {
            int err = bt_mesh_suspend();
            if (err) {
                printk("Error suspending mesh (%d)\n", err);
            } else {
                mesh_suspended = true;
            }
        } else {
            printk("Mesh is not resumed, skipping suspend.\n");
        }
    }
}


static const struct bt_mesh_sensor_cli_handlers bt_mesh_sensor_cli_handlers = {
    .data = sensor_cli_data_cb,
};

static struct bt_mesh_sensor_cli sensor_cli =
    BT_MESH_SENSOR_CLI_INIT(&bt_mesh_sensor_cli_handlers);

static void get_data(struct k_work *work)
{   
    int err;
    if (!bt_mesh_is_provisioned()||(health_pub.addr == BT_MESH_ADDR_UNASSIGNED)) {
        k_work_schedule(&get_data_work, K_MSEC(GET_DATA_INTERVAL));
        return;
    }

    if (mesh_suspended) {
        err = bt_mesh_resume();
        if (err) {
            printk("Error resuming mesh (%d)\n", err);
            k_work_schedule(&get_data_work, K_MSEC(GET_DATA_INTERVAL));
             return;
        }
        mesh_suspended = false;
    }

    /* 发送获取People Count的请求 */
    err = bt_mesh_sensor_cli_get(&sensor_cli, NULL, &bt_mesh_sensor_people_count, NULL);
    if (err) {
        printk("Error getting people count (%d)\n", err);
        
    }
    

    k_work_schedule(&get_data_work, K_MSEC(GET_DATA_INTERVAL));
}


static void attention_on(const struct bt_mesh_model *mod) {}
static void attention_off(const struct bt_mesh_model *mod) {}

static const struct bt_mesh_health_srv_cb health_srv_cb = {
    .attn_on = attention_on,
    .attn_off = attention_off,
};

static struct bt_mesh_health_srv health_srv = {
    .cb = &health_srv_cb,
};




static struct bt_mesh_elem elements[] = {
    BT_MESH_ELEM(1,
        BT_MESH_MODEL_LIST(
            BT_MESH_MODEL_CFG_SRV,
            BT_MESH_MODEL_HEALTH_SRV(&health_srv, &health_pub),
            BT_MESH_MODEL_SENSOR_CLI(&sensor_cli)
        ),
        BT_MESH_MODEL_NONE
    ),
};

static const struct bt_mesh_comp comp = {
    .cid = CONFIG_BT_COMPANY_ID,
    .elem = elements,
    .elem_count = ARRAY_SIZE(elements),
};

const struct bt_mesh_comp *model_handler_init(void)
{
    k_work_init_delayable(&get_data_work, get_data);
    k_work_schedule(&get_data_work, K_MSEC(GET_DATA_INTERVAL));
    
    return &comp;
}

Could you please help me figure out this, thank you so much!

RE: BLE mesh : Failed to publish & Out of network adv

Ziyao Zhou — Tue, 18 Feb 2025 01:29:35 GMT

Hi, I am using NCS 2.9.

After I change the CONFIG_BT_MESH_ADV_BUF_COUNT to 30

I will still got this error

By the way, on this mesh device I still got a NUS service, does that affect this issue?

And only when I add my power management code into the model_handler will I have this issue. If bt_mesh_prov is always enable, this will be OK. Is there any way to clear ADV buffer after disable the mesh?

Thank you so much for your help!

RE: BLE mesh : Failed to publish & Out of network adv

Amanda Hsieh — Mon, 17 Feb 2025 20:14:22 GMT

Hi,

What is your NCS version?

[quote user=""] it can work well for around 30s and then will have "<err> bt_mesh_access: Failed to publish (err -105) <err> bt_mesh_transport: Out of network advs"[/quote]

The error indicates a failure to publish a message likely due to insufficient network advertisement buffers from this line. Try to increase CONFIG_BT_MESH_ADV_BUF_COUNT.

Regards,
Amanda H.