openthread cli does not auto start and cannot use commissionner

RE: openthread cli does not auto start and cannot use commissionner

wass — Tue, 04 Jul 2023 16:38:37 GMT

Thank you very much for your support, the "autojoin" sample is out of scope though, as the question was about the cli. I am capable of using join functions with a custom app. Therefore, I will not follow up this question we can close it as I will proceed by creating a different sample than the cli.
Thank you again for the help, I don't think it is worth it to follow up why exactly the cli sample did not work with a specific flag.

RE: openthread cli does not auto start and cannot use commissionner

Sigurd Hellesvik — Tue, 04 Jul 2023 08:17:14 GMT

Hi wass.

I will continue helping in this case.

[quote user="wass"]Flashing actually does not delete the openthread settings region[/quote]

That is correct.

However, if you flash and erase, openthread settings will be erased.

[quote user="wass"]As you can see, the cli sample starts as disabled and does not attempt to join any network as per the expected `CONFIG_OPENTHREAD_JOINER_AUTOSTART=y`[/quote]

From your description, your issue is that when you call "ot factoryreset", the device does not autojoin again, rigjt?

If I run my autojoin sample, the device automatically joins on "ot factoryreset".
See the video below for a sample
devzone.nordicsemi.com/.../autojoin.mp4

Regards,
Sigurd Hellesvik

RE: openthread cli does not auto start and cannot use commissionner

AHaug — Tue, 20 Jun 2023 13:48:21 GMT

Hi,

Thank you for providing me with a sample and steps to recreate the issue. This is just a heads up that it might take some time attempt to recreate the issue you're observing but I will try to prioritize it towards the end of the working week

Kind regards,
Andreas

RE: openthread cli does not auto start and cannot use commissionner

wass — Wed, 14 Jun 2023 17:17:20 GMT

Hi,

thank you for the suggestions. I checked the github issue link, that is something I was aware of and is quite common for newly flashed devices in order to be in a factory reset state right after flashing. Flashing actually does not delete the openthread settings region, that's why, what actually deletes the openthread settings region is calling "ot factoryreset" which I included in my test as shown above.

I think the question could be answered by investigating the code or having a clear overview on what the cli does, which is a bit challenging to me. If the code proves that the behavior is expected then reproducing it will not justify if it is a bug or not, maybe the cli example was just not intended to be used like that.

In order to make reproduction easier, as requested here I put together in one directory all what is needed, the readme also includes the needed command which must include the test overlay

https://github.com/HomeSmartMesh/sdk-hsm-thingy53/tree/main/samples/30_usb_dongle_router

here the commands from the readme

```shell

west build -p always -b nrf52840dongle_nrf52840 -- "-DOVERLAY_CONFIG=overlay-usb.conf;overlay-joiner-rounter.conf" -DDTC_OVERLAY_FILE="usb.overlay"

nrfutil pkg generate --hw-version 52 --sd-req=0x00 --application build/zephyr/zephyr.hex --application-version 1 build/zephyr/zephyr.zip

nrfutil dfu usb-serial -pkg build/zephyr/zephyr.zip -p COM9

```

RE: openthread cli does not auto start and cannot use commissionner

AHaug — Tue, 13 Jun 2023 09:16:46 GMT

Hi,

From what I know it should autojoin. Could you have a look at this git issue from zephyr and check the logs to see if the issue is similar as the one reported in the issue and try the suggested fix: github.com/.../30433

It seems that you have not erased the OT settings area on flash (west flash --erase). Looking at the logs, your device already had a dataset stored and it simply formed a network. The startup code won't bother with the joining procedure if it has a valid dataset stored in flash.

If it does not solve the issue, could you check and see if it is reproducable in a somewhat minimal sample such as https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/openthread_samples/autojoin?

Kind regards,
Andreas

RE: openthread cli does not auto start and cannot use commissionner

wass — Mon, 12 Jun 2023 16:54:42 GMT

Hi,
thank you for taking this up.

I'll try to simplify and reduce the scope of the question.

With the above joiner config applied on the cli sample, is the following scenario expected

uart:~$ ot factoryreset
------reboot
uart:~$ ot state
disabled
Done

As you can see, the cli sample starts as disabled and does not attempt to join any network as per the expected `CONFIG_OPENTHREAD_JOINER_AUTOSTART=y`

If that is somehow expected, that would answer the question as it is different than normal samples, the cli is maybe overriding the default config ?

RE: openthread cli does not auto start and cannot use commissionner

AHaug — Mon, 12 Jun 2023 14:28:54 GMT

Hi,

Glad to hear that you've solved (atleast partially?) the issue you were observing. Could you verify if you've solved it or not?

If not, I'll continue supporting you with solving the case!

Kind regards,
Andreas

RE: openthread cli does not auto start and cannot use commissionner

wass — Sat, 10 Jun 2023 14:54:58 GMT

I answer part of my own issue, as I clarified the "commissioning" part. It was not clear to me when a dataset is needed and when not.
when testing a new fresh factoryreset cli and creating a dataset as described here, it works

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/thread/overview/commissioning.html#setting-up-the-commissioner

I'll still investigate why it does not autostart, and when it comes to other issues (joining from intermediate router, I'll test more and might open an issue in a different ticket).