Mesh Network is unstable in NCS v3.0.0-preview1

Hello.

Since nRF Connect SDK v3.0.0 has been released, I am testing the sample program.
It is a sample I have frequently used from previous versions.
The provisioning with the smartphone app was successful, but the communication afterward is unstable.
nRF Mesh for iOS, v4.3.1.

  1. Provisioning was successful.
  2. An error message appeared when retrieving the Composition Data.
    This was not shown in app version v4.2.0, so it seems to have been added in a recent update.
    At first, I thought the issue with unstable communication was due to using the old version of the app, but after updating the app to the latest version, I noticed this message.
  3. Data could not be retrieved.
  4. I swiped down the smartphone screen and attempted to retrieve the data again, which was successful.
  5. I confirmed that the sample program is working.
  6. I closed the smartphone app, and after a few minutes, I restarted the app, at which point the error message appeared.
    After this, no operations were accepted at all.
    Not only restarting the app, but also rebooting the program using the DK's Reset button results in the same issue.

Here are the logs outputted to the terminal.

*** Booting Mesh Light Fixture v2.8.99-ee7da8fdd9a0 ***
*** Using nRF Connect SDK v3.0.0-preview1-100d4fc3fa2e ***
*** Using Zephyr OS v4.0.99-71b0e2cc8bc4 ***
Initializing...
[00:00:00.322,296] <inf> fs_nvs: 8 Sectors of 4096 bytes
[00:00:00.322,296] <inf> fs_nvs: alloc wra: 0, fe8
[00:00:00.322,296] <inf> fs_nvs: data wra: 0, 0
[00:00:00.347,778] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.347,808] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.347,839] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 216.4748 Build 1825499040
[00:00:00.348,358] <inf> bt_hci_core: No ID address. App must call settings_load()
Bluetooth initialized
[00:00:00.372,924] <inf> bt_hci_core: Identity: E2:CF:AA:B2:45:B7 (random)
[00:00:00.372,955] <inf> bt_hci_core: HCI: version 6.0 (0x0e) revision 0x20b2, manufacturer 0x0059
[00:00:00.372,985] <inf> bt_hci_core: LMP: version 6.0 (0x0e) subver 0x20b2
[00:00:00.374,725] <inf> bt_mesh_provisionee: Device UUID: 301050dc-a34c-4365-8fef-af235cb3ac9a
Mesh initialized
Successfully enabled LC server
[00:00:20.069,458] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:00:24.499,359] <wrn> bt_conn: Timeout discarded. No blocking in syswq.
[00:00:26.837,341] <wrn> bt_conn: Timeout discarded. No blocking in syswq.
[00:00:26.837,463] <wrn> bt_conn: Timeout discarded. No blocking in syswq.
[00:00:26.837,554] <wrn> bt_conn: Timeout discarded. No blocking in syswq.
[00:00:27.026,977] <inf> bt_mesh_main: Primary Element: 0x000d
[00:00:28.099,487] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:00:32.538,238] <wrn> bt_conn: Timeout discarded. No blocking in syswq.
[00:00:41.668,609] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:00:46.099,975] <wrn> bt_conn: Timeout discarded. No blocking in syswq.
New light transition-> Lvl: 0, Time: 0, Delay: 0
Current light lvl: 0/65535
New light transition-> Lvl: 65535, Time: 0, Delay: 0
Current light lvl: 65535/65535
New light transition-> Lvl: 0, Time: 0, Delay: 0
Current light lvl: 0/65535
[00:05:10.464,691] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
[00:05:14.920,654] <wrn> bt_conn: Timeout discarded. No blocking in syswq.

By the way, the error message immediately after provisioning started appearing after updating the smartphone app from v4.2.0 to v4.3.1.
Do I need to modify any samples to resolve this error message?

Thanks for reading.

a.da

Parents
  • Additional Note:

    It seems that in v3.0.0-preview1, the Mesh Proxy Service sometimes fails to start for some reason.

    • After Provisioning
      This doesn't always happen.
    • When there are no other nodes temporarily in the Mesh Network
      This almost always happens.

    Newly tried:

    1. I prepared one smartphone and two nRF5340DK's.
    2. One DK was flashed with the v3.0.0-preview1 sample program, and the other with the v2.9.0 sample program.
    3. I provisioned them in the order of v3.0.0-preview1 and then v2.9.0 via the smartphone app.
    4. Even after restarting the smartphone app or rebooting the sample programs, the Mesh communication was successfully resumed.

    When I originally created this ticket, I was testing with just one smartphone and one DK.
    I thought that when the DK loses sight of the smartphone, the Mesh communication might not be able to resume, so I tried adding more DKs as described above.
    Also, when both were flashed with the v3.0.0-preview1 sample programs, I gave up because it continued to fail at step 3.

    Apologies if this was an incorrect assumption.

Reply
  • Additional Note:

    It seems that in v3.0.0-preview1, the Mesh Proxy Service sometimes fails to start for some reason.

    • After Provisioning
      This doesn't always happen.
    • When there are no other nodes temporarily in the Mesh Network
      This almost always happens.

    Newly tried:

    1. I prepared one smartphone and two nRF5340DK's.
    2. One DK was flashed with the v3.0.0-preview1 sample program, and the other with the v2.9.0 sample program.
    3. I provisioned them in the order of v3.0.0-preview1 and then v2.9.0 via the smartphone app.
    4. Even after restarting the smartphone app or rebooting the sample programs, the Mesh communication was successfully resumed.

    When I originally created this ticket, I was testing with just one smartphone and one DK.
    I thought that when the DK loses sight of the smartphone, the Mesh communication might not be able to resume, so I tried adding more DKs as described above.
    Also, when both were flashed with the v3.0.0-preview1 sample programs, I gave up because it continued to fail at step 3.

    Apologies if this was an incorrect assumption.

Children
No Data
Related