MESH CHAT

RE: MESH CHAT

Aleksander Nowakowski — Mon, 24 Feb 2025 10:33:49 GMT

Hello,

When requesting Composition Data, what Node are you connected to as GATT Proxy? On the last image from an iPhone I see that it's "PheSensor". Did you try connecting directly to the MeshChat node?

If you're using "PheSensor", are you able to send messages to this node, for example add / remove an App Key? Does this Node has proxy feature enabled? You can control it on Configuration Server screen.

I'll give few reasons why you may get a timeout for requesting Composition Data:

1. If you're connected to a freshly provisioned node - this should work. The app knows the Network key, it knows the Device Key, the Sequence Number is 0 and RPCL is empty. If it times out it means that the node ignored the receved message, i.e. failed to decode it.

2. If you're connected using a Proxy in between, there may be more reasons:

Proxy Node does not know the Network key
Proxy Node expects higher Seq from the phone

If you are able to send messages and get responses from a Proxy node, neither of these 2 are the reasons.

Proxy feature is disabled on the connected proxy node

This is enabled by default in our samples.

I would try to connect to the newly provisioned node as proxy (search after tapping CONNECT (Android) or disable Auto connection and connect manually (iOS).

RE: MESH CHAT

Dazz_ — Tue, 18 Feb 2025 17:05:22 GMT

Hi Edvin , sorry for my late response.

1: I don't have a DK because I am using the nrf52840 with a custom PCB, with NCS v2.2.0

2: I tried with another phone (Android) and it returned the same errors, see the screenshots below:

3: Would you suggest any CONFIG_LOGS I can enable, so I can understand better where the error occurs?

Thank you!

RE: MESH CHAT

Edvin — Mon, 17 Feb 2025 10:25:30 GMT

Can you try with:

1: Another DK

2: Another phone?

RE: MESH CHAT

Dazz_ — Fri, 14 Feb 2025 16:45:58 GMT

Hi Edvin

Thank you for your explanation.

Yes after seeing "Provisioning Success" on the app I get stuck on "Status: Requesting Composition Data" and after a bit fail with the "Error: Requested Timed Out", but if I go to the "Proxy" tab, the node is connected. And if I remove the automatic connection, click on Disconnect, and then search for a Proxy node, using the + symbol, I can see the previous provisioned node. But it still cannot get the Composition Data, nor associate an Application Key.

I also tried to go on the Node tab and then select Reset Node, it returned "Status: Resetting node...", and after a bit, I got "Error: Requested Timed Out". 🤔

Which configuration should I enable on the node to help troubleshoot this issue? Thank you again!

This is a snippet from the code in the past message:

## LOGS OPTIONS:
#CONFIG_BT_MESH_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_NET_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_PROXY_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_TRANS_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_BEACON_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_CRYPTO_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_ADV_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_ACCESS_LOG_LEVEL_DBG=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_MESH_DEBUG=y
CONFIG_BT_MESH_DEBUG_PROXY=y
# CONFIG_BT_DEBUG_CONN=y
# CONFIG_BT_DEBUG_ATT=y
# CONFIG_BT_DEBUG_GATT=y
# CONFIG_BT_LOG_LEVEL_DBG=y
CONFIG_BT_DEBUG_SMP=y
# CONFIG_BT_MESH_DEBUG_TRANS=y
# CONFIG_BT_MESH_DEBUG_PROV=y

RE: MESH CHAT

Edvin — Fri, 14 Feb 2025 10:30:24 GMT

[quote user="Dazz_"]Did you try to use my same NCS version?
[/quote]

I tested both v2.2.0 and v2.8.0.

[quote user="jermi"]What version of NRF MESH are you using[/quote]

I am using nRF Mesh version 4.2.0 (iOS), but my colleague also tested using 3.3.3 on Android, without issues.

The sniffer trace packets that you refer to are:

177: Just a malformed advertisement packet. Lost probably due to noisy environment. No big deal, and it happens all the time. This was before connecting to the phone.

1903: Just some BLE packet with mesh information. Nothing wrong with that packet (just that the sniffer doesn't have the correct keys to decrypt the content).

1922: That may be a bug in the sniffer. However, it is just a channel map update from the phone. Since the devices are still connected after this, it seems that both devices uses the new channel map. The same is the case for the 1290 packet, so I believe this is fine.

I do believe that what you are seeing is an issue, but I am not sure how to reproduce it, and hence not able to investigate it. I remember seeing something similar at one point, but then the issue was to make sure the phone was connected to a node in the network. In the iOS app, this is configured in the "proxy" tab. "Automatic Connection" was not turned on for some reason. When it fails, look in this tab to see if you are still connected to a node in the network.

Best regards,

Edvin

RE: MESH CHAT

jermi — Fri, 14 Feb 2025 01:17:27 GMT

Hi Edvin：

What version of NRF MESH are you using ，The version I am using。

jermi

RE: MESH CHAT

Dazz_ — Thu, 13 Feb 2025 17:57:13 GMT

Hi Edvin ,

Did you try to use my same NCS version?

This is the link in which you can download the log relative to the sniffed packets using WireShark: https://we.tl/t-Jdve90ix0q

If you do not want to download it I can attach some screenshot at the end of this message.

Also, this is my prj.conf file:

Which logs options do you want me to enable that will help you to understand better the issue?

# # Enable East sensors
CONFIG_SENSOR=y

# Enable RTT logging and logs
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_LOG=y
CONFIG_CONSOLE=y

# Config file from zaphyr/samples/bluetooth/mesh
# CONFIG_MAIN_STACK_SIZE=2048
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS_NVS=y
CONFIG_SETTINGS=y
CONFIG_HWINFO=y

CONFIG_BT=y
CONFIG_BT_DEVICE_NAME="Node"
CONFIG_BT_L2CAP_TX_BUF_COUNT=8
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_OBSERVER=y
CONFIG_BT_BROADCASTER=y

CONFIG_BT_CTLR_DUP_FILTER_LEN=0
CONFIG_BT_CTLR_LE_ENC=n
CONFIG_BT_CTLR_LE_PING=n
CONFIG_BT_DATA_LEN_UPDATE=n
CONFIG_BT_PHY_UPDATE=n
CONFIG_BT_CTLR_MIN_USED_CHAN=n
CONFIG_BT_CTLR_PRIVACY=n
CONFIG_BT_CTLR_CHAN_SEL_2=n

CONFIG_BT_MESH=y
CONFIG_BT_MESH_MODEL_EXTENSIONS=y
CONFIG_BT_MESH_RELAY=y
CONFIG_BT_MESH_FRIEND=y
CONFIG_BT_MESH_PB_ADV=y

CONFIG_BT_MESH_PB_GATT=y
CONFIG_BT_MESH_GATT_PROXY=y
CONFIG_BT_MESH_GATT_PROXY_ENABLED=y
CONFIG_BT_MESH_PB_GATT_CLIENT=y

CONFIG_BT_MAX_CONN=3
CONFIG_BT_MESH_TX_SEG_MAX=10
# CONFIG_BT_MESH_RX_SEG_MAX=10
CONFIG_BT_MESH_ADV_BUF_COUNT=13

CONFIG_BT_EXT_ADV=y
CONFIG_BT_EXT_ADV_MAX_ADV_SET=5

CONFIG_BT_MESH_PROXY_USE_DEVICE_NAME=y
CONFIG_BT_MESH_CFG_CLI=y
CONFIG_BT_MESH_DEFAULT_TTL=3


# CONFIG_BT_MESH_SUBNET_COUNT=2
# CONFIG_BT_MESH_APP_KEY_COUNT=2
# CONFIG_BT_MESH_MODEL_GROUP_COUNT=2
# CONFIG_BT_MESH_LABEL_COUNT=3

## LOGS OPTIONS:
#CONFIG_BT_MESH_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_NET_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_PROXY_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_TRANS_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_BEACON_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_CRYPTO_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_ADV_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_ACCESS_LOG_LEVEL_DBG=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_MESH_DEBUG=y
CONFIG_BT_MESH_DEBUG_PROXY=y
# CONFIG_BT_DEBUG_CONN=y
# CONFIG_BT_DEBUG_ATT=y
# CONFIG_BT_DEBUG_GATT=y
# CONFIG_BT_LOG_LEVEL_DBG=y
CONFIG_BT_DEBUG_SMP=y
# CONFIG_BT_MESH_DEBUG_TRANS=y
# CONFIG_BT_MESH_DEBUG_PROV=y

Pics legend:
1. Before Confirm Provisioning

2. After Provisioned complete

3. Request Composition data timeout

The network provisioner is my iPhone (iOS 18.3) with nRF Mesh App (v4.2.0)

Thank you for your time!

RE: MESH CHAT

Edvin — Thu, 13 Feb 2025 10:28:41 GMT

I am not able to reproduce it on my DK, even with the hex file from your build folder. Can you check the logs from the nRF52832/nRF52840? Does that say anything when it fails?

[quote user="Dazz_"]I also have an nrf52840-Dongle that I used to sniff the packets with Wireshark and noticed some errors[/quote]

What errors specifically? What packet numbers are you referring to?

BR,
Edvin

RE: MESH CHAT

jermi — Wed, 12 Feb 2025 01:46:08 GMT

NCS2.8 Select NRF52832DK, No modifications were made based on the sample，Compile using Vscode

D:\NCS\v2.8.0\nrf\samples\bluetooth\mesh\chatdevzone.nordicsemi.com/.../0474.chat.7z

RE: MESH CHAT

Dazz_ — Tue, 11 Feb 2025 16:33:04 GMT

I am using:

A custom PCB board that includes RAK4630, nrf52840 with NCS Version 2.2.0

I edit the code in a way to remove the DK functions and lib so I can run the mesh and provisioning but it returns a Get Composition Data Timeout.

I also have an nrf52840-Dongle that I used to sniff the packets with Wireshark and noticed some errors. See the log attached.

Thank you for your help Edvin

#include <ncs_version.h>
printk("NCS Version: %s\n", NCS_VERSION_STRING);
// NCS Version: 2.2.0

https://we.tl/t-Jdve90ix0q

RE: MESH CHAT

Edvin — Tue, 11 Feb 2025 14:56:48 GMT

I am not able to reproduce it. Can you share the build command that you used to build it, together with uploading your build folder?

Best regards,

Edvin

RE: MESH CHAT

jermi — Tue, 11 Feb 2025 13:48:18 GMT

Yes, I am using NCS2.8 and the nRF52832 DK.

RE: MESH CHAT

Edvin — Tue, 11 Feb 2025 11:50:39 GMT

Are both of you using NCS v2.8.0 and nRF52832 DK?

RE: MESH CHAT

Dazz_ — Mon, 10 Feb 2025 18:30:14 GMT

Hi Edvin
I have the same issue. It returns a "Get Composition Data Timeout" on iOS (18.3).

I also tried other easier and basic examples like this one: https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/bluetooth/mesh

But it returns the same error. Same as Jermi's screenshot. I tried to use another phone with Android instead but nothing.

I tried to develop a simple code following the documentation and the samples but no clue! 😞

jermi Did you solve this issue?

Hope we can make it work! Thank you guys! 🙂

RE: MESH CHAT

jermi — Mon, 10 Feb 2025 09:37:09 GMT

Hi Edvin：

I deleted all DK programs, downloaded them again, and also deleted all devices on my phone. I restarted and performed the following steps. Please check if the process is correct

The four LED lights on the DK board flash, and the phone displays as follows

The phone display has been stuck in this state without changing

Best Regards！

JERMI

RE: MESH CHAT

Edvin — Mon, 10 Feb 2025 08:05:20 GMT

Have you tried resetting the mesh network on your phone, and erasing the nRF52832, and re-programming it?

Has the DK been used for any other applications with the same phone in the past? Can you check if it is listed under the bluetooth settings in the phone's OS? If so, try to "Forget device" or "Remove device".

Best regards,

Edvin

RE: MESH CHAT

jermi — Fri, 07 Feb 2025 15:23:19 GMT

RE: MESH CHAT

Edvin — Fri, 07 Feb 2025 13:03:27 GMT

Make sure you are still connected to the network. What does it say under the "proxy" menu in the nRF Mesh app?

Best regards,

Edvin

RE: MESH CHAT

jermi — Fri, 07 Feb 2025 05:58:22 GMT

Timeout error, how do I handle it？

RE: MESH CHAT

Edvin — Fri, 24 Jan 2025 14:43:16 GMT

Try clicking the "Get composition data", and see if it comes up. This is usually part of the provisioning process, but perhaps it failed.

Best regards,

Edvin

RE: MESH CHAT

jermi — Fri, 24 Jan 2025 01:37:10 GMT

Hello Edvin:

I Add An Key in the last screenshot. The third button from the bottom,

Sent command From UART Disp:

How can I communicate on two Demo boards？

Best Regards

Jermi

RE: MESH CHAT

Edvin — Thu, 23 Jan 2025 23:06:45 GMT

Hello Jermi,

Did you see any warnings when you built the sample? Does the UART log from the nRF say anything when you start the application?

I don't think it should matter, but could you try to add an App Key in the last screenshot. The third button from the bottom.

I will test this tomorrow morning when I get in the office.

Best regards,

Edvin