Bluetooth Mesh - light_ctrl sample - bt_mesh_access - warnings

RE: Bluetooth Mesh - light_ctrl sample - bt_mesh_access - warnings

toni95 — Mon, 25 Mar 2024 08:44:20 GMT

Hi,

The error warning may be related to a wrong subscription/publish:

When subscribing/publishing make sure thet you do not subscribe to and publishing everything to the same group! I created a group called "Server Publish Group" where I set every sensor server to publish its data to this group. The client subscribes to this group. Then I created another group called "Server Subcribe Group" where all servers subscribe to and the client publishes to. This way I do not get those kinds of errors (as mentioned here: bt_mesh_access error).

The error <wrn> bt_mesh_access: Clearing publish retransmit timer may be related to sending messages. As stated in the sensor_server example

/* Only one message can be published at a time. Swap sensor after each timeout. */

There can only be one message be published. You may have a look at the example code for sensor_server.

I hope this helps.

Best,

Toni

RE: Bluetooth Mesh - light_ctrl sample - bt_mesh_access - warnings

cnhyades — Mon, 29 Jan 2024 07:54:23 GMT

Hi Susheel,

Thanks.

Maybe I'm doing something wrong in provisoning/configuring. Please let me know your steps, I'll try to compare what I'm doing different.

RE: Bluetooth Mesh - light_ctrl sample - bt_mesh_access - warnings

Susheel Nuguru — Mon, 29 Jan 2024 07:23:17 GMT

Sorry for late reply Sharan,

I tested this with IOS and I got only these while provisioning and no error messages during bind, subscribe, publish and add to group.

*** Booting nRF Connect SDK v2.5.1 ***
Initializing...
[00:00:00.008,239] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.008,239] <inf> fs_nvs: alloc wra: 0, fe8
[00:00:00.008,270] <inf> fs_nvs: data wra: 0, 0
[00:00:00.008,422] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision:
                                            c5 93 ba a9 14 4d 8d 05  30 4e 9b 92 d7 71 1e e8 |.....M.. 0N...q..
                                            aa 02 50 3c                                      |..P<
[00:00:00.012,084] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.012,115] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.012,145] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017
[00:00:00.012,573] <inf> bt_hci_core: No ID address. App must call settings_load()
Bluetooth initialized
[00:00:00.272,308] <inf> bt_hci_core: Identity: DD:11:EE:AF:37:4D (random)
[00:00:00.272,338] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x1102, manufacturer 0x0059
[00:00:00.272,369] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x1102
[00:00:00.278,472] <inf> bt_mesh_prov_device: Device UUID: e9602ec8-f278-4411-969f-d1370d87ebee
Mesh initialized
Successfully enabled LC server
[00:00:09.736,175] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:00:22.951,690] <err> bt_mesh_prov_device: Invalid confirmation value
[00:00:26.955,963] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:00:56.205,627] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:01:10.879,119] <inf> bt_mesh_main: Primary Element: 0x0007
[00:01:11.895,446] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:01:16.425,415] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
New light transition-> Lvl: 0, Time: 0, Delay: 0
Current light lvl: 0/65535

As all the mesh nodes are behaving normally after this, I think it is safe to ignore these logs with errors.

RE: Bluetooth Mesh - light_ctrl sample - bt_mesh_access - warnings

cnhyades — Fri, 26 Jan 2024 08:01:35 GMT

Nothing special. After provisining step -> with the Configuration Wizard:

1. Bind application keys to all the models(Select All)
2. Subribe to Group 1 all models(Select All)
3. Publication to all to model(Select All)
4. Go to Groups -> Group1 -> ON/OFF

And I see those warnings and errors

I'm trying to understand how the light_ctrl and sensor_server work together:

1. Manually control(on/off/dim) the light without any warning or errors.
2. When I press the button1 on the sensor_server sample I expect the light level to change or something happens happens logically. I'm not able to get the grip how its all working together.

Any help on this greately appreciated.

RE: Bluetooth Mesh - light_ctrl sample - bt_mesh_access - warnings

Susheel Nuguru — Fri, 26 Jan 2024 07:37:25 GMT

Hi,

Normally err is not a good sign. But I am not getting that log with error at my end. What else did you do to reproduce it apart from provisioning?

RE: Bluetooth Mesh - light_ctrl sample - bt_mesh_access - warnings

cnhyades — Thu, 25 Jan 2024 11:53:59 GMT

Hi Susheel,

Understood, thanks. I've not modified the sample code yet, but I'll keep in mind about the CONFIG_MAIN_STACK_SIZE.

What's your input on the other warnings - Do I need to care or ignore them?

<wrn> bt_mesh_access: Clearing publish retransmit timer

<wrn> bt_mesh_net: Unable to allocate loopback

<err> bt_mesh_access: No OpCode 0x00008208 for elem

RE: Bluetooth Mesh - light_ctrl sample - bt_mesh_access - warnings

Susheel Nuguru — Thu, 25 Jan 2024 11:34:35 GMT

I see the same at my end.

But as mentioned in this thread, these are some requests initiated by the IOS and our stack always ignores them which does not interrupt the flow of the node logic.

By the way I have noticed that this sample uses most of its main stack, so I suggest that you increase CONFIG_MAIN_STACK_SIZE if you are adding more logic in the main thread.